Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: use form schema for flaky test template #40737

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
34 changes: 0 additions & 34 deletions .github/ISSUE_TEMPLATE/4-report-a-flaky-test.md

This file was deleted.

47 changes: 47 additions & 0 deletions .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.