Build OpenSCAP with clang sanitizers #1970
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jan-cerny
force-pushed
the
clang
branch
21 times, most recently
from
24a4bbd to
73d8ad0
Compare
jan-cerny
changed the title
| targets: | ||
| - fedora-all-x86_64 | ||
| - centos-stream-8-x86_64 | ||
| - centos-stream-9-x86_64 | ||
|
|
||
| - job: tests | ||
| trigger: pull_request |
There was a problem hiding this comment.
Suggested change
| trigger: pull_request | |
| trigger: pull_request | |
| identifier: standard |
This is probably what makes the mess in the statuses.
|
I modified my spec to have a part of sanitizers I hope are also in scope here, #1883 |
|
I wasn't able to configure Packit to not create "unwanted" builds and test runs. It seems to combine the build targets together. It would be possible to avoid this situation if Packit had an option to define build-test dependencies explicitely, see packit/packit-service#1720. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will create a special COPR build where OpenSCAP will be built with the Clang compiler with special options.
The special option is a ThreadSanitizer https://clang.llvm.org/docs/ThreadSanitizer.html is a tool that detects data races.
This way we will be able to use and download the build and use it instead of normal OpenSCAP package to debug issues like freezing or thread crashes. The
oscapwill work as usual but at the same time it will print warnings when a data race happens.To get meaningful warnings you should install also the openscap-debuginfo rpm package, you will get tracebacks with exact file names and line numbers of the problematic code.
I propose creating COPR builds for EPEL 8 and 9.