"make test" always uses the last successfully build binary although building failed

Open
#22 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cmake

Research direction

Start by tracing the CMake-generated make test target and how test binaries are built and selected. Reproduce the case where a test fails to build, then verify that make test reports failure instead of running a previously built binary or reporting 100% success.

Written by the indexing model from the issue text.

Description

This can lead to 100% tests passed although one of the tests failed to build and should thereby also fail the test (not run).

Acceptance Criteria
  • If a test fails to build the test should not pass when running make test
Dominant language
CMake
Stars
6
Forks
9
Avg merge
23h 34m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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 seqan/app-template

All issues in seqan/app-template

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.