-
-
Notifications
You must be signed in to change notification settings - Fork 660
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
internal/internal_integration/node_spec_events_test.go:33 may be flaky #1452
Comments
Thanks for reporting this - I don't know who/how the debian packages are maintained but it seems odd to me that installing ginkgo ends up running all the tests. There's no need to run these and they (especially the integration tests run in series) will add several minutes to the build time. Do you know where we could go to change how ginkgo is built and installed? |
Happy to clarify as needed. Installing the ginkgo package does not run any tests. The tests are being run as part of the build process (and there is another way to execute them using the autopkgtest machinery, but that's unrelated to this bug). As you can see from the build logs above, this is how the tests are being invoked:
the long list of packages is dynamically generated with |
ah, thanks for clarifying. yes this is likely due to a slow build machine. The test is a bit too finnicky about the measured duration so I'm pushing a fix that will make it more lenient (I generally try to avoid testing code with actual as for the invocation. you can use |
v2.20.1 has the fix. I don't generally backport bugfixes to prior minor releases, however, so this will not resolve flakiness issues on older version of Ginkgo. |
Thank you so much! I've backported your commit as https://salsa.debian.org/go-team/packages/golang-github-onsi-ginkgo-v2/-/commit/107e820 so that it can be included in the next package update. |
sounds good. let me know if you see it flake again (i wasn't able to reproduce it locally but am pretty sure this is the issue). |
I finally got around to actually upload this change to debian, only to find another timeout on armel:
At least the issue originally in this bugreport didn't get triggered. I can file a separate issue, if you prefer. let me know. Thanks! |
hey sorry for the long latency. i've bumped this threshold as well and will cut another release oon |
While looking at the debian package of ginkgo, I can across https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078516 that indicates that the Integration Tests may be flaky. Here are two instances where the same test fails in a very similar manner:
Usually this passes on a retry.
The test in question appears to be here: https://github.com/onsi/ginkgo/blob/master/internal/internal_integration/node_spec_events_test.go#L33-L70
It is possible that this test is affected by heavy load on the host, I couldn't reproduce it yet on my laptop.
The text was updated successfully, but these errors were encountered: