#2073 step 3/4: a skipped qemu run is a ctest skip (SKIP_RETURN_CODE), and the recipe summary says so

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
testing

Research direction

Read check/run_qemu.sh and locate the CTest recipe that runs it, along with the recipe summary. Configure the skipped QEMU result to be reported as a CTest skip and update the summary to say so; confirm a normal run and a Q15T_SKIP_QEMU=1 run are reported appropriately. The issue says the steps for parent #2073 run in order, with tests first.

Written by the indexing model from the issue text.

Description

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

Make a skipped qemu run (check/run_qemu.sh, Q15T_SKIP_QEMU=1) a ctest skip via SKIP_RETURN_CODE, not a pass, and say so in the recipe summary.

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.