Repository navigation
T-22072 [CI] Name the test in the E2E Linear issue and include the failure summary - #9
Merged
Merged
Conversation
…ilure summary The issue title names the test (E2E failure: AWS Lambda extension) and its body carries each failed job's errors and summary: the invocations and the read-back tables. A job that stops before its read-back names the step it stopped at. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
download-artifact unpacks a lone matching artifact straight into its path, so in a run with one job the summary was never found. Also keep an annotations API error out of the issue, and keep the plain issue text byte-identical to before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A failed scheduled E2E run opens a Linear issue titled "E2E failure: E2E", listing only the failed jobs and steps. The read-back tables that explain a failure sat in the job summaries, which the issue did not include.
notify_linear_failure.ymltakes two optional inputs.test_namereplaces the workflow name in the title.job_summariesadds each failed job's::error::messages (read from the job's check-run annotations) and the summary the job uploaded as thee2e-summary-<job name>artifact. A caller that sets neither gets the issue exactly as before.test_name: AWS Lambda extensionandjob_summaries: true, so the issue is titled "E2E failure: AWS Lambda extension".🤖 Generated with Claude Code