Skip to content

browser.test_pthread_create more flakey in CI in recent days. #12368

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

Open
sbc100 opened this issue Sep 29, 2020 · 3 comments
Open

browser.test_pthread_create more flakey in CI in recent days. #12368

sbc100 opened this issue Sep 29, 2020 · 3 comments

Comments

@sbc100
Copy link
Collaborator

sbc100 commented Sep 29, 2020

I've seen this test flake quite a few times recently. e.g:

https://app.circleci.com/pipelines/github/emscripten-core/emscripten/8321/workflows/ac5e8100-f66c-4ef2-bc54-b37ad3db84de/jobs/361395

@sbc100
Copy link
Collaborator Author

sbc100 commented Sep 29, 2020

@kripken

@sbc100 sbc100 changed the title browser.test_pthread_create more flaky in CI in recent days. browser.test_pthread_create more flakey in CI in recent days. Sep 29, 2020
kripken added a commit that referenced this issue Oct 2, 2020
…akey (#12383)

See #12368 - the flakiness in the test appears to be 100% due to the minimal runtime
part, so something specific is racy there. After spending a little time I saw nothing
obvious, but maybe I'm not familiar enough with minimal runtime to know where to
look, that is, where the differences between the runtimes would be regarding pthreads.

For now this disables that test on minimal runtime, and also makes the test stricter -
it's 100% deterministic so there's no need to retry once after a failure (which actually
made the flakiness here harder to notice).

Note that this does not remove all minimal runtime + pthreads tests, as there is still
test_minimal_runtime_hello_pthread (which is simpler, and shows no flakiness).
@stale
Copy link

stale bot commented Apr 17, 2022

This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant.

@stale stale bot added the wontfix label Apr 17, 2022
@sbc100
Copy link
Collaborator Author

sbc100 commented Apr 18, 2022

bump

@stale stale bot removed the wontfix label Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant