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
Reliablility report is inaccurate #647
Comments
The reports here are generated using the |
So this issue should be transferred, but I don't have write accees on the ncu repository so I cannot transfer it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I started investigating nodejs/node#44805
when taking a look at nodejs/reliability#388:
sequential/test-watch-mode-inspect
Example
the first PR in the Failed PR row has two CI runs prior to this report: 46819, 46808
the first CI run reports a failure for this based on the previous osx1015 run https://ci.nodejs.org/job/node-test-commit-osx/47578/ that did not actually run in this build (due to
java.net.ConnectException: Connection timed out
) but Jenkins still considers the child of a previous run to be the child of this run.this obviously happened in other PRS/CI runs as well, wich makes the report links and count very hard to rely on when investigating flaky test issues
The text was updated successfully, but these errors were encountered: