-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error with diff in github actions #666
Comments
I wonder if perhaps this is specific to a certain version of |
I have several jobs running in parallel to each other (via Github Actions matrixes). |
Can you try a newer version of helm and see if that helps? |
Hello! I'll keep an eye on it, the fact is that on the previous version I encountered problems on average 1 time out of 10-15 launches. |
@allenporter
|
Hi, what version of helm are you using? Thanks! |
Hello. I have the latest version of Helm, but I don’t really understand why it’s here.
|
What's the "concurrency" about? does that run in parallel on the same filesystem . Basically we can't have multiple processes clobbering the local filesystem. Flux build creates temp files that may be getting messed up if two run at once in the same directory. To do multiple runs at once they may need their own file paths checked out. |
OK this still seems consistent with helms cache not working with multiple instances in parallel. People say the solution is to use a separate temporary directory for every instance. The reason for a shared repository cache is to avoid needing to pull the same repositories multiple times specially when running diffs (everything is loaded twice). We could workaround with a lock held on each repo as a hack but not a fan necessarily of that. Could also add more controls to tune helm concurrency. I'd prefer if helm cli was fixed to be more resilient to running in parallel of course.... Need to think about this more. |
Hello!
This error sometimes appears for an unknown reason about 1 time per 10 starts.
I'm using version 5.2.0, but I observed this on version 5.1.0 as well.
The text was updated successfully, but these errors were encountered: