| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
From https://docs.gitlab.com/ee/ci/yaml/#artifactspaths it doesn't
look like gitlab yaml does not expect shell command execution there.
CI does indeed complain about this:
WARNING: invalid path "": unexpected command substitution at 1:1
Fix this by using a glob pattern.
|
|
|
|
|
| |
The gcr4 replaces gcr3, thus make it possible to use either of the two,
while defaulting to gcr4, as it'll live for a longer time.
|
| |
|
|
|
|
|
|
| |
The others are not erroring out correctly for close_range syscalls,
causing issues when spawning. So use the "crun" runners and disable
"asan" as there is no overlap.
|
| |
|
|
|
|
|
| |
libXfixes 6.0 provides the new ClientDisconnectMode that clients can
use to declare themselves as to-be-terminated.
|
| |
|
|
|
|
|
|
| |
The new FDO templates do not need privileged runners anymore. Also,
those do not exist and the asan should be run on the asan runner
instead.
|
| |
|
|
|
|
|
| |
The used template was changed. Also switch back to rawhide as it is
working again now (requiring a dependency update).
|
|
|
|
| |
This also fixes building the image inside non-privileged containers.
|
| |
|
| |
|
|
|
|
|
|
| |
The images have not been updated for a while due to a docker TLS issue.
Disabling it fixes this, see
https://about.gitlab.com/blog/2019/07/31/docker-in-docker-with-docker-19-dot-03/
|
|
|
|
|
|
| |
Currently the coverage report is not generating, causing the delivery to
also fail. As we are already allowing a coverage failure, do the same
for delivery.
|
|
|
|
| |
This is needed to build libgsd.
|
| |
|
|
|
|
|
| |
It appears to be broken currently on rawhide. Assume that this is just
an intermitten failure and hope it will just start working eventually.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It works only if enabled via CI/CD Settings. More info available at
https://docs.gitlab.com/ee/user/project/pipelines/settings.html#test-coverage-parsing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AddressSanitizer (or ASan) is a programming tool that detects memory
corruption bugs such as buffer overflows or use after free. AddressSanitizer
is based on compiler instrumentation.
MemorySanitizer (MSan) is a detector of uninitialized memory reads in C/C++ programs.
Uninitialized values occur when stack- or heap-allocated memory is read before
it is written.
ThreadSanitizer is a tool that detects data races.
UndefinedBehaviorSanitizer (UBSan) is a fast undefined behavior detector. UBSan
catches various kinds of undefined behavior, for example:
- Using misaligned or null pointer
- Signed integer overflow
- Conversion to, from, or between floating-point types which would overflow the
destination
The llvm.org states that Sanitizers have found thousands of bugs everywhere.
Sanitizers running during CI can prevent bugs from taking up residence. They
are helper tools to maintain bugs out.
|
|
|
|
| |
The expected gain is 5 minutes.
|
|
|
|
|
| |
As it's really only useful to read the logs when things fail, best to
have a bit more information there.
|
|
|
|
|
| |
The libcanberra gtk module wasn't installed, which made the test suite
fail. Add libcanberra-gtk3 to the CI packages to fix this.
|
| |
|
|
|
|
|
| |
This replaces the special cases and temporary files hack used beforehand
and enables testing of the async logic in the backlight code.
|
|
|
|
|
|
| |
Port the test suite to python 3.
Fixes #65
|
|
|