| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
libc in the Debian container got updated to 2.31, which in combination
with clang-9 triggers systemd/systemd#14865.
This has been fixed by https://reviews.llvm.org/D74712 which is (to my
knowledge) included in clang-10. To mitigate this without upgrading to
clang-10 we can compile with -O1 which works around it as well, see
https://bugzilla.redhat.com/show_bug.cgi?id=1803203.
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently systemd is no longer installed in fedora containers
by default
```
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348:
starting container process caused "exec: \"/sbin/init\": stat /sbin/init: no such file or directory": unknown.
The command "$CI_MANAGERS/fedora.sh SETUP" failed and exited with 127 during .
```
|
|
|
|
|
|
|
| |
Let's install libzstd & libfido2 to cover two recently added features.
In case of libfido2 this should also get rid of the 'dead code' issues
found by Coverity, like CID#1430168, CID#1430167, CID#1430166, or
CID#1430165.
|
|
|
|
|
| |
Now that CIFuzz supports all the sanitizers we use and ALLOWED_BROKEN_TARGETS_PERCENTAGE
we no longer need that bash script.
|
| |
|
| |
|
| |
|
|
|
|
| |
it's just a follow-up to https://github.com/systemd/systemd/pull/16064
|
| |
|
|
|
|
| |
so we have all PPA definitions at one place.
|
|
|
|
| |
Also, sort the whole list when we're at it.
|
|
|
|
|
| |
Travis CI is getting overloaded, so let's move some load over to GitHub
Actions.
|
|
|
|
|
|
|
| |
In the past we occasionally stumbled upon a build issue which could be
reproduced only with specific optimization level or other compilation
option. Let's try to build the current revision with several most common
compiler options causing such issues to catch them early.
|
|
|
|
|
|
| |
Now that https://github.com/systemd/systemd/issues/15907 is gone,
we can simply use "undefined" instead of listing all the possible checks
explicitly.
|
| |
|
|
|
|
|
| |
Now that https://github.com/systemd/systemd/issues/15583 is gone, it
should be safe to turn it on.
|
|
|
|
|
|
|
| |
To judge from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947134 and
https://salsa.debian.org/debian/util-linux/-/commit/44ec91ef110e7131d8a0467374797bc2e0f30e51,
`util-linux` no longer depends on `fdisk` so it seems it should be installed
manually.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The submit phase of the Fuzzit Travis job has been spuriously failing
for some time with various (and usually pretty hidden) errors, like:
```
./fuzzit create job --type regression ...
2020/04/23 17:02:12 please set env variable FUZZIT_API_KEY or pass --api-key. API Key for you account: ...
```
```
./fuzzit create job --type regression ...
2020/04/23 11:36:53 Creating job...
2020/04/23 11:36:54 Uploading fuzzer...
2020/04/23 11:36:54 Job created successfully
2020/04/23 11:36:54 Get https://...&action=create: read tcp x.x.x.x:39674->x.x.x.x:443: read: connection reset by peer
```
```
./fuzzit create job --type regression ...
2020/04/22 18:09:15 Creating job...
2020/04/22 18:09:16 Uploading fuzzer...
2020/04/22 18:09:37 Job created successfully
2020/04/22 18:09:37 500 Internal Server Error
```
etc.
Let's retry each submit job up to three times to (hopefully) mitigate this.
|
|
|
|
|
|
| |
Based on a report from Fossies.org using Codespell.
Followup to #15436
|
|
|
|
| |
I don't think anyone uses it.
|
|
|
|
|
| |
https://mesonbuild.com/Release-notes-for-0-54-0.html#ninja-version-requirement-bumped-to-17
https://github.com/mesonbuild/meson/issues/6867
|
|
|
|
|
| |
Since clang was updated to 9.0.1 libFuzzer has been exiting with 72
when it's run with timeout. Let's pass -max_total_time to it instead.
|
| |
|
|
|
|
|
|
|
|
| |
The compatibility issue in meson v0.53 has been fixed in v0.53.1, which
is already available through pip, so let's remove the pin for meson
introduced before.
Reverts: 514793658c499821383bdc8bbf1d33048c18dd40
|
|
|
|
|
|
| |
Let's make sure we can test systemd-repart properly
(And while we are at it, also test cryptsetup-pkcs#11)
|
|
|
|
|
|
|
|
| |
Latest meson doesn't work with older python 3.5, which is present on
Ubuntu 16.04. Let's pin in to the latest working version (0.52.1) until
we properly bump all necessary Ubuntu images to 18.04.
See: https://github.com/mesonbuild/meson/issues/6427
|
|
|
|
|
|
|
| |
This avoids nasty race conditions between dnf/apt-get and unfinished
population of /tmp (among other things), as `docker exec` allows commands
to run before the system is fully booted (i.e. initializing/starting
state reported by `systemctl is-system-running`).
|
|
|
|
|
|
|
|
| |
Judging by https://travis-ci.org/systemd/systemd/jobs/604425785
(where the script failed with "tools/coverity.sh: line 45: python: command not found")
python-unversioned-command is no longer installed by default with python2.
Given that it's not the first time python has vanished and it's not clear
what exactly should be installed to make sure it's there, let's just use jq instead.
|
|
|
|
| |
"We removed some cahing related code that auth used and caused problems"
|
|
|
|
|
|
|
| |
I was informed that fuzzit-1.1 is going to be deprecated soon. Generally
the latest version isn't recommened because it's still in beta and theoretically
might be backwards incompatible but let's try rolling forward to avoid PRs
like this going forward. We can always roll it back :-)
|
|
|
|
|
|
|
|
| |
Now that v243 is out, the script has been pulled by forks that are
activated on Travis CI. As a result, all those forks have started to send
their fuzzers to Fuzzit inadvertantly consuming our CPUs along the way.
Let's prevent this by bailing out early if the script is run outside of
the systemd repository.
|
|
|
|
|
|
|
|
| |
It's just a follow-up to https://github.com/systemd/systemd/pull/13281
that should make it a little bit easier to make sense of
MSan reports.
https://clang.llvm.org/docs/MemorySanitizer.html#origin-tracking
|
|
|
|
|
| |
Now that the ids are gone, we can generate commands simply
using names as we go
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Let's drop the tests we also run on CentOS CI to free up some resources
for something more useful.
|
|
|
|
|
| |
Not that `journalctl --flush` is no longer flaky, it should be
safe to bring the test back.
|
|
|
|
| |
Now that 2eb1c19881678851a7e is merged it should be safe.
|
| |
|
|
|
|
| |
object-size and float-cast-overflow
|
|
|
|
| |
to make it easier to make sense of them
|
| |
|
| |
|
|
|
|
| |
in preparation for adding more ASan options
|
|
|
|
|
|
| |
This should help to silence UBSan reports mentioned in
https://github.com/systemd/systemd/pull/12771#issuecomment-502139157
for now.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
includes two travis ci steps:
1) Every pull-request/push all fuzzing targets will do a quick
sanity run on the generated corpus and crashes (via Fuzzit)
2) On a daily basis the fuzzing targets will be compiled (from
master) and will and their respectible fuzzing job on Fuzzit
will be updated to the new binary.
|