| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
| |
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.
|
| |\
| |
| | |
test-bpf: skip test when run inside containers
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| | |
| | | |
test: run check-directives.sh as part of the test suite
|
| | | | |
|
| | | |
| | |
| | |
| | | |
It is useful for various tests (test-directives, test-udev, …).
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
Build man pages on demand only
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |/
|/|
| |
| | |
See https://github.com/google/oss-fuzz/pull/2419.
|
| |\ \
| | |
| | | |
travis: make sure the fuzzers can be built in "local" mode
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This should address https://github.com/google/oss-fuzz/issues/2428
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Apparently systemd is in /bin now.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
They are basically the same except that a couple of environment variables
have to be passed for building systemd with clang.
|
| | |
|
| |
|
|
|
| |
This should help to catch issues like https://github.com/systemd/systemd/issues/11253
and https://github.com/systemd/systemd/issues/11251.
|
| |
|
|
|
| |
This should also fix an issue mentioned in
https://github.com/systemd/systemd/pull/11196#issuecomment-448123946.
|
| |
|
|
|
|
| |
To judge from https://api.travis-ci.org/v3/job/465547774/log.txt,
overlayfs on Travis CI is having trouble delivering inotify events,
which is why `test-path` and `test-event` are failing there.
|
| |
|
|
|
|
| |
Turns out some tests like `test-execute` are tightly coupled with
systemd as PID1 (which should be fixed of course). In the meantime,
let's see how it goes.
|
| |
|
|
| |
This should help to catch issues like https://github.com/systemd/systemd/issues/11075
|
| |
|
|
| |
See https://clang.llvm.org/docs/AddressSanitizer.html#symbolizing-the-reports
|
| | |
|
| | |
|
| |
|
|
|
|
| |
New features are constantly added to networkd. Apparently, not everybody
knows that the "directives" files should be updated too to make
the fuzzers aware of them.
|
| |
|
|
|
|
| |
Let's not bother contributors with spurious failures nobody can't
seem to reproduce. There is an issue about that where we're trying
to figure out what's going on: https://github.com/systemd/systemd/issues/10696.
|
| | |
|
| |
|
|
| |
This should somewhat address https://github.com/systemd/systemd/issues/10696.
|
| | |
|
| | |
|
| | |
|
| | |
|
