dify - 💡(How to fix) Fix Web test shard jobs hide failure details until report merge [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

The web test workflow runs each shard with only the blob reporter. When a shard exits with a failure, the shard job log does not show the failed test cases or error details. The readable failure output is only produced later in the merge report job after the blob reports are downloaded and merged.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Problem

The web test workflow runs each shard with only the blob reporter. When a shard exits with a failure, the shard job log does not show the failed test cases or error details. The readable failure output is only produced later in the merge report job after the blob reports are downloaded and merged.

This makes it hard to diagnose which shard failed directly from the failing shard job, especially when the matrix job is the first place reporting the exit code.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING