You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/src/platform/test/functional/page_objects/share_page.ts@elastic/appex-sharedux# Assigned per https://github.com/elastic/kibana/pull/200209/files#r1846648444
3675
3677
/src/platform/test/accessibility/apps/kibana_overview_*@elastic/appex-sharedux# Assigned per https://github.com/elastic/kibana/pull/200209/files/cab99bce5ac2082fa77222beebe3b61ff836b94b#r1846659920
3676
3678
/x-pack/platform/test/functional/services/sample_data@elastic/appex-sharedux# Assigned per https://github.com/elastic/kibana/pull/200142#discussion_r1846512756
3677
-
/src/platform/test/functional/page_objects/files_management.ts@elastic/appex-sharedux# Assigned per https://github.com/elastic/kibana/pull/200017#discussion_r1840477291
Copy file name to clipboardExpand all lines: .github/workflows/failed-test-investigator.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -284,7 +284,13 @@ Request an automatic fix immediately for a fixable **`application`** failure. Fo
284
284
285
285
**Skip** the `ai:fix-flaky` label — regardless of `failCount` — when a fix PR for this issue is already up (open, in draft, or in review) in the Kibana repository; you already check for one when writing the note block below, so don't request a duplicate. Also skip `ai:fix-flaky` (and `failure:ai-fixable`) for Security Cypress when the doctor action is `migrate`, a new Scout spec, a new API/unit test, or `none`.
286
286
287
-
An engineer can still request a fix for any issue by adding `ai:fix-flaky` manually; that path does not go through this workflow and is unaffected by the recurrence gate.
287
+
An engineer can still request a fix for any issue by adding `ai:fix-flaky` manually; that path does not go through this workflow and is unaffected by the recurrence gate or the team opt-out below.
288
+
289
+
#### Teams opted out of automatic fix requests
290
+
291
+
Some teams prefer to request fixes themselves. When the issue carries one of these `Team:` labels, never add `ai:fix-flaky` — regardless of classification or `failCount`. Still add `failure:ai-fixable` when a fix is available, and use the "Fix available, team opted out" tip in "Comment format" so the team sees how to request one.
292
+
293
+
-`Team:Kibana Management`
288
294
289
295
### "Previous fix didn't hold" label
290
296
@@ -371,6 +377,15 @@ If a fix PR is already up (in draft or in review) in the Kibana repository — t
371
377
> Marked "AI-fixable". Add `ai:fix-flaky` to request a fix now; otherwise it will be requested automatically if the test fails again.
372
378
```
373
379
380
+
**Fix available, team opted out** — you added `failure:ai-fixable` without `ai:fix-flaky` because the issue's team has opted out of automatic fix requests (see "Teams opted out of automatic fix requests"). Fixes are never requested automatically for it, so don't promise one:
381
+
382
+
```markdown
383
+
> [!TIP]
384
+
> Marked "AI-fixable". Add `ai:fix-flaky` to request a fix PR — `<Team: label>` has opted out of automatic fix requests.
385
+
```
386
+
387
+
Fill `<Team: label>` with the issue's opted-out team label, e.g. `Team:Kibana Management`.
388
+
374
389
### 1. Visible header (required)
375
390
376
391
A `###` heading followed by one summary sentence — nothing else, no standing metadata lines:
0 commit comments