summaryrefslogtreecommitdiff
path: root/.github/ISSUE_TEMPLATE
diff options
context:
space:
mode:
authorMichaël Zasso <targos@protonmail.com>2021-11-06 09:46:35 +0100
committerMichaël Zasso <targos@protonmail.com>2021-11-08 13:01:53 +0100
commit8e42eaec53e7fc70c90c4aaebaf672e89c598afe (patch)
tree25cfdb3f9a33a3f49a36fc5f23715d3aa987a3e5 /.github/ISSUE_TEMPLATE
parenta420da61735e8b993ee99a5abca9f19e1c67d8e5 (diff)
downloadnode-new-8e42eaec53e7fc70c90c4aaebaf672e89c598afe.tar.gz
meta: use form schema for flaky test template
PR-URL: https://github.com/nodejs/node/pull/40737 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Richard Lau <rlau@redhat.com>
Diffstat (limited to '.github/ISSUE_TEMPLATE')
-rw-r--r--.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md34
-rw-r--r--.github/ISSUE_TEMPLATE/4-report-a-flaky-test.yml47
2 files changed, 47 insertions, 34 deletions
diff --git a/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md b/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md
deleted file mode 100644
index 544c9d5f47..0000000000
--- a/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-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 occasionally in the 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**:
diff --git a/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.yml b/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.yml
new file mode 100644
index 0000000000..2ad659dec3
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.yml
@@ -0,0 +1,47 @@
+name: Report a flaky test
+description: Report a flaky test in our CI
+title: "Investigate flaky test - "
+labels: ["flaky-test"]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ Thank you for reporting a flaky test.
+
+ Flaky tests are tests that fail occasionally in the 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 form below as you're able.
+ - type: input
+ attributes:
+ label: Test
+ description: The test that is flaky.
+ placeholder: e.g. `test-fs-stat-bigint`
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Platform
+ description: The platform the test is flaky on.
+ placeholder: e.g. `macos` or `linux`
+ - type: textarea
+ attributes:
+ label: Console output
+ description: >
+ A pasted console output from a failed CI job showing the whole failure
+ of the test.
+ render: console
+ - type: textarea
+ attributes:
+ label: Build links
+ description: Links to builds affected by the flaky test.
+ value: '- '
+ - type: textarea
+ attributes:
+ label: Additional information
+ description: >
+ 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.