Skip to content

Commit

Permalink
meta: wrap flaky test template at 80 characters
Browse files Browse the repository at this point in the history
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]>
  • Loading branch information
cjihrig authored and codebytere committed Jun 18, 2020
1 parent d4442b1 commit 148c1f1
Showing 1 changed file with 8 additions and 4 deletions.
12 changes: 8 additions & 4 deletions .github/ISSUE_TEMPLATE/4-report-a-flaky-test.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,17 +8,21 @@ 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.
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
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.
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**:
Expand Down

0 comments on commit 148c1f1

Please sign in to comment.