Skip to content

Commit 148c1f1

Browse files
cjihrigcodebytere
authored andcommitted
meta: wrap flaky test template at 80 characters
The other issue templates are wrapped at 80 characters. This commit updates the flaky test template to be consistent. PR-URL: #33677 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Zeyu Yang <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
1 parent d4442b1 commit 148c1f1

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md

+8-4
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,21 @@ labels: "CI / flaky test"
88
<!--
99
Thank you for reporting a flaky test.
1010
11-
Flaky tests are tests that fail occaisonally in Node.js CI, but not consistently enough to block PRs from landing,
12-
or that are failing in CI jobs or test modes that are not run for every PR.
11+
Flaky tests are tests that fail occaisonally in Node.js CI, but not consistently
12+
enough to block PRs from landing, or that are failing in CI jobs or test modes
13+
that are not run for every PR.
1314
1415
Please fill in as much of the template below as you're able.
1516
1617
Test: The test that is flaky - e.g. `test-fs-stat-bigint`
1718
Platform: The platform the test is flaky on - e.g. `macos` or `linux`
18-
Console Output: A pasted console output from a failed CI job showing the whole failure of the test
19+
Console Output: A pasted console output from a failed CI job showing the whole
20+
failure of the test
1921
Build Links: Links to builds affected by the flaky test
2022
21-
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.
23+
If any investigation has been done, please include any information found, such
24+
as how consistently the test fails, whether the failure could be reproduced
25+
locally, when the test started failing, or anything else you think is relevant.
2226
-->
2327

2428
* **Test**:

0 commit comments

Comments
 (0)