| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Should address https://github.com/systemd/systemd/issues/12854
|
|
|
|
|
|
| |
Now that the other stages are explicitly listed in the "stages"
section, we should include "Built & test" there to make sure
it's run first.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Coverity is unpredictable and, according to a notification I received
yeserday, it will be upgraded on June 17. During the upgrade
it might be offline for 3 days, af far as I understand. Anyway, Travis
stops as soon as a stage fails so it makes sense to put stages that
are likely to fail at the end so that the others have a chance to
do what they are supposed to do.
https://community.synopsys.com/s/topic/0TO2H0000001CN7WAM/coverity-scan-status
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This should help to catch issues like https://github.com/systemd/systemd/issues/11253
and https://github.com/systemd/systemd/issues/11251.
|
|
|
|
|
| |
Turns out Fedora is the least stable distribution in terms of
downloading packages. Debian is much more stable so let's use it.
|
|
|
|
|
| |
This should also fix an issue mentioned in
https://github.com/systemd/systemd/pull/11196#issuecomment-448123946.
|
|
|
|
| |
This should help to catch issues like https://github.com/systemd/systemd/issues/11075
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Otherwise `coverity.sh build` will fail with
```
find: '/var/tmp/coverity-scan-analysis': No such file or directory
```
See https://travis-ci.org/systemd/systemd/jobs/451683385.
|
|
|
|
|
| |
so that it will be possible to work on the test failure and try to make
Travis CI work at the same time.
|
| |
|
|
|
|
| |
This should make debugging somewhat easier
|
| |
|
|\
| |
| | |
Coverity support for glibc-2.27
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
$ build/test-sizeof
...
_Float128 → 128 bits, signed
_Float64 → 64 bits, signed
_Float64x → 128 bits, signed
_Float32 → 32 bits, signed
_Float32x → 64 bits, signed
...
This seems to be enough to make coverity work with glibc-2.27 found in Fedora 28+.
|
|/ |
|
|
|
|
|
| |
Building and testing of systemd on Fedora Rawhide is now handled by
dedicated Fedora CI. We don't need to duplicate this in Travis CI.
|
| |
|
|
|
|
|
| |
There are only two files in tools/, I don't think we need a separate
directory for them.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Coverity scan analysis tasks run as scheduled cron jobs
- Stage separation for Build, Test and Coverity scan phase
- Travis CI now uses Fedora container to build and run tests
- Containers are accessible from Docker Hub and failed builds
can be reproduced and examined
- coverity.sh: separate build and upload
|
|
|
|
|
| |
The library moved to:
https://git.gnome.org/browse/libgudev/
|
|
|
|
|
| |
This lets libmount add in user options from /run/mount/utab, like
_netdev which is needed to get proper ordering against remote-fs.target
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Introduce a macro to conditionally execute tests. This avoids
skipping the entire test if some parts require systemd
* Skip the journal tests when no /etc/machine-id is present
* Change test-catalog to load the catalog from the source directory
of systemd.
* /proc/PID/comm got introduced in v2.6.33 but travis is still
using v2.6.32.
* Enable make check and make distcheck on the travis build
* Use -D"CATALOG_DIR=STR($(abs_top_srcdir)/catalog)" as a STRINGIY
would result in the path '/home/ich/source/linux' to be expanded
to '/home/ich/source/1' as linux is defined to 1.
|
|
Instruct travis-ci to build systemd and create a tarball. In case
of an error travis-ci will complain on IRC. The systemd testsuite
currently requires the host to have a recent version of systemd
installed and running. This is not the case for the Ubuntu VM of
travis-ci. This means make check and make distcheck will result in
a build failure and to avoid this these commands are not executed.
This requires a one time configuration on travis-ci for the repo
on github by the owner of the repo.
|