feat(ci): report nightly test history to tcache - #3624
Open
OlufemiAdeOlusile wants to merge 1 commit into
Open
Conversation
OlufemiAdeOlusile
force-pushed
the
add-nightly-history-upload
branch
3 times, most recently
from
August 31, 2026 21:37
f711980 to
ac0c2f2
Compare
OlufemiAdeOlusile
force-pushed
the
add-nightly-history-upload
branch
2 times, most recently
from
September 1, 2026 01:02
1ff587b to
fb2495a
Compare
OlufemiAdeOlusile
marked this pull request as ready for review
September 1, 2026 01:59
Add a `history_name` input and a "Report nightly history" step to the reusable regression workflow. When a nightly's tests do not pass, PUT its JUnit XML to tcache's `/history` endpoint, so the failure analysis can tell a new failure from a recurring one. Only the three nightly workflows set `history_name`, so a manual regression dispatch never writes there. Not `testrun_name`, because that input is also the only gate on the `/import` step above, and nightly runs must stay out of it. `TCACHE_URL` points at the `/results` API, so appending `/history` gave `/results/history` and every upload returned 404. Drop that suffix first. A 200 does not mean the report landed. Caddy answers a path it has no route for with 200 and an empty body, so the step compares the bytes the tcache serves back against the bytes sent. Gate on `steps.testing-step.outcome`, as the failure-analysis steps in this file already do. Job-level `failure()` also fires when a later non-test step fails.
OlufemiAdeOlusile
force-pushed
the
add-nightly-history-upload
branch
from
September 2, 2026 10:50
fb2495a to
118bb78
Compare
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
1 participant
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.
Store a failed nightly's JUnit XML in tcache's
/history, so the failureanalysis can tell a new failure from a recurring one. A new
history_nameinput turns it on, and only the three nightlies set it.
Not
testrun_name, because that input also gates the/importstep above, andnightlies must stay out of it.
TCACHE_URLends in/results, so the suffix is stripped before appending/history. Without that, every upload returns 404.The step then compares the bytes tcache serves back against the bytes sent. A
200 alone is not enough, because Caddy answers an unrouted path with 200 and an
empty body.
This needs the
historytable migration and areverse_proxy /history/*lineon the tcache host. If either is missing the step fails and says so.
Tested locally against tcache at master behind a real Caddy, on a database
migrated from the old schema. A real node test's report uploaded and read back
byte-identical, with its failure intact. The
if:gate is the one part thatneeds a real run.