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
Performance tests broken (always paste a result from 3rd Jan, actual run fails) #2647
Comments
CC @tomerd |
I just noticed that my manual tests occasionally failed. I reproduced it by running it in tight loop and eventually tracked it down to an apparent race in
This may be the reason we don't get perf test results. Not the fact that perf testing infra is broken exactly. [1]
[2]
|
CC @FranzBusch for flakey test (we should track that separately) @gmilos good catch! However whatever happens in the performance tests should not make the harness post wrong and outdated data. Also, it's posting is so quickly that I doubt it ran anything at all |
Agreed re the harness being immune to failures in the test binary. For reference, I filed the issue about the specific test here: #2649 |
cc @yim-lee can you help us here. The performance tests seem to broken. |
It posts bogus results because the build doesn't get far enough to the cleanup stage to delete previous test result files, and the job is configured to post contents from the report file. I manually wiped the workspace this time. Updating the job to wipe workspace before build didn't help because it fails very early on (some Git operation), which I will look into now. |
The performance tests post bogus results (from an old run from 3rd Jan) and the actual perf build fails:
E.g.
https://ci.swiftserver.group/view/nio/job/swift-nio2-performance-prb/158/console
The text was updated successfully, but these errors were encountered: