Commit Graph

22 Commits

Author SHA1 Message Date
Lennart Poettering 0edd431e15 ci: add new dependencies to CI 2020-01-28 22:38:22 +01:00
Frantisek Sumsal a3e42c468f test: unpin meson from v0.52.1
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: 514793658c
2020-01-25 23:14:35 +03:00
Lennart Poettering e65f29b4c6 ci: add dependencies for repart + cryptsetup's pkcs#11 support
Let's make sure we can test systemd-repart properly

(And while we are at it, also test cryptsetup-pkcs#11)
2020-01-20 17:42:03 +01:00
Frantisek Sumsal 514793658c test: pin meson to 0.52.1 for fuzzit/fuzzbuzz
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
2020-01-08 13:56:30 +03:00
Evgeny Vereshchagin 807f9a1700 fuzzit: export the API key instead of using `auth`
"We removed some cahing related code that auth used and caused problems"
2019-09-12 14:02:21 +03:00
Evgeny Vereshchagin 20c9c29c68 travis: switch to the latest version of the fuzzit CLI
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 :-)
2019-09-07 00:06:36 +03:00
Evgeny Vereshchagin 64d0f7042d travis: protect the systemd organization on Fuzzit from forks
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.
2019-09-06 02:07:37 +00:00
Evgeny Vereshchagin d4d74d0fc0 fuzzit: get MSan to track origins
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
2019-08-09 07:25:39 +00:00
Evgeny Vereshchagin 9cf19c1b30 fuzzit: collapse a series of commands
Now that the ids are gone, we can generate commands simply
using names as we go
2019-08-08 15:08:58 +00:00
Evgeny Vereshchagin a9285009b7 fuzzit: switch to a new organization 2019-08-08 15:08:52 +00:00
Evgeny Vereshchagin 688b142d39 fuzzit: unleash MSan on all the fuzzers 2019-08-07 23:09:15 +00:00
Yu Watanabe 81f33199e7 fuzzit: ignore library version 2019-07-23 23:32:33 +03:00
Evgeny Vereshchagin 0772b11cc8 tests: turn on the "object-size" UBSan check on Fuzzit
Now that 2eb1c19881 is merged it should be safe.
2019-07-11 19:37:22 +03:00
Evgeny Vereshchagin 28025ba839 travis: turn on all default UBSan checks except for pointer-overflow, object-size and float-cast-overflow 2019-06-17 23:45:36 +03:00
Evgeny Vereshchagin 5afed2fc20 fuzzit: sort UBSan checks alphabetically
to make it easier to make sense of them
2019-06-17 12:49:07 +02:00
Evgeny Vereshchagin 9bd2422ac3 travis: turn on nonnull-attribute on Fuzzit 2019-06-15 23:12:24 +02:00
Evgeny Vereshchagin f789e0b4f8 travis: add more ASan options 2019-06-15 05:19:58 +02:00
Evgeny Vereshchagin b5e1f0bdf4 travis: clean up bash variables a bit
in preparation for adding more ASan options
2019-06-15 05:19:58 +02:00
Evgeny Vereshchagin 5057d73ba1 travis: use UBSan checks from OSS-Fuzz
This should help to silence UBSan reports mentioned in
https://github.com/systemd/systemd/pull/12771#issuecomment-502139157
for now.
2019-06-15 05:19:52 +02:00
Evgeny Vereshchagin e87e6962fd travis: turn on UBSan on Fuzzit 2019-06-15 00:09:15 +02:00
Evgeny Vereshchagin 356f607aa3 travis: add 5 more fuzz targets 2019-06-14 22:06:08 +02:00
Jeka Pats 53a42e6268 Continuous Fuzzing Integration with Fuzzit
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.
2019-06-14 21:09:40 +03:00