-
Notifications
You must be signed in to change notification settings - Fork 157
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
TestParallelLambdaCreation flake #4731
Labels
impact/flaky-test
A test that is unreliable
kind/engineering
Work that is not visible to an external user
Comments
t0yv0
added
impact/flaky-test
A test that is unreliable
and removed
needs-triage
Needs attention from the triage team
labels
Nov 8, 2024
This was referenced Nov 11, 2024
@flostadler can we get this skipped or some such it is very impactful and is blocking releases. Thanks! |
t0yv0
pushed a commit
that referenced
this issue
Nov 15, 2024
The flaky Lambda test might be caused by errors when flushing & closing the writers for the Lambda archives (e.g. out of space). This change adds handling for those errors, to help understand why the files appear to not be found when executing the pulumi programs. Relates to #4731
mikhailshilkov
added
the
kind/engineering
Work that is not visible to an external user
label
Nov 18, 2024
That change didn't bring any clarity either. It almost seems like the file gets cleaned up async by another process. I'll skip it for now to bring stability back into the release process while we investigate |
That sounds good! |
flostadler
added a commit
that referenced
this issue
Nov 19, 2024
Skipping `TestParallelLambdaCreation` because it started to be flaky. Skipping the test for now to bring stability back into the release process while we investigate the issue. Relates to #4731
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
impact/flaky-test
A test that is unreliable
kind/engineering
Work that is not visible to an external user
Got a failure in TestParallelLambdaCreation that resolved itself after a retry. The test might be flaky.
The text was updated successfully, but these errors were encountered: