| Age | Commit message (Collapse) | Author |
|
atf_tc_expect_fail - this is shell, so fix the names accordingly.
XXX Why do they differ?
|
|
See PR kern/47661.
|
|
|
|
|
|
|
|
|
|
This enables us to remove custom Atffiles whose only purpose was to avoid
using the helpers as tests.
XXX src/tests/dev/dm/ is not (yet) linked into the build!
|
|
|
|
|
|
|
|
cleanup function defined, resulting in a rump_server process hanging
around after the tests completed.
|
|
a stupid error.
|
|
Add tests for normal configuration of RAID 1 and RAID 5 sets.
|
|
this is why it was wrong for rump_syscalls.h to include this.
|
|
PR kern/44515
PR kern/44964
|
|
|
|
|
|
should not be allowed by atf-run (although they currently are ignored).
|
|
|
|
|
|
|
|
|
|
from martin
|
|
|
|
|
|
for this test. Thanks, pooka!
|
|
now that it's possible. With warm fs cache, the startup time of
the former is 0.01s and the latter 0.1s. With cold caches it's
0.2s vs 2s.
|
|
need to have an extended wait for the first powerd event to occur. Revert
that portion of previous commit.
|
|
- Does not require root access on the host, only in the rump
environment (which it gets by default)
- Manual clean-up of powerd process and rump-server socket is
not necessary - happens automatically
- Don't use a global, absolute path for the rump-server socket
For alarm_sensor, make sure events are still delivered after 'envstat -S'
(the cur_value was deliberately left at an alarm level and should not be
affected by the reset).
No longer need to skip the alarm_sensor and limit_sensor tests, since
pooka fixed passing of proplist to built-in modules.
Increase wait time for first powerd event report. (This should not be
needed, so there's probably a bug somewhere, but the increased timeout
lets us validate the rest of the sensor functionality.)
|
|
|
|
|
|
been nuked.
|
|
|
|
|
|
not dev/raid, so reflect this in the test dir. Affects location
for test of PR kern/44239.
|
|
described in PR kern/44239
|
|
XXX: the atf sh "compiler" should check for errors.
|
|
with a shellscript in terms of rump.cgdconfig and dd.
|
|
|
|
(XXX: need better way to reboot it)
|
|
|
|
|
|
Notably, md is a little tricky for this, since the ioctl that
configures the service also blocks in the kernel. Therefore, use
an additional pthread to probe when the service is fully configured
and the server can detach.
Also, rawpart love.
|
|
and checks the same data can be retrieved.
|
|
|
|
plaintext into into an encrypted image and back into plaintext by
doing rump I/O on /dev/cgd. There is one test to check that giving
the same password for both encryption and decryption produces the
same plaintext and another to check that giving a different passwords
does not produce the same plaintext.
This could be fairly easily extended to test all feature of cgd
(hint hint). For example, now cgd.conf is included in cvs, but
the only reason for that is that without further hacking cgdconfig
uses /dev/random quality random to generate the salt for a
pkcsetcetc_kdf2 cgconfig -g, and making an automated test block on
the entropy pool is just not good form. Details are everything.
|
|
- The use.fs property is gone.
- Mark the tests/fs/t_create:attrs test as broken when using the default
unprivileged-user:_atf setting. This probably deserves a fix somehow
but I'm not sure at this point.
|
|
how many bugs this found :-)
|
|
This poses problems when linking statically, as for sun2. Add -lrump
also after -lrumpuser, so that this links statically as well.
|
|
watchdog just a little bit sooner. This maintains the spirit of the
test while avoiding the actual bug. This can be reverted once (if)
the PR is fixed.
|