summaryrefslogtreecommitdiff
path: root/tests/sbin
AgeCommit message (Collapse)Author
2023-03-23PR 57284: rewrite test to extract all temperaturs from all local sensorsmartin
and test them (instead of only one temperature from a tiny list of hard coded possible devices).
2022-11-30Simplify: avoid use of the explicit raw partition, MAKDEV doesmartin
all the needed magic for us already. Pointed out by kre
2022-11-29Avoid dependence on details of the MD synthesized disklabel formartin
the vnd after mounting the single filesystem image.
2022-11-21vnconfig is used in this tests, so require user root.martin
2022-11-21Adapt to recent gpt(8) change which now issues a message whenkre
the secondary GPT header is moved. Do it this way rather than just using -q to suppress the message, so the test verifies that the appropriate action was taken.
2022-11-17Restore backward compatibility of UFS2 with previous NetBSD releases bychs
disabling support in UFS2 for extended attributes (including ACLs). Add a new variant of UFS2 called "UFS2ea" that does support extended attributes. Add new fsck_ffs operations "-c ea" and "-c no-ea" to convert file systems from UFS2 to UFS2ea and vice-versa (both of which delete all existing extended attributes in the process).
2021-10-30Delete trailing whitespacegson
2021-09-16fix typos in word "successful".andvar
2020-12-10apply this change to a a couple more tests:mrg
--- 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-09-08disable these tests unless ATF_SBIN_IFCONFIG_WIFI_ENABLE=yes ismrg
in the environment. they change wifi configuration, restart wpa_supplicant and hostapd, and, on broken wifi chipsets, may hang the test run.
2020-07-27Skip the repeated_link_addr test by default as it causes thegson
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-27Use the new "run_unsafe" atf_config_get() option also with a couple of otherjruoho
tests that are known to be unsafe.
2020-07-27Instead of just skipping interfaces that are "up", skip the wholegson
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-22Skip interfaces that are already UP before the test starts. We canmartin
not change state of the test host this way, it breaks e.g. test systems with the root filesystem on NFS.
2020-07-06Remove the expected timeout; there is something more sinister behind thejruoho
timeouts seen on the Qemu/evbarm-aarch64 runs.
2020-07-03Skip these also for Qemu runs as they cause panics. Point to PR kern/55451.jruoho
2020-07-03Expect a timeout for evbarm-aarch64, as seen in the recent Qemu runs.jruoho
2020-06-30Skip a few more nodes, and enable this test for Qemu runs.jruoho
2020-06-30Add a couple of tests for sequential ifconfig(8) options, incl. PR kern/41912.jruoho
2020-06-27Ups. Fix shell parameter.jruoho
2020-06-27Add also a test that writes random garbage to every ifconfig(8) option thatjruoho
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-27Add a simple test case that writes random garbage to (almost) every sysctl node.jruoho
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-27Add a basic test for enabling/disabling network interface capabilities.jruoho
2020-06-27Add test cases for different 802.11 options. These include cases forjruoho
PR kern/35045, PR kern/45745, and PR kern/55424.
2020-06-27Use atf_pass to avoid test failure in case there are no suitable interfaces.jruoho
2020-06-25Test creating thousands of bridge(4)'s. Unlike with tap(4) (PR kern/55417),jruoho
this test succeeeds. It is even possible to have the ultimate ifconfig(8) output with more than 65,000 devices.
2020-06-25Verify that PR kern/52150 is no longer present.jruoho
2020-06-25Instead of UINT_MAX + 2, test what is claimed.jruoho
2020-06-25Actually create the tap(4) with a negative device number. Doh.jruoho
2020-06-25Reference also PR kern/52526.jruoho
2020-06-25Fix pastos.jruoho
2020-06-25Add a test case for kern/52771.jruoho
2020-06-25Add a test case for PR kern/53410.jruoho
2020-06-25Add test cases for PR kern/53546 and PR kern/55417. Both are skipped asjruoho
both reproduce panics.
2020-06-25Reference also PR kern/53860.jruoho
2020-06-25Require root privileges.jruoho
2020-06-24Fix references in comments.jruoho
2020-06-24Add a test case for PR bin/55389.jruoho
2020-03-15Skip tests where the old or the new image size seem to not fit intomartin
the working directory.
2020-03-15Skip this test if the atf working directory has not enough spacemartin
for the created image.
2020-03-12Fix typomartin
2017-10-08Make most of the resize_ffs tests skip if PUFFS is not configuredkre
in the kernel. (nb: for this purpose, a module that is configured to autoload counts as configured in the kernel...)
2017-03-22Skip the "migrate" test on architectures not natively using MBR, itmartin
can not work there.
2016-06-17When deadbeef is treated as a 32-bit signed integer, it actually has apgoyette
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-03-08Require the boot block to be used, test can't work otherwise.joerg
2015-12-27I was right - the output from gpt(8) did grow an extra space character!pgoyette
Fix the test to expect it. Test now passes on my local test bed.
2015-12-27Revert - tested using wrong test case. :(pgoyette
2015-12-27Update test - the attributes listed by the show command now have a spacepgoyette
in the comma-separated list. This allows the test to once again pass.
2015-12-06Add test for type, set, unsetchristos
2015-12-05more variableschristos