summaryrefslogtreecommitdiff
path: root/travis-ci/managers
Commit message (Collapse)AuthorAgeFilesLines
* travis: enable fuzzer regression tests under sanitizersFrantisek Sumsal2020-05-221-1/+4
|
* fuzzit: turn on the pointer-overflow checkEvgeny Vereshchagin2020-05-201-3/+2
| | | | | Now that https://github.com/systemd/systemd/issues/15583 is gone, it should be safe to turn it on.
* ci: install fdisk on DebianEvgeny Vereshchagin2020-05-141-0/+1
| | | | | | | 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.
* install libzstd-dev for CI buildsNorbert Lange2020-05-041-1/+3
|
* fuzzit: make the submit phase a bit more robustFrantisek Sumsal2020-04-241-2/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* tree-wide: fix spelling errorsFrantisek Sumsal2020-04-211-1/+1
| | | | | | Based on a report from Fossies.org using Codespell. Followup to #15436
* ci: turn off FuzzBuzzEvgeny Vereshchagin2020-03-301-5/+0
| | | | I don't think anyone uses it.
* travis: install ninja with pipEvgeny Vereshchagin2020-03-301-2/+2
| | | | | https://mesonbuild.com/Release-notes-for-0-54-0.html#ninja-version-requirement-bumped-to-17 https://github.com/mesonbuild/meson/issues/6867
* ci: pass max_total_time to libFuzzerEvgeny Vereshchagin2020-02-181-1/+1
| | | | | 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.
* ci: add new dependencies to CILennart Poettering2020-01-284-2/+4
|
* test: unpin meson from v0.52.1Frantisek Sumsal2020-01-252-6/+2
| | | | | | | | 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
* ci: add dependencies for repart + cryptsetup's pkcs#11 supportLennart Poettering2020-01-204-2/+12
| | | | | | Let's make sure we can test systemd-repart properly (And while we are at it, also test cryptsetup-pkcs#11)
* test: pin meson to 0.52.1 for fuzzit/fuzzbuzzFrantisek Sumsal2020-01-082-2/+6
| | | | | | | | 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
* travis: wait for the container to fully boot upFrantisek Sumsal2019-12-312-2/+8
| | | | | | | 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`).
* coverity: replace python with jqEvgeny Vereshchagin2019-10-301-1/+1
| | | | | | | | 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.
* fuzzit: export the API key instead of using `auth`Evgeny Vereshchagin2019-09-121-3/+1
| | | | "We removed some cahing related code that auth used and caused problems"
* travis: switch to the latest version of the fuzzit CLIEvgeny Vereshchagin2019-09-071-5/+5
| | | | | | | 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 :-)
* travis: protect the systemd organization on Fuzzit from forksv243.1Evgeny Vereshchagin2019-09-061-1/+5
| | | | | | | | 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.
* fuzzit: get MSan to track originsEvgeny Vereshchagin2019-08-091-1/+1
| | | | | | | | 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
* fuzzit: collapse a series of commandsEvgeny Vereshchagin2019-08-081-64/+2
| | | | | Now that the ids are gone, we can generate commands simply using names as we go
* fuzzit: switch to a new organizationEvgeny Vereshchagin2019-08-081-32/+32
|
* fuzzit: unleash MSan on all the fuzzersEvgeny Vereshchagin2019-08-071-1/+38
|
* fuzzit: ignore library versionYu Watanabe2019-07-231-1/+1
|
* Free up some resources on Azure PipelinesEvgeny Vereshchagin2019-07-171-59/+0
| | | | | Let's drop the tests we also run on CentOS CI to free up some resources for something more useful.
* tests: run TEST-01-BASIC under ASAN+UBSan againEvgeny Vereshchagin2019-07-161-3/+1
| | | | | Not that `journalctl --flush` is no longer flaky, it should be safe to bring the test back.
* tests: turn on the "object-size" UBSan check on FuzzitEvgeny Vereshchagin2019-07-111-2/+2
| | | | Now that 2eb1c19881678851a7e is merged it should be safe.
* test: install missing dependencies for CIsFrantisek Sumsal2019-07-082-1/+2
|
* travis: turn on all default UBSan checks except for pointer-overflow, ↵Evgeny Vereshchagin2019-06-171-5/+4
| | | | object-size and float-cast-overflow
* fuzzit: sort UBSan checks alphabeticallyEvgeny Vereshchagin2019-06-171-1/+1
| | | | to make it easier to make sense of them
* travis: turn on nonnull-attribute on FuzzitEvgeny Vereshchagin2019-06-151-1/+1
|
* travis: add more ASan optionsEvgeny Vereshchagin2019-06-151-1/+3
|
* travis: clean up bash variables a bitEvgeny Vereshchagin2019-06-151-6/+8
| | | | in preparation for adding more ASan options
* travis: use UBSan checks from OSS-FuzzEvgeny Vereshchagin2019-06-151-2/+9
| | | | | | This should help to silence UBSan reports mentioned in https://github.com/systemd/systemd/pull/12771#issuecomment-502139157 for now.
* travis: turn on UBSan on FuzzitEvgeny Vereshchagin2019-06-151-1/+1
|
* travis: add 5 more fuzz targetsEvgeny Vereshchagin2019-06-141-2/+10
|
* Continuous Fuzzing Integration with FuzzitJeka Pats2019-06-141-0/+60
| | | | | | | | | | 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.
* Merge pull request #12617 from mbiebl/skip-test-bpf-containersEvgeny Vereshchagin2019-05-291-1/+1
|\ | | | | test-bpf: skip test when run inside containers
| * travis: set the `container` env variable explicitlyFrantisek Sumsal2019-05-191-1/+1
| | | | | | | | | | | | | | | | As we build a custom Docker image, we need to ensure that systemd correctly detects it's running in a container. One can simply do this directly in a Dockerfile (ENV container docker) or when starting the container (-e container=docker). For the sake of readability, let's pick the latter approach here.
* | Merge pull request #12510 from keszybz/test-directivesYu Watanabe2019-05-213-7/+50
|\ \ | | | | | | test: run check-directives.sh as part of the test suite
| * | travis: use variable to avoid one callZbigniew Jędrzejewski-Szmek2019-05-201-1/+1
| | |
| * | tests: install perl for CIZbigniew Jędrzejewski-Szmek2019-05-203-4/+49
| | | | | | | | | | | | It is useful for various tests (test-directives, test-udev, …).
| * | test: run check-directives.sh as part of the test suiteZbigniew Jędrzejewski-Szmek2019-05-202-2/+0
| | |
* | | Merge pull request #12519 from keszybz/man-on-demandYu Watanabe2019-05-213-3/+3
|\ \ \ | |_|/ |/| | Build man pages on demand only
| * | meson: default to -Dman=false to make development quickerZbigniew Jędrzejewski-Szmek2019-05-093-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | This makes the default build much quicker. If people are building systemd for packaging or actual installation, they probably need to set some more options anyway (-Ddns-servers=, -Dntp-servers=), so adding -Dman=true is not a big burden. For CIs configured locally, -Dman=true is added to restore status quo ante.
* | | tests: catch broken fuzz targets as early as possibleEvgeny Vereshchagin2019-05-191-1/+1
| |/ |/| | | | | See https://github.com/google/oss-fuzz/pull/2419.
* | Merge pull request #12515 from evverx/fix-fuzzers-in-local-modeZbigniew Jędrzejewski-Szmek2019-05-161-0/+11
|\ \ | | | | | | travis: make sure the fuzzers can be built in "local" mode
| * | tests: make fuzzbuzz.sh compatible with Azure Pipelines againEvgeny Vereshchagin2019-05-141-0/+2
| | | | | | | | | | | | | | | | | | | | | Now that https://github.com/systemd/systemd/pull/12542 is merged, fuzzbuzz.sh should be changed a little bit to make it work on Azure Pipelines. We can no longer assume that source repositories are added "automagically" by Travis CI or that PATH is set properly.
| * | travis: make sure the fuzzers can be built in "local" modeEvgeny Vereshchagin2019-05-141-0/+9
| | |
* | | tests: make docker-run and helper.py happy by not using colons in filenamesEvgeny Vereshchagin2019-05-161-1/+7
| | | | | | | | | | | | This should address https://github.com/google/oss-fuzz/issues/2428
* | | tests: turn on the QEMU part in the Xenial jobEvgeny Vereshchagin2019-05-141-1/+3
| | | | | | | | | | | | | | | | | | | | | The test has been flaky since varlink was merged. Let's not annoy people with the test that fails more often than not. It should be OK because the same test is run on Arch.
View Lorry Controller Status