Add 'Debugging from the UI' section with parallel-worker URLs and known limitations#58
Merged
Merged
Conversation
samgutentag
added
the
needs review
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Member
Author
|
Verification status (2026-05-29): Verified: customers can use this. Ready to publish.
Ready to publish after editorial and eng review of flagged items. Generated by Claude Code |
samgutentag
added
ready to merge
…d ID, RSpec/Go caveats
samgutentag
force-pushed
the
sam-gutentag/test-error-debugging
branch
from
c23f292 to
aaccd27
Compare
samgutentag
commented
May 26, 2026
| If a failing test raises `RSpec::Core::MultipleExceptionError`, only one of the captured exceptions appears in the failure detail view today. See [Known limitations](../../../dashboard#known-limitations) for the current status and workaround. | ||
| </Info> | ||
|
|
||
| ### Environment Variables |
Member
Author
There was a problem hiding this comment.
promote this to a h2 tag
Member
Author
|
Verification status (May 31, 2026): Debugging-from-UI guide covers existing, shipped behaviors — no flag or eng dependency.
Next action: merge this PR. Generated by Claude Code |
Member
Author
|
Docs Verify Sweep · June 1, 2026 · ✅ live Feature is live in production. Ready to merge. Unchanged from previous sweep (May 31, 2026). Generated by Claude Code |
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.
Summary
flaky-tests/dashboard.mdxcovering the parallel-worker URL gap (with per-CI env-var workaround), Bundle Upload ID lookups (support-only today), and CI artifact retention vs ticket resolution lag.<Info>callouts forRSpec::Core::MultipleExceptionError(single exception surfaced today, gem extension pending) and Go subtests reporting 0ms duration (AI analysis caveat + post-process workaround).flaky-tests/get-started/frameworks/rspec/index.mdxto the MultipleExceptionError note and fromflaky-tests/get-started/frameworks/gotestsum.mdxto the Go-subtest note.Why
Sourced from customer feedback mining (cluster
test-error-log-detail-debugging-info, verdictpartial, 9 pairs across 6 customers). The dashboard page documents the failure-detail UI but doesn't address the recurring gaps: parallel-worker drill-down, Bundle Upload ID search, RSpec MultipleExceptionError visibility, Go-subtest 0ms AI caveat, artifact retention lag.Items flagged for review
CIRCLE_BUILD_URL/BUILDKITE_BUILD_URL/CI_JOB_URL/ the constructed GitHub Actions URL is the right surface to recommend, and that appending it to a JUnit property/system-out block is the recommended approach (vs. a CLI flag we haven't documented).dashboard.mdxis already a split candidate (3 clusters target it). If you'd rather this become a standaloneflaky-tests/debugging-from-the-ui.mdxpage, the section is self-contained and can be lifted out without restructuring the rest of the dashboard doc.gotestsum.mdx(the only Go framework page) at the dashboard limitations section. If there's a more specific Go troubleshooting page planned, the link should move there.Customer signal
test-error-log-detail-debugging-info(verdict: partial, 9 pairs / 6 customers)