Skip to content

chore: improve ecosystem test failure reporting#20937

Open
crimsonjay0 wants to merge 4 commits into
eslint:mainfrom
crimsonjay0:improve-ecosystem-test-failure-reporting
Open

chore: improve ecosystem test failure reporting#20937
crimsonjay0 wants to merge 4 commits into
eslint:mainfrom
crimsonjay0:improve-ecosystem-test-failure-reporting

Conversation

@crimsonjay0

Copy link
Copy Markdown
Contributor

Prerequisites checklist

AI acknowledgment

  • I did not use AI to generate this PR.
  • (If the above is not checked) I have reviewed the AI-generated content before submitting.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

What changes did you make? (Give an overview)

The workflow previously sent only a bare "Ecosystem tests failed." message to Discord. This PR enhances it to:

  1. Include which plugins failed and a direct link to the CI run in the Discord notification.
  2. Automatically create a new GitHub issue (or update an existing open one) with failure details.

Fixes #20886

Is there anything you'd like reviewers to focus on?

@crimsonjay0 crimsonjay0 requested a review from a team as a code owner May 31, 2026 17:57
@github-project-automation github-project-automation Bot moved this to Needs Triage in Triage May 31, 2026
@netlify

netlify Bot commented May 31, 2026

Copy link
Copy Markdown

Deploy Preview for docs-eslint canceled.

Name Link
🔨 Latest commit e7ea1ca
🔍 Latest deploy log https://app.netlify.com/projects/docs-eslint/deploys/6a204949f31b1f00089589cb

@eslint-github-bot eslint-github-bot Bot added the chore This change is not user-facing label May 31, 2026
@fasttime fasttime added the accepted There is consensus among the team that this change meets the criteria for inclusion label Jun 1, 2026
@fasttime fasttime moved this from Needs Triage to Implementing in Triage Jun 1, 2026
Comment thread .github/workflows/ecosystem-tests.yml Outdated
Comment thread .github/workflows/ecosystem-tests.yml Outdated
Comment thread tools/sync-ecosystem-issue.js
module.exports = async ({ github, context, core }) => {
const runUrl = `${context.serverUrl}/${context.repo.owner}/${context.repo.repo}/actions/runs/${context.runId}`;
const title = "Ecosystem tests failure";
const label = "build";

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about creating a dedicated label for "ecosystem tests fail"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have permissions to create repo labels, but if a maintainer can set one up, I'll update the code to use it.

Comment thread tools/build-failure-summary.js

@fasttime fasttime left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks! Leaving open for @kecrily's feedback.

@fasttime fasttime moved this from Implementing to Second Review Needed in Triage Jun 9, 2026
@fasttime

Copy link
Copy Markdown
Member

Sorry for the delay getting this ready to merge @crimsonjay0. There is now a merge conflict. Could you take a look?

@fasttime fasttime moved this from Second Review Needed to Implementing in Triage Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

accepted There is consensus among the team that this change meets the criteria for inclusion chore This change is not user-facing contributor pool github actions

Projects

Status: Implementing

Development

Successfully merging this pull request may close these issues.

Repo: Improve failure message for ecosystem tests failure

3 participants