Repository navigation
Land #4 and #5 on main (they merged into their stacked parent branches) - #6
Merged
Merged
Conversation
The central run now groups failed tests by their real cause (an app crash, a browser error, a server error, or the check that failed), with an example test, its screenshot and trace, and the code at a crash. The comment shows them as a table under the headline, quotes the code, keeps known failures apart as "probably not from your PR", and, when a crash or browser error leads and the PR changes a dependency's version in package.json, points at that bump. Table cells cannot be broken by pipes in error text. A crash among failed tests is titled "failed", not "couldn't run your build". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er PRs share While the suite runs, the central run now publishes live.json (counts and the top browser-side cause so far). The poll loop reads it every two minutes from tests.iblai.app, logs a progress line, and posts one early-warning comment once a crash or browser error has hit 10 tests; the run keeps going. /status shows the same live counts. In the comment, a cause other PRs' recent runs hit too is marked "also failing on …, probably not yours", and the code quote and the dependency hint follow this PR's own top cause. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
feat: warn the PR early when its build crashes, and mark failures other PRs share
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.
#4 and #5 were stacked and got merged into their parent branches instead of
main. GitHub only retargets a stacked PR when its parent branch is deleted. Only #3 reachedmain.This PR brings the rest onto
main:feat/show-causesnow holds #4 + #5. There is no new code. The tree is identical to the reviewed tip of #5, on top ofmain's #3.After merging: tag
v1.6.0and movev1.v1still points at v1.5.0, so no PR runs #2–#5 yet.🤖 Generated with Claude Code