-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add a flaky test issue template to ensure that enough information is provided for investigation PR-URL: #33500 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Beth Griggs <[email protected]>
- Loading branch information
1 parent
3d05e3d
commit b7ea7be
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
name: Report a flaky test | ||
about: Report a flaky test in our CI | ||
labels: "CI / flaky test" | ||
|
||
--- | ||
|
||
<!-- | ||
Thank you for reporting a flaky test. | ||
Flaky tests are tests that fail occaisonally in Node.js CI, but not consistently enough to block PRs from landing, | ||
or that are failing in CI jobs or test modes that are not run for every PR. | ||
Please fill in as much of the template below as you're able. | ||
Test: The test that is flaky - e.g. `test-fs-stat-bigint` | ||
Platform: The platform the test is flaky on - e.g. `macos` or `linux` | ||
Console Output: A pasted console output from a failed CI job showing the whole failure of the test | ||
Build Links: Links to builds affected by the flaky test | ||
If any investigation has been done, please include any information found, such as how consistently the test fails, whether the failure could be reproduced locally, when the test started failing, or anything else you think is relevant. | ||
--> | ||
|
||
* **Test**: | ||
* **Platform**: | ||
* **Console Output:** | ||
``` | ||
REPLACE ME | ||
``` | ||
* **Build Links**: |