summaryrefslogtreecommitdiffstats
path: root/test (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #10736 from yuwata/coredump-commentLennart Poettering2018-11-121-0/+0
|\ | | | | fuzz: fix oss-fuzz#8658
| * fuzz: add testcase of oss-fuzz#8658Yu Watanabe2018-11-121-0/+0
| |
* | Merge pull request #10731 from yuwata/fix-oss-fuzz-11344Lennart Poettering2018-11-121-0/+6
|\ \ | |/ |/| Fixes oss-fuzz#11344
| * fuzz: add testcase of oss-fuzz#11344Yu Watanabe2018-11-111-0/+6
| |
* | Merge pull request #10669 from danderson/networkd-6rdYu Watanabe2018-11-125-6/+34
|\ \ | | | | | | networkd: add 6rd support for sit netdevs
| * | Add a networkd test for 6rd interface creation.David Anderson2018-11-103-6/+25
| | | | | | | | | | | | | | | | | | Unfortunately we can't check the 6rd attribute, because it's not exposed in /sys or anywhere other than netlink... But at least we can check that networkd brings up an interface that looks right.
| * | Add 6rd directive to the netdev fuzzing corpus.David Anderson2018-11-102-0/+9
| | |
* | | Merge pull request #10694 from evverx/udev-test-in-containerYu Watanabe2018-11-121-7/+18
|\ \ \ | | | | | | | | udev-test: remove a check for whether the test is run in a container
| * | | udev-test: skip the test only if it can't setup its environmentEvgeny Vereshchagin2018-11-101-3/+21
| | | | | | | | | | | | | | | | This is basically a replacement for 0eb3cc88504b5d8f74.
| * | | udev-test: remove a check for whether the test is run in a containerEvgeny Vereshchagin2018-11-091-7/+0
| | | | | | | | | | | | | | | | It's too broad a check that prevents the test from running on Travis CI.
* | | | fuzz: add testcase of oss-fuzz#10734Yu Watanabe2018-11-111-0/+0
| | | |
* | | | fuzz: add testcase of already fixed issue 10908Yu Watanabe2018-11-111-0/+9
| |_|/ |/| |
* | | fuzz: add testcase of oss-fuzz#11345Yu Watanabe2018-11-111-0/+2
| | |
* | | fuzz: add testcase for oss-fuzz#11324Yu Watanabe2018-11-101-0/+0
| |/ |/|
* | fuzz: add testcases of recent issuesYu Watanabe2018-11-092-0/+7
|/
* fuzz: add a testcase for oss-fuzz#11285Yu Watanabe2018-11-081-0/+2
|
* fuzz: add more testcases of already fixed issue about multiple netdev kindYu Watanabe2018-11-085-0/+0
| | | | | | | This adds testcases of oss-fuzz#11286, oss-fuzz#11287, oss-fuzz#11296, oss-fuzz#11297, and oss-fuzz#11299. The issue was fixed by 62facba19ad645df7fb425ce170bdbda208b303c.
* fuzz: add testcases for oss-fuzz#11279 and #11280Yu Watanabe2018-11-072-0/+0
|
* test: missing "die"Yu Watanabe2018-11-071-1/+1
| | | | Follow-up for a41ff38b0999fb83464309a29b8f39450b8d4b85.
* tests: add a couple of files containing all the sections and directivesEvgeny Vereshchagin2018-11-062-0/+340
| | | | | | | | | | | | | | | This should help the fuzzers to discover code paths faster. In case anyone is interested, they were generated with the following script ``` perl -aF'/[\s,]+/' -ne ' if (my ($s, $d) = ($F[0] =~ /^([^\s\.]+)\.([^\s\.]+)$/)) { $d{$s}{$d} = 1; } END { while (my ($key, $value) = each %d) { printf "[%s]\n%s\n", $key, join("\n", keys(%$value)) }}' ``` by passing src/network/networkd-network-gperf.gperf and src/network/netdev/netdev-gperf.gperf to it.
* tests: replace AdActorSysPrio with AdActorSystemPriorityEvgeny Vereshchagin2018-11-061-1/+1
| | | | This is a follow-up to https://github.com/systemd/systemd/pull/10653.
* tests: add a reporoducer for https://github.com/systemd/systemd/issues/10639Evgeny Vereshchagin2018-11-061-0/+8
|
* tests: add some data that can be fed to fuzz-network-parserEvgeny Vereshchagin2018-11-0653-0/+384
|
* tests: add a reproducer for https://github.com/systemd/systemd/issues/10629Evgeny Vereshchagin2018-11-061-0/+10
|
* networkd: make netdev_load_one "public" and add a fuzzer for itEvgeny Vereshchagin2018-11-0628-0/+211
|
* networkd: cleanup for #10542Tobias Jungel2018-11-061-1/+1
| | | | fixes: 53b1f7d
* Merge pull request #10606 from yuwata/udev-testsLennart Poettering2018-11-0520-14/+97
|\ | | | | test: mask hwdb-update.services in most tests
| * test: drop 'After=multi-user.target' from most of testsuite.serviceYu Watanabe2018-11-0313-13/+1
| |
| * test: mask several unnecessary servicesYu Watanabe2018-11-0312-0/+95
| | | | | | | | This may make CIs run faster.
| * test: increase timeout for TEST-17-UDEV-WANTSYu Watanabe2018-11-031-1/+1
| | | | | | | | | | As the test randomly fails with timeout. This may fix #10274.
* | Merge pull request #10618 from yuwata/fix-10615Lennart Poettering2018-11-052-0/+3
|\ \ | | | | | | network: fix several issues in config parser
| * | test: UseRoutes= and UseTimezone= need to be in [DHCP] sectionYu Watanabe2018-11-031-0/+2
| | |
| * | test-network: wait after removing linksYu Watanabe2018-11-031-0/+1
| |/ | | | | | | | | | | After ec6a47044a2ab321ae6427ce0d9fa3f6a17544a8, networkd starts soon after removing links used by previous test. That causes some racy situation of removing links and detecting links by networkd.
* | tests: also use lsmod to check whether modules are available (#10634)Evgeny Vereshchagin2018-11-051-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's not entirely impossible to screw something up playing with kernel modules on a Saturday evening :-) This PR fixes a scenario where a module has been loaded into the kernel but the module itself has been removed from the disk. ``` $ lsmod | grep wireg wireguard 225280 0 ip6_udp_tunnel 16384 1 wireguard udp_tunnel 16384 1 wireguard $ modprobe wireguard modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.18.16-200.fc28.x86_64 $ sudo ./systemd-networkd-tests.py NetworkdNetDevTests.test_wireguard ... modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.18.16-200.fc28.x86_64 test_wireguard (__main__.NetworkdNetDevTests) ... unexpected success ---------------------------------------------------------------------- Ran 1 test in 5.152s FAILED (unexpected successes=1) ``` This is a follow-up to https://github.com/systemd/systemd/pull/10625.
* | tests: add a basic test for wireguard (#10631)Evgeny Vereshchagin2018-11-032-2/+29
|/
* tests: mark a few tests as expected failures when the required modules ↵Evgeny Vereshchagin2018-11-031-0/+14
| | | | | | aren't available Closes https://github.com/systemd/systemd/issues/10617.
* tests: make NetworkdNetWorkTests.test_routing_policy_rule pass on CentOSEvgeny Vereshchagin2018-11-021-1/+1
| | | | | Depending on the content of /etc/iproute2/rt_dsfield, ip can print either `0x08` or `throughput` as was shown in https://github.com/systemd/systemd/issues/10617#issuecomment-435200859.
* networkd: add missing bonding options (#10542)Tobias Jungel2018-11-022-8/+16
| | | | | | | | | Add support for bonding options system prio, port key and actor system mac. These options exist in the linux kernel since 4.2 (torvalds/linux@171a42c38c6e1) Details: https://www.kernel.org/doc/Documentation/networking/bonding.txt
* tests: add an lldp fuzzerEvgeny Vereshchagin2018-10-293-0/+0
| | | | | | | | | I went through my antique collection of fuzzers the other day to see which ones I hadn't sent upstream yet. This one seems to be nice to have and ready to be merged. As far as I can tell, it hasn't managed to find anything useful yet, but it's better to be safe than sorry especially when it comes to networking code :-)
* Merge pull request #10378 from poettering/json-fuzz-fixZbigniew Jędrzejewski-Szmek2018-10-251-0/+9
|\ | | | | json: a comprehensive fix for oss-fuzz#10908
| * fuzz: add test from oss-fuzz#10908Lennart Poettering2018-10-181-0/+9
| | | | | | | | https://oss-fuzz.com/download?testcase_id=5639441482252288
* | test: create /dev/null in test-udev.plYu Watanabe2018-10-231-1/+2
| |
* | tests: allow passing log_level via an environment variable (#10490)Evgeny Vereshchagin2018-10-231-1/+1
| |
* | tests: update networkd-test.py to use resolvectl instead of systemd-resolve ↵Michael Biebl2018-10-231-10/+10
| | | | | | | | | | (#10486) The latter is merely a compat symlink nowadays.
* | fuzz: add testcase of oss-fuzz#11019Yu Watanabe2018-10-181-0/+0
| |
* | tests: clean up again after running tests (#10446)Lennart Poettering2018-10-183-3/+11
|/ | | | | | | | | | | | | | | | | Currently, if I run the full "run-integration-tests.sh" script it will fail on my machine because it fills up /var/tmp whith just too much crap until the disk is full. Let's make sure that "run-integration-tests.sh" cleans up after every test. For that change the make targets to run from "clean setup run" to "clean setup run clean" — except that that doesn't work since make is smart enough to realize that the same target appears twice on the command line and will only execute it once. Let's fix that by defining another target "clean-again" which is just like "clean", but allows us to be added to the same command line a second time. Then, let's build with "clean setup run clean-again" and all is good. While we are at it, let's also add .PHONY where appropriate, after all these all are phony targets.
* core: implement per unit journal rate limitingAnita Zhang2018-10-181-0/+2
| | | | | | | | | Add LogRateLimitIntervalSec= and LogRateLimitBurst= options for services. If provided, these values get passed to the journald client context, and those values are used in the rate limiting function in the journal over the the journald.conf values. Part of #10230
* shared: add %g, %G specifiers for group / gid (#10368)Davide Cavalca2018-10-135-10/+14
|
* tests: fix fallthrough condition for supplementary groupsDavide Cavalca2018-10-116-16/+16
|
* tests: pass halt_on_error=1 to UBSanEvgeny Vereshchagin2018-10-111-1/+1
| | | | | | | | | | | | | | | By default, UBSan neither crashes nor exits with a non-zero exit code when undefined behavior has been detected. This is problematic because it makes it much harder to catch issues like https://github.com/systemd/systemd/issues/10346, https://github.com/systemd/systemd/issues/10347, and https://github.com/systemd/systemd/issues/10333. In fact, those issue were found just because I decided to grep the test log, which isn't something that I normally do :-) As it turns out, the only way to make UBSan signal that something is wrong that works more or less reliably everywhere is to pass halt_on_error=1 (though, it's probably worth noting that it's currently not set for PID1 in order not to trigger kernel panics). See https://reviews.llvm.org/D35085#804183 and https://chromium.googlesource.com/chromium/src/testing/libfuzzer/+/HEAD/reference.md