Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI - test_optimizer] GitHub Actions, Melos, very_good test lead sometimes to cache error #947

Open
md-weber opened this issue Jan 16, 2024 · 2 comments
Labels
bug Something isn't working as expected p3 Issues that we currently consider unimportant

Comments

@md-weber
Copy link

Description
We use GitHub Actions with the caching support of the subosito/flutter-action@v2 together with Melos and every now and then we run into the following error:

cache/bundled/test_optimizer_0.1.0+1_e324e538d331470906db7fbaea6b8d957bcce68d/hooks/build/hooks/pre_gen/pre_gen_7389adb0f4462262bdd04123d3826c0231f89ed6.dart': No such file or directory

Melos config looks like this:

  ci:test:
    run: |
      melos exec -c 4 -- \
        very_good test --coverage --test-randomize-ordering-seed random

Steps To Reproduce

  • Create a minimal project with melos multiple packages
  • Add a CI with GitHub Actions
  • Run very_good test with 4 concurrencies via melos in all packages

Expected Behavior
No error

Additional Context
I know that is not a perfect issue, but any help is much appreciated.

@md-weber md-weber added the bug Something isn't working as expected label Jan 16, 2024
@md-weber md-weber changed the title [CI - test_optimizer] GitHub Actions, Melos, VGV Test lead sometimes to cache error [CI - test_optimizer] GitHub Actions, Melos, very_good test lead sometimes to cache error Jan 16, 2024
@tomarra
Copy link
Contributor

tomarra commented Jan 29, 2024

Hi @md-weber 👋 Thanks for opening up an issue.

Would you be able to provide a sample project that can clearly demonstrate this? We don't tend to work with a lot of projects using Melos so want to make sure we are not spinning our wheels or trying something different then what your putting together. One other thing to ask is if you have tried this without the concurrency flag. We have seen some issues with that in the past and would like to be able to rule that out quickly if possible.

Thanks in advance and looking forward to your reply.

@tomarra tomarra added the waiting for response Waiting for follow up label Jan 29, 2024
@md-weber
Copy link
Author

Hi @tomarra thanks for your answer, I will work on a demo example this weekend and hope that I can provide you an example till next week.

At the moment we did exactly that to at least not see the warning anymore. As soon the concurrency is out, it works flawless. If that just mean we cannot use concurrency in Melos it is still good to have that issue so that people know about it 👍

@tomarra tomarra removed the waiting for response Waiting for follow up label Feb 13, 2024
@tomarra tomarra removed their assignment Feb 13, 2024
@tomarra tomarra added the p3 Issues that we currently consider unimportant label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected p3 Issues that we currently consider unimportant
Projects
Status: Backlog
Development

No branches or pull requests

2 participants