mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-12-25 23:21:33 +03:00
commit
a9dba3ef5f
@ -2,8 +2,6 @@
|
||||
|
||||
System and Service Manager
|
||||
|
||||
<a href="http://in.waw.pl/systemd-github-state/systemd-systemd-issues.svg"><img align="right" src="http://in.waw.pl/systemd-github-state/systemd-systemd-issues-small.svg" alt="Count of open issues over time"></a>
|
||||
<a href="http://in.waw.pl/systemd-github-state/systemd-systemd-pull-requests.svg"><img align="right" src="http://in.waw.pl/systemd-github-state/systemd-systemd-pull-requests-small.svg" alt="Count of open pull requests over time"></a>
|
||||
[![Semaphore CI 2.0 Build Status](https://the-real-systemd.semaphoreci.com/badges/systemd/branches/main.svg?style=shields)](https://the-real-systemd.semaphoreci.com/projects/systemd)<br/>
|
||||
[![Coverity Scan Status](https://scan.coverity.com/projects/350/badge.svg)](https://scan.coverity.com/projects/350)<br/>
|
||||
[![OSS-Fuzz Status](https://oss-fuzz-build-logs.storage.googleapis.com/badges/systemd.svg)](https://oss-fuzz-build-logs.storage.googleapis.com/index.html#systemd)<br/>
|
||||
|
@ -198,6 +198,6 @@ can be found under various directories such as `factory/`, `modprobe.d/`, `netwo
|
||||
|
||||
## Utilities for Developers
|
||||
|
||||
`tools/`, `coccinelle/`, `.github/`, `.semaphore/`, `.lgtm/`, `.mkosi/` host various
|
||||
`tools/`, `coccinelle/`, `.github/`, `.semaphore/`, `.mkosi/` host various
|
||||
utilities and scripts that are used by maintainers and developers. They are not
|
||||
shipped or installed.
|
||||
|
@ -69,9 +69,9 @@ available functionality:
|
||||
13. When building systemd from a git checkout the build scripts will
|
||||
automatically enable a git commit hook that ensures whitespace cleanliness.
|
||||
|
||||
14. [LGTM](https://lgtm.com/) analyzes every commit pushed to `main`. The list
|
||||
of active alerts can be found
|
||||
[here](https://lgtm.com/projects/g/systemd/systemd/alerts/?mode=list).
|
||||
14. [CodeQL](https://codeql.github.com/) analyzes each PR and every commit
|
||||
pushed to `main`. The list of active alerts can be found
|
||||
[here](https://github.com/systemd/systemd/security/code-scanning).
|
||||
|
||||
15. Each PR is automatically tested with [Address Sanitizer](https://clang.llvm.org/docs/AddressSanitizer.html)
|
||||
and [Undefined Behavior Sanitizer](https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html).
|
||||
|
@ -211,10 +211,10 @@ where --test-name= is the name of the test you want to run/debug. The
|
||||
--shell-fail option will pause the execution in case the test fails and shows
|
||||
you the information how to connect to the testbed for further debugging.
|
||||
|
||||
Manually running LGTM/CodeQL analysis
|
||||
Manually running CodeQL analysis
|
||||
=====================================
|
||||
|
||||
This is mostly useful for debugging various CodeQL/LGTM quirks.
|
||||
This is mostly useful for debugging various CodeQL quirks.
|
||||
|
||||
Download the CodeQL Bundle from https://github.com/github/codeql-action/releases
|
||||
and unpack it somewhere. From now the 'tutorial' assumes you have the `codeql`
|
||||
@ -238,9 +238,9 @@ This can occur if the specified build commands failed to compile or process any
|
||||
- For other languages, the --command must specify a "clean" build which compiles
|
||||
all the source code files without reusing existing build artefacts.
|
||||
|
||||
If you want to run all queries systemd uses in LGTM/CodeQL, run:
|
||||
If you want to run all queries systemd uses in CodeQL, run:
|
||||
|
||||
$ codeql database analyze codeqldb/ --format csv --output results.csv .github/codeql-custom.qls .lgtm/cpp-queries/*.ql -vvv
|
||||
$ codeql database analyze codeqldb/ --format csv --output results.csv .github/codeql-custom.qls .github/codeql-queries/*.ql -vvv
|
||||
|
||||
Note: this will take a while.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user