5e02285975
Remove the "expected failure" from test n12, and change it not to use
...
the "-v" command line option to ipf_test. The -v option causes it to
display additional information, some of which is not fixed (looks like
an internal data structure address).
One fewer on the expected-failures list. :)
2015-12-26 08:01:58 +00:00
c8560b5aee
Remove the "broken on BE" mark from the N14 testcase - ozaki-r fixed it
...
recently.
2014-12-01 19:46:29 +00:00
349f6dd23e
Darren fixed n8 and n9 recently
2014-07-15 20:00:23 +00:00
cccb715a0e
Test n17_6 does not yet exist so remove unrequired files and test case
2014-07-12 14:37:12 +00:00
0bac6b7608
Mark two more test case as only failing for BE
2013-05-16 07:43:02 +00:00
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
99e62f4068
Fix argument order for "n14"
2013-03-19 13:23:58 +00:00
19ec7b0e9f
Mark a few more test cases known to only work by chance as failing
...
and point to PR 47665.
Julio: how do we make such cases not fail when they actually happen to
work (by pure luck)?
2013-03-18 20:03:56 +00:00
ebd45a6ca9
Mark some long-standing failures as known failures.
...
The offending tests are these:
- t_filter_exec: f26, f27.
- t_filter_parse: i17.
- t_nat_exec: n12.
These tests are confirmed to fail in NetBSD/current under amd64, i386 and
sparc as reported by the continuous testing systems.
2013-03-17 03:00:05 +00:00
0855789845
Test-case n3_6 is not applicable to NetBSD (according to Darren R.)
2012-12-02 08:52:06 +00:00
08896ebe5a
More test clean-up
2012-12-01 21:37:41 +00:00
1ed7a9a845
Update a couple of tests to indicate that they are broken/failing because
...
of missing input/expected data files
2012-11-29 17:22:17 +00:00
acd8a5e133
Since all of the expected-results files provided from upstream include
...
the "-D" output (Dump additional internal tables), update the tests to
actually generate the data!
This lets us re-enable 28 of the 30 "skipped" tests.
XXX Still need to work on tests n12 and n17_6
2012-11-29 04:57:42 +00:00
30a942f180
test cases n201 and n202 were removed on import of 5.1.2
2012-07-22 16:22:41 +00:00
e048bbf458
Restore the rest of the ipfilter test framework, even if most of these
...
tests are broken. The "golden output" files for these tests need to be
updated.
2012-07-08 14:45:05 +00:00
4f5cd33ee1
Mark the failing tests as broken. XXX: If no one is willing to maintain
...
the ipf tests, these should be removed.
2012-03-27 09:27:33 +00:00
f8a1d7977c
Back out the recent import of IPFilter 5.1.1 for the upcoming branch,
...
which will now have IPFilter 4.1.34. IPFilter 5.1.1 will be restored
post-branch.
ok: core, releng.
2012-02-15 17:55:03 +00:00
c785063d3d
Comment out test n3_6 - the data files are missing
2012-02-14 09:17:22 +00:00
b13c836b86
Update ipf test suite with test cases from IPFilter 5.1.1
2012-02-13 18:52:53 +00:00
94e5abaaf2
Disable test cases which have not worked in ages instead of skipping them.
2010-12-18 13:06:51 +00:00
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
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
pgoyette