Skip to content

Conversation

@amirh
Copy link
Contributor

@amirh amirh commented Jul 26, 2018

No description provided.

@Hixie
Copy link
Contributor

Hixie commented Jul 26, 2018

Is there a bug tracking this? We should include all the logs that led us to mark it flaky.

@Hixie
Copy link
Contributor

Hixie commented Jul 26, 2018

I'm a little concerned about so quickly rushing to mark this flaky. It's been extremely reliable in the past, with no more flakiness than any other test. It's only ever failed twice in a row with the recent engine roll.

@amirh
Copy link
Contributor Author

amirh commented Jul 26, 2018

Filed #19826 with logs from the last 3 flakes.

@amirh
Copy link
Contributor Author

amirh commented Jul 26, 2018

I cannot reproduce it locally, I guess if it's not a flake we will see it immediately when it gets to the device lab...

@amirh
Copy link
Contributor Author

amirh commented Jul 26, 2018

Closing this PR as we currently think this is a rare flake (we'll know once we roll again 😄 )

@amirh amirh closed this Jul 26, 2018
@amirh amirh deleted the flake branch July 26, 2018 19:17
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 10, 2021
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