Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
/ corefx Public archive

Turn AutoRetry On #29312

Merged
merged 1 commit into from
Apr 25, 2018
Merged

Turn AutoRetry On #29312

merged 1 commit into from
Apr 25, 2018

Conversation

sunandabalu
Copy link
Member

No description provided.

@danmoseley
Copy link
Member

@karelz should OK this also. Karel, this will rerun failing jobs (eg., System.Net.Http.Tests as a whole) if any fail. As configured it will only try this once. All failing logs will be shown in MC in the usual way, even if it passes on rerun. A pass on rerun will show up in the default view, albeit in green, with a curly arrow.

This should help suppress flaky failures, which we can mine from Kusto to actually do something about.

@karelz
Copy link
Member

karelz commented Apr 24, 2018

In general that sounds good. I am curious:

What exactly will show MC if:

  1. Only 1st run fails test A?
  2. 1st run fails A, 2nd run fails B?
  3. 1st run fails A & B, 2nd run fails B & C?
    How will it show in build report and in test history?

Is it applied to PRs, nightly runs or both?

@sunandabalu
Copy link
Member Author

sunandabalu commented Apr 24, 2018

The number of times a retry happens is not per test level, it is at a work item level. If a workitem has one or mote test failures, the same work item is requeued to run again.

  1. Only 1st run fails test A?
    Which means in the retry attempt the test passed, test A will show up in MC as passed on retry. The Work Item will also show as passed on retry.
  2. 1st run fails A, 2nd run fails B?
    If tests fails in the 1st attempt, and passes in the subsequent attempts will show up as passed on retry. Work Item will show as passed on retry if subsequent attempt was successful, otherwise will show as fail.
  3. 1st run fails A & B, 2nd run fails B & C?
    Same as 2 above

Is it applied to PRs, nightly runs or both?
Applies to all Helix runs for the repo.

@karelz
Copy link
Member

karelz commented Apr 24, 2018

@sunandabalu are you sure [2] and [3] above will show "passed on retry" when there were failures in the retry run? I could believe that in case [2] if the comparison is per test, but in [3] it is a definitely a bug as one test consistently failed in both runs. That should definitely show as a failure.

Will I see both reruns entries in per-test history view on MC? Will I be able to click-through to the logs for each run?

@sunandabalu
Copy link
Member Author

sunandabalu commented Apr 25, 2018

The work item will show as pass on retry only if the 2nd attempt passes ie no tests failed. In both [2] and [3] the work item will show as fail. The specific test that passed on retry will show as passedonretry.
The logs specific to each run per test will be displayed , for eg., if this test were run twice you will see two entries for the specific arch - https://mc.dot.net/#/product/netcore/master/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Fcli~2F/build/20180424.05/workItem/System.Net.Http.Functional.Tests/wilogs

Per Test page will show PassedOnRetry if the test passed on retry , for eg. here - https://mc.dot.net/#/product/netcore/master/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Fcli~2F/build/20180424.05/workItem/System.Net.Http.Functional.Tests

Per Workitem will show PassedOnRetry only if the next attempt was successful , for eg., here - https://mc.dot.net/#/product/netcore/master/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Fcli~2F/build/20180424.05

@sunandabalu
Copy link
Member Author

@karelz can you approve the change, so I can merge the PR?

@karelz
Copy link
Member

karelz commented Apr 25, 2018

@sunandabalu do you have example links where it shows PassedOnRetry? The links don't seem to show that ...

@sunandabalu
Copy link
Member Author

Not yet in PROD, once this PR makes it in we can get some data showing up.

@sunandabalu
Copy link
Member Author

@dotnet-bot Please Test Linux-musl x64 Debug Build

@sunandabalu
Copy link
Member Author

@danmosemsft , @karelz looks like I don't have access to merge to corefx, can either of you merge this?

@danmoseley danmoseley merged commit 3d90a52 into dotnet:master Apr 25, 2018
@karelz karelz added this to the 2.2.0 milestone Apr 25, 2018
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants