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

Outcome incorrectly set by Flank #914

Closed
bootstraponline opened this issue Jul 24, 2020 · 6 comments · Fixed by #917
Closed

Outcome incorrectly set by Flank #914

bootstraponline opened this issue Jul 24, 2020 · 6 comments · Fixed by #917
Assignees
Labels

Comments

@bootstraponline
Copy link
Contributor

bootstraponline commented Jul 24, 2020

Describe the bug

A clear and concise description of what the bug is.

[task 2020-07-23T20:29:15.152Z] ┌─────────┬──────────────────────┬──────────────────────────────────────────┐
[task 2020-07-23T20:29:15.153Z] │ OUTCOME │      MATRIX ID       │               TEST DETAILS               │
[task 2020-07-23T20:29:15.153Z] ├─────────┼──────────────────────┼──────────────────────────────────────────┤
[task 2020-07-23T20:29:15.153Z] │  flaky  │ matrix-1vj2pt9wih182 │ 1 test cases failed, 106 passed, 2 flaky │
[task 2020-07-23T20:29:15.153Z] └─────────┴──────────────────────┴──────────────────────────────────────────┘

FTL confirmed the matrix outcome is actually failure. Flank reported flaky.

Let's diagram the Flank outcome setting logic with PlantUML in addition to fixing this bug.

Expected behavior

A clear and concise description of what you expected to happen.

I expected the outcome to match the FTL outcome (failure).

Details (please complete the following information):

Have you tested on the latest Flank snapshot?

Post the output of flank --version.

Flank v20.07.0

Additional context

Add any other context about the problem here.

https://firebase-community.slack.com/archives/C72V6UW8M/p1595539705001900

@pawelpasterz pawelpasterz self-assigned this Jul 27, 2020
@pawelpasterz
Copy link
Contributor

pawelpasterz commented Jul 27, 2020

The logic that flank needs to reflect:

Case Outcome Exit code
at least one test failed failed 1
no failed test but at least 1 flaky flaky 0
no failed and no flaky success 0

@pawelpasterz
Copy link
Contributor

pawelpasterz commented Jul 28, 2020

gcloud output

at least one test failed

Screenshot 2020-07-28 at 09 01 41

no failed test but at least 1 flaky

Screenshot 2020-07-28 at 09 01 56

no failed and no flaky

Screenshot 2020-07-28 at 09 02 09

@pawelpasterz
Copy link
Contributor

pawelpasterz commented Jul 28, 2020

flank output

at least one test failed

Screenshot 2020-07-28 at 09 33 40
Screenshot 2020-07-28 at 09 18 09

no failed test but at least one flaky EDIT: below outcome is Corner Case

Screenshot 2020-07-28 at 09 13 15

no failed and no flaky

Screenshot 2020-07-28 at 09 23 23

What needs to be fixed:

  • the failed test always means failed outcome, regardless of others being flaky (currently flaky tests obscure failed ones)
  • flaky tests mean flaky outcome but with success exit code (currently exit code is 0 but status is success)
  • optional: do we want to change the naming of the outcome? (ex. failure -> failed) cc @jan-gogo

@bootstraponline
Copy link
Contributor Author

  • do we want to change the naming of the outcome?

for naming, let's match gcloud.

@pawelpasterz
Copy link
Contributor

pawelpasterz commented Jul 30, 2020

no failed test but at least one flaky EDIT: below outcome is Corner Case
Screenshot 2020-07-28 at 09 13 15

Above is a corner case that needs to be resolved in a separate issue (#918). It requires to check flank API calls with gcloud's.
Originally described bug to be resolved in #917

@pawelpasterz
Copy link
Contributor

@rpappalax
Fix in review #917. Please let me know immediately if you will encounter a similar issue in the future. Please, keep in mind there is another issue found (thanks to your case 😄 ) we still need to investigate #918

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants