Skip to content

Commit d97872d

Browse files
committed
meta: use form schema for flaky test template
PR-URL: #40737 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Richard Lau <[email protected]>
1 parent e58cce4 commit d97872d

File tree

2 files changed

+47
-34
lines changed

2 files changed

+47
-34
lines changed

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

-34
This file was deleted.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
name: Report a flaky test
2+
description: Report a flaky test in our CI
3+
title: "Investigate flaky test - "
4+
labels: ["flaky-test"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thank you for reporting a flaky test.
10+
11+
Flaky tests are tests that fail occasionally in the Node.js CI, but not
12+
consistently enough to block PRs from landing, or that are failing in CI
13+
jobs or test modes that are not run for every PR.
14+
15+
Please fill in as much of the form below as you're able.
16+
- type: input
17+
attributes:
18+
label: Test
19+
description: The test that is flaky.
20+
placeholder: e.g. `test-fs-stat-bigint`
21+
validations:
22+
required: true
23+
- type: input
24+
attributes:
25+
label: Platform
26+
description: The platform the test is flaky on.
27+
placeholder: e.g. `macos` or `linux`
28+
- type: textarea
29+
attributes:
30+
label: Console output
31+
description: >
32+
A pasted console output from a failed CI job showing the whole failure
33+
of the test.
34+
render: console
35+
- type: textarea
36+
attributes:
37+
label: Build links
38+
description: Links to builds affected by the flaky test.
39+
value: '- '
40+
- type: textarea
41+
attributes:
42+
label: Additional information
43+
description: >
44+
If any investigation has been done, please include any information
45+
found, such as how consistently the test fails, whether the failure
46+
could be reproduced locally, when the test started failing, or anything
47+
else you think is relevant.

0 commit comments

Comments
 (0)