"Success" sometimes shows up in failing tests' replay.err files
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I've seen this before but never really payed much attention to it. @rocallahan ran into it today. I don't know where that output comes from; a quick scan of util.sh doesn't show any clues. The output can safely be ignored, but it's kind of misleading.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining util.sh and reproducing a failing test that produces a replay.err file containing "Success". Trace where that output is emitted, then verify that the misleading line no longer appears in replay.err for failing tests while the failure information remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, shell
- Domain
- devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100