-
-
Notifications
You must be signed in to change notification settings - Fork 37.3k
investigate flaky test-fs-stat-bigint #31727
Copy link
Copy link
Closed
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.freebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.fsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
Metadata
Metadata
Assignees
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.freebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.fsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
What steps will reproduce the bug?
Run test-fs-stat-bigint many times on FreeBSD.
How often does it reproduce? Is there a required condition?
It reproduces probably about 1% of the time.
What is the expected behavior?
The test should always pass.
What do you see instead?
The test sometimes fails with a block count of 1 vs 9:
Additional information
Seems to only reproduce on FreeBSD in CI, but I'm running a stress test to confirm.
https://ci.nodejs.org/job/node-stress-single-test/48/