The NetBSD project now has a server dedicated to automated regression
testing of NetBSD-current, running the ATF test suite on daily (or
more frequent) builds in qemu virtual machines. The first two ports
being tested are i386 and sparc; the sparc results are available at
http://releng.netbsd.org/b5reports/sparc/
Alas, the tests are not yet fully working on sparc. The first 134 ATF
tests run fine, and most of them succeed, but at one point during the
fs/vfs/t_vnops test, test cases start timing out, ultimately causing
the test run as a whole to time out. Here is an extract from the ATF
log output around the point where things start to go wrong:
p2k_ffs_rename_dotdot: Passed.
p2k_ffs_rename_nametoolong: Passed.
p2k_ffs_rename_reg_nodir: Passed.
p2k_ffs_symlink_zerolen: Passed.
puffs_access_simple: Failed: Test case timed out after 300 seconds
puffs_attrs: Failed: Test case timed out after 300 seconds
puffs_create_exist: Failed: Test case timed out after 300 seconds
puffs_create_nametoolong: Failed: Test case timed out after 300 seconds
puffs_dir_notempty: Failed: Test case timed out after 300 seconds
puffs_dir_rmdirdotdot: Failed: Test case timed out after 300 seconds
The complete log output is at
http://releng.netbsd.org/b5reports/sparc/build/2011.07.31.23.10.58/test.log
Your help in tracking down the cause of the failure would be
appreciated. For example, if you happen to be running -current on a
physical sparc machine, it would be helpful if you could try running
the ATF tests manually:
cd /usr/tests
atf-run|atf-report
and let me and/or the port-sparc list know whether the tests time out in
the same way there as they do under qemu.
Thanks,
--
Andreas Gustafsson, gs...@gson.org
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
The latter would be my bet too (noting that not all pthread tests pass).
Martin