#2078 step 3/3: send the traced program's expected FAIL output to a file or prefix it; keep the verdict line

Open Beginner friendly
  • Is something wrong?
#2,607 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
testing

Research direction

Find the test or script that runs unparsable_identity_traps and inspect how it captures the expected failure output and prints its verdict. Redirect that output to a file or prefix it so a scan for FAIL does not match, while keeping the test's own verdict line; run the step's tests first and confirm the verdict remains visible.

Written by the indexing model from the issue text.

Description

Part of #2078 (step 3 of 3; steps run in order, tests first).

Send unparsable_identity_traps' expected failure output to a file, or prefix it so a scan for FAIL does not match, and keep the test's own verdict line.

Local change only; the PR for this step names this issue.

Dominant language
C++
Stars
2
Forks
5
Avg merge
4h 12m
Merged PRs (30d)
788

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EchoTools/nevr-runtime

All issues in EchoTools/nevr-runtime

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.