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

test-sqlite-statement-sync is flaky #54810

Open
anonrig opened this issue Sep 6, 2024 · 2 comments
Open

test-sqlite-statement-sync is flaky #54810

anonrig opened this issue Sep 6, 2024 · 2 comments
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. linux Issues and PRs related to the Linux platform. sqlite Issues and PRs related to the SQLite subsystem.

Comments

@anonrig
Copy link
Member

anonrig commented Sep 6, 2024

Test

test-sqlite-statement-sync

Platform

Linux x64

Console output

14:03:14 not ok 3703 parallel/test-sqlite-statement-sync
14:03:14   ---
14:03:14   duration_ms: 121007.74000
14:03:14   severity: fail
14:03:14   exitcode: -15
14:03:14   stack: |-
14:03:14     timeout
14:03:14     (node:3665096) ExperimentalWarning: SQLite is an experimental feature and might change at any time
14:03:14     (Use `node --trace-warnings ...` to show where the warning was created)
14:03:14   ...

Build links

Additional information

No response

@anonrig anonrig added the flaky-test Issues and PRs related to the tests with unstable failures on the CI. label Sep 6, 2024
@github-actions github-actions bot added the linux Issues and PRs related to the Linux platform. label Sep 6, 2024
@RedYetiDev RedYetiDev added the sqlite Issues and PRs related to the SQLite subsystem. label Sep 6, 2024
@aduh95
Copy link
Contributor

aduh95 commented Sep 6, 2024

FWIW I'm unable to reproduce on macOS:

$ tools/test.py --repeat 9999 test/parallel/test-sqlite-statement-sync.js -t 1 
[03:27|% 100|+ 9999|-   0]: Done                              

All tests passed.

@jasnell
Copy link
Member

jasnell commented Sep 7, 2024

Unable to reproduce on ubuntu locally either. Given that it's a timeout, we can try moving the test to sequential and see if that addresses the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. linux Issues and PRs related to the Linux platform. sqlite Issues and PRs related to the SQLite subsystem.
Projects
None yet
Development

No branches or pull requests

4 participants