No longer have a machine available in the pool.

Fixes ccov-all-export on Windows platform with an if/else split.

Prefixed all code-coverage jobs with the operating system, added Windows
all code coverage jobs.

Add macOS AppleClang/Clang CI jobs

Expand testing to other architectures, with Linux is
amd64/arm64/ppc64le, macOS is amd64/arm64, and Windows is amd64.

When on macOS, if using the Apple-provided toolchain from XCode, also
use the same toolchain for code-coverage. The use of hybrid toolchains
does not go well.

The assimp library now has pkg-config and CMake config files installed
by default, rendering this module script unnecessary.

When cross-compiling, the used emulator will be prefixed to the call.

In addition to the current ARGS multi-value option which appends options
to the end of an executable call, PRE_ARGS instead prefixes items to the
call, to the end for of:
$PRE_ARGS ccov-* $ARGS

Since these files were originally added, the libraries themselves have
added native CMake configuration files that can be used instead.

The only purpose of the job was to create the 'ccov' directory in the
binary directory to store all the generated code coverage files.

Rather than generating the directory at build time using a target,t he
directory is now created at CMake generation time, meaning the build-
time target is no longer necessary.

CI attempted to run jobs on riscv64 nodes when opensuse/fedora don't
have supported container images for that architecture.

Infrastructure/CI runners have been restructured.

This option only applies to C++, however it was being applied to both C
and C++ compilation calls. Using the CMake generator expression limits
the inclusion of this option to just the compiling of C++ files.

Rafał Lalik authored 2 years ago and StableCoder committed 2 years ago

Fix for IWYU, cppcheck and clang-tidy

For AFL itself, when enabled via the AFL variable will search for the
base afl-cc/afl-c++ compiler wrappers, and if found use them. Then any
options specified at configuration time such as the speicifc mode or
options must be specified.

Because of the nature of having to change the compiler, this file must
be included at a very early stage before the compilers are detected and
verified.

Since it supports sanitizers, the sanitizers file has been updated to
add the appropriate flags when AFL is enabled.

Cleaning up the accrual of non-standard formatting.

Updated both the sanitizer file for adding the flag and the README.

Rafał Lalik authored 3 years ago and StableCoder committed 3 years ago

Sometimes genhtml incorrectly discovers the common path, e.g.
https://github.com/linux-test-project/lcov/issues/130
so it is beter to point it manually to the proper location.
wq

Rafał Lalik authored 3 years ago and StableCoder committed 3 years ago

Code coverage: Call ccov-preprocessing target to prepare tree structure before the ccov-all-processing

Rafał Lalik authored 3 years ago and StableCoder committed 3 years ago

According to the documentation, any code coverage is enabled
only when CODE_COVERAGE is enabled. The add_code_coverage()
function was not checking for it. This commit fixes it.

Rafał Lalik authored 3 years ago and StableCoder committed 3 years ago

Each selected sanitizer is tested individually, and if test fails the configure step aborts.
After that, all selected sanitizers are tested for mutual compatibility.

It reuse SET_SANITIZER, sanitizers are passed as a string which is tested with MATCHES. No Delimeter is actually required.

In previous versions to get around issues on Windows, the running of
ccov targets was split to a separate custom target, and then later
re-merged with some processing commands.

This removes that extra split run of the targeted executable, so that it
will only be run just once.

Mark de Wever authored 3 years ago and StableCoder committed 3 years ago

The code has been based on the ccov-all-export target.

All the currently avialable C standards from C90 to C23.

An important distinction between the GCC/lcov and clang/LLVM patterns
when excluding files.

The report targets are not compatible with GCC's code coverage
currently, and if either the C or CXX compiler just wasn't defined, it
would attempt to add it.

Rather than manualy checking for target name re-use, now uses the
default implementation's behaviour and messaging.

When running ccov-run-* targets in parrallel on
Windows, multiple processes would attempt to write to the profile data
files, causing contention and failure. This job has been split in two
and the call to write to file has been serialized through a specified
job pool 'ccov_serial_pool'.

For the ccov-all targets, added a Windows-specific set that utilizes
Powershell commands to work.

CMake only added support for `cmake -E rm` with v3.17.0, prior to that
it was the flawed `cmake -E remove`.

To support this older version, still widely available in Ubuntu 20.04
LTS, there is now a check around commands removing files.

For shared builds on Windows.

Windows has regular Clang available, and the associated LLVm tools to
support code coverage, best to make sure it works.

The creation and changing into the build directory is no longer an
explicit step, isntead using CMake to create the files in the build
directory then running ninja in the build directory instead.

Fixed case where the Clang/Static builds were actually built as shared
binaries.

Some calls to 'rm' and 'echo' did not go through the 'cmake -E' command,
limiting their use to posix-compliant systems.

The ccov-all targets have been replaced with stubs on Windows, as
attempts to feed
file text to the llvm-profdata for processing have so far been
unsuccessful.

Overall however, code coverage on Windows is much more usable by default
for individual ccov targets.

Better to be consistent on naming scheme, as all previous items used
dashes as separators.