OpenVPN / OpenVPN/openvpn

can we decouple building and running the unit tests?

Open
#914 3 comments 0 reactions 1 assignee View on GitHub

@cron2 is already working on this.

Since Nov 24, 2025.

enhancement
Dominant language
C
Stars
14.6k
Forks
3.4k
PR merge metrics
No merged PRs in 30d

Description

Trying to figure out what failed on running unit-tests can be misleading if it's actually compiling unit-tests, but we do not have a separate stage for it (and I'm not sure how to tackle this in our Makefiles).

But I fould find it useful if I could so something like

$ make
$ make build-checks
$ make check

where the second stage would build everything that is needed for "make check", but not actually run anything (I would run the second stage in my tests with ">$log 2>&1" and only print that log if anything fails)...

Not sure how complex it is, but I thought (in the light of the "building the UT fails" for gerrit 1400/v1) that this would also make the BB mails easier to categorize - a build fail is always a no-go, while a t_client test fail can be "external circumstances", so re-run might work

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.