Skip to content
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

Wrong build status when first fails and rerun passes #174

Open
Muusssi opened this issue Apr 9, 2021 · 1 comment · Fixed by #184
Open

Wrong build status when first fails and rerun passes #174

Muusssi opened this issue Apr 9, 2021 · 1 comment · Fixed by #184
Labels
bug Something isn't working

Comments

@Muusssi
Copy link
Member

Muusssi commented Apr 9, 2021

Describe the bug
When a build has multiple results for the same test case (i.e. reruns) the build status can be wrongly fail even if all test pass in the rerun.

To Reproduce
Steps to reproduce the behavior:

  1. Execute and archive tests where some test cases of a test suite pass others fail
  2. Execute the test that failed in the previous run so that they pass and archive them to the same build
  3. While all test are shown to pass the build status shows failure

Expected behavior
The overall build status should always reflect the status of the last execution of each test case (and suite).

@Muusssi Muusssi added the bug Something isn't working label Apr 9, 2021
@Muusssi
Copy link
Member Author

Muusssi commented Apr 12, 2021

Muusssi added a commit that referenced this issue Apr 22, 2021
The build status is now calculated from the statuses of the last execution
of each test case within that build.
This should also improve the performance of the teams/series API
lakooi added a commit that referenced this issue Apr 26, 2021
…irst-fails-and-rerun-passes

Bug/174 - Wrong build status when first fails and rerun passes (#174)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant