summaryrefslogtreecommitdiff
path: root/.travis.yml
Commit message (Collapse)AuthorAgeFilesLines
* coverity: switch back to Fedora 31Evgeny Vereshchagin2020-07-121-1/+1
| | | | | Apparently 6 days ago fedora:latest started to point to fedora:32, which comes with gcc-10. Coverity doesn't support it yet.
* ci: bring back Coverity part 2Evgeny Vereshchagin2020-06-241-0/+1
| | | | | | | | | | | | | | | It's just a follow-up to https://github.com/systemd/systemd/pull/16266. Currently the Coverity stage is failing with ``` Starting container systemd-fedora-latest 2db425228e1addbce607c7e47e492a0faef2c2c4e85701c6c239a50de95944eb Error: No such container: bash The command "$CI_MANAGERS/fedora.sh SETUP" failed and exited with 1 during . Your build has been stopped. ``` https://travis-ci.org/github/systemd/systemd/builds/701798193
* ci: bring back CoverityEvgeny Vereshchagin2020-06-241-0/+1
| | | | | | | | | | | | | Looks like DOCKER_EXEC got lost somewhere along the way, which, in turn, caused the "coverity" job to fail with ``` $ $DOCKER_EXEC meson cov-build -Dman=false Command 'meson' not found, but can be installed with: apt install meson Please ask your administrator. ``` https://travis-ci.org/github/systemd/systemd/builds/701705788
* travis: use a matrix for similar jobsFrantisek Sumsal2020-06-161-116/+71
|
* github: move the clang/gcc build check to GH ActionsFrantisek Sumsal2020-06-111-42/+0
| | | | | Travis CI is getting overloaded, so let's move some load over to GitHub Actions.
* travis: bump Ubuntu release to BionicFrantisek Sumsal2020-06-111-1/+1
|
* travis: replace set (+|-)e with travis_terminateFrantisek Sumsal2020-06-111-13/+4
| | | | | It looks nicer and works around https://travis-ci.community/t/exit-0-cannot-exit-successfully-on-arm/5731/
* travis: check build with various compiler optionsFrantisek Sumsal2020-06-091-0/+42
| | | | | | | 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.
* turn off fuzzitEvgeny Vereshchagin2020-06-041-22/+0
| | | | | It seems it went down yesterday and it's not clear how long it will take to bring it back.
* travis: add missing closing quote signYu Watanabe2019-11-241-1/+1
| | | | Fixes #14127.
* travis: skip the right stageEvgeny Vereshchagin2019-09-071-1/+1
| | | | | It's just a follow-up to https://github.com/systemd/systemd/pull/13493. The stage is called "Fuzzit-Regression" now.
* travis: switch to the latest version of the fuzzit CLIEvgeny Vereshchagin2019-09-071-4/+4
| | | | | | | 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 :-)
* coverity: stop setting _Float*Evgeny Vereshchagin2019-06-211-2/+1
| | | | Should address https://github.com/systemd/systemd/issues/12854
* travis: always run the "Build & test" stage firstEvgeny Vereshchagin2019-06-141-0/+3
| | | | | | 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.
* travis: skip the Fuzzit-Sanity stage when it's run by cronEvgeny Vereshchagin2019-06-141-0/+3
|
* travis: run Coverity after Fuzzit-FuzzingEvgeny Vereshchagin2019-06-141-3/+3
| | | | | | | | | | | 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
* Continuous Fuzzing Integration with FuzzitJeka Pats2019-06-141-0/+19
| | | | | | | | | | 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.
* tests: move the FuzzBuzz stage from Travis CI to Azure PipelinesEvgeny Vereshchagin2019-05-141-7/+0
|
* travis: move the Xenial phase to Azure PipelinesFrantisek Sumsal2019-05-131-7/+0
|
* travis: make sure the fuzz targets can be built on FuzzBuzzEvgeny Vereshchagin2019-05-071-0/+7
|
* travis: add another stage to really run everything under ASan+UBsanEvgeny Vereshchagin2018-12-241-0/+7
| | | | | This should help to catch issues like https://github.com/systemd/systemd/issues/11253 and https://github.com/systemd/systemd/issues/11251.
* travis: switch to Debian TestingEvgeny Vereshchagin2018-12-241-38/+20
| | | | | Turns out Fedora is the least stable distribution in terms of downloading packages. Debian is much more stable so let's use it.
* travis: use xenial instead of trustyEvgeny Vereshchagin2018-12-231-0/+1
| | | | | This should also fix an issue mentioned in https://github.com/systemd/systemd/pull/11196#issuecomment-448123946.
* travis: also compile systemd on Debian TestingEvgeny Vereshchagin2018-12-071-0/+18
| | | | This should help to catch issues like https://github.com/systemd/systemd/issues/11075
* travis: also run the tests built with clang under ASan+UBsanEvgeny Vereshchagin2018-12-041-0/+18
|
* travis: also build systemd with clangEvgeny Vereshchagin2018-12-011-0/+18
|
* travis: use latest instead of rawhideEvgeny Vereshchagin2018-12-011-4/+4
|
* travis: run ASan job in parallel with the standard oneFrantisek Sumsal2018-11-081-2/+1
|
* travis: move the ASan part into a separate stageEvgeny Vereshchagin2018-11-081-0/+19
|
* travis: make the directory with coverity tools available in a containerEvgeny Vereshchagin2018-11-071-2/+2
| | | | | | | | | 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.
* travis: overwrite test-capability with a simple script that is just skippedEvgeny Vereshchagin2018-11-071-4/+1
| | | | | so that it will be possible to work on the test failure and try to make Travis CI work at the same time.
* travis: run Coverity on a more stable Fedora releaseFrantisek Sumsal2018-11-061-1/+1
|
* travis: move Docker setup to a separate scriptFrantisek Sumsal2018-11-061-23/+12
| | | | This should make debugging somewhat easier
* travis: rewrite .travis.yml and re-enable Travis CI for FedoraFrantisek Sumsal2018-11-061-62/+78
|
* Merge pull request #9193 from keszybz/coverityLennart Poettering2018-06-141-1/+1
|\ | | | | Coverity support for glibc-2.27
| * travis: add defines for _Float64/_Float64x/_Float32/_Float32xZbigniew Jędrzejewski-Szmek2018-06-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | $ 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+.
* | travis: stop sending notifications to the authors of randomly chosen commitsEvegeny Vereshchagin2018-06-071-1/+0
|/
* travis: use Travis CI only for running scheduled Coverity scansMichal Sekletar2018-06-041-112/+8
| | | | | 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.
* Enable ccache and mount it into the build/test container.Omer Katz2018-05-221-2/+4
|
* Rename scripts/coverity.sh to tools/coverity.shZbigniew Jędrzejewski-Szmek2018-03-121-1/+1
| | | | | There are only two files in tools/, I don't think we need a separate directory for them.
* Integration of Travis CI and Coverity Scan Analysis (#7691)Marek Čermák2018-01-111-8/+174
| | | | | | | | | | | | - 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
* remove gudev and gtk-docKay Sievers2015-06-031-2/+2
| | | | | The library moved to: https://git.gnome.org/browse/libgudev/
* mount: use libmount to enumerate /proc/self/mountinfoChris Leech2014-11-281-1/+1
| | | | | This lets libmount add in user options from /run/mount/utab, like _netdev which is needed to get proper ordering against remote-fs.target
* test: Make testing work on systems without or old systemdHolger Hans Peter Freyther2013-08-221-2/+3
| | | | | | | | | | | | | | * 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.
* travis: Add a travis.yml for doing CI after commitsHolger Hans Peter Freyther2013-07-151-0/+13
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.
View Lorry Controller Status