summaryrefslogtreecommitdiff
path: root/travis-ci
Commit message (Collapse)AuthorAgeFilesLines
* 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-214-7/+51
|\ \ | | | | | | 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-204-4/+50
| | | | | | | | | | | | 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.
* | | tests: set NSPAWN_TIMEOUT and QEMU_TIMEOUT explicitlyEvgeny Vereshchagin2019-05-141-2/+3
|/ / | | | | | | | | | | | | | | These were never set explictily because we relied on Travis CI canceling a job if it's been stuck for 10 minutes. Now that the script is run on Azure Pipelines (where the default timeout is 60 minutes) we should limit the script manually to avoid waiting for an hour for broken jobs to finish.
* | tests: make fuzzbuzz.sh compatible with Azure PiplinesEvgeny Vereshchagin2019-05-141-2/+8
| |
* | travis: make the ASan+UBSan stage compatible with Azure PipelinesEvgeny Vereshchagin2019-05-121-1/+2
|/
* travis: make sure that the fuzz targets can be built on OSS-FuzzEvgeny Vereshchagin2019-05-071-0/+6
|
* travis: make sure the fuzz targets can be built on FuzzBuzzEvgeny Vereshchagin2019-05-071-0/+10
|
* codespell: fix spelling errorsBen Boeckel2019-04-291-1/+1
|
* scripts: use 4 space indentationZbigniew Jędrzejewski-Szmek2019-04-124-69/+68
| | | | | | | | | | | | | | | | | | We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed. 4 sp was the most common, in particular the majority of scripts under test/ used that. Let's standarize on 4 sp, because many commandlines are long and there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp also seems to be the default indentation, so this will make it less likely that people will mess up if they don't load the editor config. (I think people often use vi, and vi has no support to load project-wide configuration automatically. We distribute a .vimrc file, but it is not loaded by default, and even the instructions in it seem to discourage its use for security reasons.) Also remove the few vim config lines that were left. We should either have them on all files, or none. Also remove some strange stuff like '#!/bin/env bash', yikes.
* travis: use /bin/systemd instead of /usr/bin/systemdEvgeny Vereshchagin2019-03-051-1/+1
| | | | Apparently systemd is in /bin now.
* travis: stop using the official upstream-systemd-ci repositoryEvgeny Vereshchagin2019-02-031-1/+2
| | | | | | | | | Turns out the key for the repository hasn't been propagated properly so let's restore the kludge that was removed in https://github.com/systemd/systemd/pull/11582. Of course it's ugly but at least it works. The issue was kind of reported to the maintainers of the repository in https://github.com/systemd/systemd/pull/11531#issuecomment-460023474.
* travis: switch to the "official" systemd-ci repositoryEvgeny Vereshchagin2019-01-291-3/+1
| | | | | | Now that add-apt-repository hasn't failed for almost two days on Semaphore it should be safe to assume that the key has been propagated properly and the repository is ready to be used on Travis CI.
* travis: also run TEST-01-BASIC with QEMU to cover udevd and so onEvgeny Vereshchagin2018-12-291-0/+5
|
* travis: pass $TRAVIS when running the tests so that they can be skipped properlyEvgeny Vereshchagin2018-12-291-1/+1
|
* travis: merge RUN_CLANG into RUNEvgeny Vereshchagin2018-12-291-8/+5
| | | | | They are basically the same except that a couple of environment variables have to be passed for building systemd with clang.
* test: don't run TEST-01-BASIC in unprivileged containers on Travis CIEvgeny Vereshchagin2018-12-241-1/+1
|
* travis: add another stage to really run everything under ASan+UBsanEvgeny Vereshchagin2018-12-241-0/+19
| | | | | This should help to catch issues like https://github.com/systemd/systemd/issues/11253 and https://github.com/systemd/systemd/issues/11251.
View Lorry Controller Status