Repository navigation
ci: don't fail test jobs when the gotestsum artifact upload fails - #7781
Merged
Merged
Conversation
Co-authored-by: Isaac <no-reply@databricks.com>
Collaborator
✅ Integration test reportCommit: 354c7e7
Top 6 slowest tests (at least 2 minutes):
|
denik
marked this pull request as ready for review
November 18, 2026 18:29
denik
requested review from
Sankalp-Mittal,
andrewnester and
rugpanov
and removed request for
rugpanov
November 18, 2026 18:29
andrewnester
approved these changes
Nov 18, 2026
Collaborator
❌ Integration test reportCommit: 749c68f
27 interesting tests: 14 RECOVERED, 9 FAIL, 3 flaky, 1 KNOWN
Top 50 slowest tests (at least 2 minutes):
|
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.
Changes
Mark the "Upload gotestsum JSON output" step in
push.ymlascontinue-on-error: true.Why
Twice in three days on main, a
task test (macos, ...)job ran its whole test suite green (PASS Package acceptance) and was still marked failed. In both cases only the artifact upload had failed:That artifact (
test-output-<os>-<deployment>) is only a debugging aid for timing. No job in this workflow downloads it. A failed upload also skipped the "Check no files changed" step. With this change:The release-build artifacts are consumed downstream, so I left them unchanged.
The third run in this group (error/3743) was a Windows job whose hosted runner "lost communication with the server" partway through the tests. That is a GitHub runner issue and is not addressed here.
Dashboard
Failed to CreateArtifact: Unable to make request: ENOTFOUND(Package failed with no test reporting a failure)Tests
None. This is a workflow-only change.
AI agent (opus5.5, isaac_claude)
This pull request and its description were written by Isaac.