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.

Sign up for GitHub

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

Jump to bottom

Change standalone_2/io/http_close_test to be less flaky #35807

Open
whesse opened this issue Jan 30, 2019 · 0 comments
Open

Change standalone_2/io/http_close_test to be less flaky #35807

whesse opened this issue Jan 30, 2019 · 0 comments
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. library-io

Comments

@whesse
Copy link
Contributor

whesse commented Jan 30, 2019

One of the flakiest tests on the VM is standalone_2/io/http_close_test.

Can we make the test more stable, by making it accept network failures, or by making it retry if it sees a failure? This helps to make other flakes more visible, by removing this test from the flakiness dashboard. @sortie
@whesse whesse added area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. library-io area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). labels Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. library-io
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@whesse