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

Steps to investigate CI flakiness with async-streams tests #58864

Merged
merged 4 commits into from
Jan 15, 2022

Conversation

jcouv
Copy link
Member

@jcouv jcouv commented Jan 14, 2022

From discussion with Stephen, those steps should help:

  1. update the ManualResetValueTaskSourceCore code
  2. try to get a crash dump (including embedded symbols and sources)

Relates to #34207
Relates to #58196
Relates to #47156
Relates to #40927

public ValueTaskSourceStatus GetStatus(short token)
{
ValidateToken(token);
return
!_completed ? ValueTaskSourceStatus.Pending :
_continuation == null || !_completed ? ValueTaskSourceStatus.Pending :
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stephentoub FWIW, this seems the only actual code change when updating ManualResetValueTaskSourceCore source code, but I'm not seeing how it could relate to the symptom (ie. the completion sentinel being invoked, see stacktrace below).
Although almost all the failures occur on Linux, there's one on Windows too (so not exclusive).

    at System.Threading.Tasks.Sources.ManualResetValueTaskSourceCoreShared.ThrowInvalidOperationException()
    at System.Threading.Tasks.Sources.ManualResetValueTaskSourceCoreShared.CompletionSentinel(Object _)
    at System.Threading.Tasks.Sources.ManualResetValueTaskSourceCore`1.InvokeContinuation()
    at System.Threading.Tasks.Sources.ManualResetValueTaskSourceCore`1.SignalCompletion()
    at System.Threading.Tasks.Sources.ManualResetValueTaskSourceCore`1.SetResult(TResult result)
    at C.<Main>g__local|0_0()
    at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
    at System.Runtime.CompilerServices.AsyncIteratorMethodBuilder.MoveNext[TStateMachine](TStateMachine& stateMachine)
    at C.<Main>g__local|0_0()
    at C.Main()
    at C.Main()
    at C.<Main>()

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That change came from dotnet/coreclr#22711 which was addressing a race condition. So... it might be relevant.

@jcouv jcouv self-assigned this Jan 14, 2022
@jcouv jcouv added the Feature - Async Streams Async Streams label Jan 14, 2022
@jcouv jcouv marked this pull request as ready for review January 15, 2022 00:36
@jcouv jcouv requested a review from a team as a code owner January 15, 2022 00:36
Copy link
Contributor

@AlekseyTs AlekseyTs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (commit 4)

@jcouv jcouv added the Test Test failures in roslyn-CI label Jan 15, 2022
@jcouv
Copy link
Member Author

jcouv commented Jan 15, 2022

Merging with a single review since test-only change. Thanks

@jcouv jcouv merged commit d1383e7 into dotnet:main Jan 15, 2022
@jcouv jcouv deleted the async-streams1 branch January 15, 2022 00:50
@ghost ghost added this to the Next milestone Jan 15, 2022
@RikkiGibson RikkiGibson modified the milestones: Next, 17.2.P1 Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers Feature - Async Streams Async Streams Test Test failures in roslyn-CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants