Commit Graph

97 Commits

Author SHA1 Message Date
gson 2e07311f7f Delete trailing whitespace 2021-10-30 13:50:12 +00:00
andvar b58602814f fix typos in word "successful". 2021-09-16 22:19:10 +00:00
mrg 9c9331d392 apply this change to a a couple more tests:
---
date: 2020-07-27 09:57:44 -0700;  author: gson;  state: Exp;  lines: +6 -1;  commitid: m3HouRBlhyJQVJhC;
Skip the repeated_link_addr test by default as it causes the
evbarm-aarch64 testbed to hang (PR port-evbarm/55521), and will not be
safe to run by default even after that bug is fixed, for similar
reasons as t_repeated_updown.
---

t_repeated_mtu.sh changes the MTU, which may cause NFS to fail.
if you have NFS root, this is system killing.

t_repeated_scan.sh kills and restarts both hostapd and
wpa_supplicant.
2020-12-10 08:16:59 +00:00
mrg a29667efc0 disable these tests unless ATF_SBIN_IFCONFIG_WIFI_ENABLE=yes is
in the environment.  they change wifi configuration, restart
wpa_supplicant and hostapd, and, on broken wifi chipsets, may
hang the test run.
2020-09-08 06:11:32 +00:00
gson e665c975ab Skip the repeated_link_addr test by default as it causes the
evbarm-aarch64 testbed to hang (PR port-evbarm/55521), and will not be
safe to run by default even after that bug is fixed, for similar
reasons as t_repeated_updown.
2020-07-27 16:57:44 +00:00
jruoho 3f94c7658e Use the new "run_unsafe" atf_config_get() option also with a couple of other
tests that are known to be unsafe.
2020-07-27 07:36:19 +00:00
gson 7836998153 Instead of just skipping interfaces that are "up", skip the whole
repeated_updown test case unless explicitly enabled with "atf-run -v
run_unsafe=yes".  Gratuitously configuring interfaces "up" is no more
safe than gratuitously configuring them "down"; for example, it could
lead to accidentally connecting to an insecure network or diverting
traffic from the desired route.
2020-07-27 06:52:48 +00:00
martin e6ac0f80fe Skip interfaces that are already UP before the test starts. We can
not change state of the test host this way, it breaks e.g. test systems
with the root filesystem on NFS.
2020-07-22 05:47:24 +00:00
jruoho 671da32626 Remove the expected timeout; there is something more sinister behind the
timeouts seen on the Qemu/evbarm-aarch64 runs.
2020-07-06 10:35:00 +00:00
jruoho 7b69662fe9 Skip these also for Qemu runs as they cause panics. Point to PR kern/55451. 2020-07-03 07:03:14 +00:00
jruoho f62e6216a7 Expect a timeout for evbarm-aarch64, as seen in the recent Qemu runs. 2020-07-03 02:51:13 +00:00
jruoho 6d91546d37 Skip a few more nodes, and enable this test for Qemu runs. 2020-06-30 11:49:26 +00:00
jruoho e643f0ea97 Add a couple of tests for sequential ifconfig(8) options, incl. PR kern/41912. 2020-06-30 11:48:20 +00:00
jruoho 3e2e2a93b9 Ups. Fix shell parameter. 2020-06-27 14:04:17 +00:00
jruoho 7725c11dd6 Add also a test that writes random garbage to every ifconfig(8) option that
takes parameters. Based on quick testing, iwn(4) and wm(4) pass, but
urtwn(4) panics. Use at your own risk; in some cases, it may be possible
that horrors are written directly to the hardware.
2020-06-27 13:53:43 +00:00
jruoho 313072e773 Add a simple test case that writes random garbage to (almost) every sysctl node.
This test reproduced already at least five unique panics in a few quick runs.
The test is skipped by default as it is not likely safe even without the panics.
2020-06-27 08:50:46 +00:00
jruoho b61f0fee17 Add a basic test for enabling/disabling network interface capabilities. 2020-06-27 06:57:44 +00:00
jruoho dc018d6b62 Add test cases for different 802.11 options. These include cases for
PR kern/35045, PR kern/45745, and PR kern/55424.
2020-06-27 05:07:07 +00:00
jruoho 6232dbeb26 Use atf_pass to avoid test failure in case there are no suitable interfaces. 2020-06-27 04:15:17 +00:00
jruoho f5fa72a2a9 Test creating thousands of bridge(4)'s. Unlike with tap(4) (PR kern/55417),
this test succeeeds. It is even possible to have the ultimate ifconfig(8)
output with more than 65,000 devices.
2020-06-25 18:30:42 +00:00
jruoho 9611465bb1 Verify that PR kern/52150 is no longer present. 2020-06-25 17:08:32 +00:00
jruoho 11d78a2165 Instead of UINT_MAX + 2, test what is claimed. 2020-06-25 16:57:00 +00:00
jruoho 04cb13a856 Actually create the tap(4) with a negative device number. Doh. 2020-06-25 16:52:49 +00:00
jruoho 02dcf11b6e Reference also PR kern/52526. 2020-06-25 16:34:49 +00:00
jruoho c6ea14b7ca Fix pastos. 2020-06-25 15:43:26 +00:00
jruoho 0f5766374a Add a test case for kern/52771. 2020-06-25 15:41:40 +00:00
jruoho 77e941ddd2 Add a test case for PR kern/53410. 2020-06-25 15:01:35 +00:00
jruoho 5c3bd061a3 Add test cases for PR kern/53546 and PR kern/55417. Both are skipped as
both reproduce panics.
2020-06-25 14:24:45 +00:00
jruoho 07a6f275d7 Reference also PR kern/53860. 2020-06-25 11:26:05 +00:00
jruoho b23ebd9451 Require root privileges. 2020-06-25 10:34:34 +00:00
jruoho 08daf067e8 Fix references in comments. 2020-06-24 10:07:13 +00:00
jruoho 6ecb6de692 Add a test case for PR bin/55389. 2020-06-24 09:11:26 +00:00
martin b46551040d Skip tests where the old or the new image size seem to not fit into
the working directory.
2020-03-15 11:17:59 +00:00
martin 581b9627a8 Skip this test if the atf working directory has not enough space
for the created image.
2020-03-15 10:15:16 +00:00
martin 0c2085b2fd Fix typo 2020-03-12 18:08:54 +00:00
kre 981c4cd0ef Make most of the resize_ffs tests skip if PUFFS is not configured
in the kernel.   (nb: for this purpose, a module that is configured
to autoload counts as configured in the kernel...)
2017-10-08 21:12:27 +00:00
martin defea524bf Skip the "migrate" test on architectures not natively using MBR, it
can not work there.
2017-03-22 19:13:40 +00:00
pgoyette aec3683782 When deadbeef is treated as a 32-bit signed integer, it actually has a
negative value.  So, if the value gets written into a sysctl variable,
and then is read back, the twos-complement value is displayed.

So, when checking for the value having been written, make sure we check
for the correct value!
2016-06-17 03:55:35 +00:00
joerg c632ff2be2 Require the boot block to be used, test can't work otherwise. 2016-03-08 08:04:48 +00:00
pgoyette bc9ef90a7d I was right - the output from gpt(8) did grow an extra space character!
Fix the test to expect it.  Test now passes on my local test bed.
2015-12-27 06:53:48 +00:00
pgoyette 9328be7df7 Revert - tested using wrong test case. :( 2015-12-27 01:50:39 +00:00
pgoyette a161b63780 Update test - the attributes listed by the show command now have a space
in the comma-separated list.

This allows the test to once again pass.
2015-12-27 01:46:24 +00:00
christos 1580202168 Add test for type, set, unset 2015-12-06 00:38:30 +00:00
christos ce40c86d4c more variables 2015-12-05 18:53:29 +00:00
christos a1fb78d5a0 file shuffling 2015-12-05 18:52:11 +00:00
christos ac8087a5ab Add a migration test 2015-12-05 18:45:35 +00:00
christos cf8c4fce6c Add biosboot test 2015-12-05 14:23:41 +00:00
christos 6c37bffdde Oops + 2015-12-04 20:16:23 +00:00
christos 2d4dd9611a remove extra 2015-12-04 18:53:35 +00:00
christos 11ff782d8f Add gpt tests 2015-12-04 17:19:33 +00:00