8 Commits

Author	SHA1	Message	Date
martin	e2eacae3cf	Assume that the NAT failures that happen on some architectures are endianess ... bugs, so do not expect failure on LE archs for now.	2013-05-16 07:20:29 +00:00
pgoyette	5cf1898f6e	Use proper quoting for the expected-failure reason	2012-12-01 04:43:44 +00:00
pgoyette	a95855641b	If we're going to expect a failure, we need to use the correct shell ... function! "atf_expect_fail()" does not have a "_tc" in its name!	2012-11-30 14:46:48 +00:00
pgoyette	85d282e793	fix typo in previous - missing quote	2012-11-29 18:54:43 +00:00
pgoyette	a557d345a2	Add another test option for expected failures, rather than simply ... skipping tests	2012-11-29 17:10:21 +00:00
jmmv	decf2b5e0f	Adjusts tests after import of atf-0.12: ... - 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.	2010-11-07 17:51:16 +00:00
jmmv	b27e7b1e81	Oh, wow. Loads of broken ipf test cases that went unnoticed because they ... were unchecked errors. Fix them. These have been caught by the upcoming version of atf, which explicitly does 'set -e' in shell test programs.	2010-10-19 16:36:36 +00:00
jmmv	f8a35c46be	Do not use awk to generate the test program. Use some eval magic to generate ... the tests on the fly alongside with easier-to-read functions. While doing this, split the big monolithic test program into more granular but cohesive test programs. Phew, this one was tough. And it's horrible to see that many these tests (yes, the tests themselves probably) are broken.	2010-07-10 17:28:36 +00:00