It appears that we now get a different errno. Looking at Jenkins to find
the first commit where this test starting failing indicates that
2fe5a79425c79f7b828acd91da66d97230925fc8 is the most likely cause.
Details
test now passes
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
tests/sys/net/routing/test_rtsock_l3.c | ||
---|---|---|
398–399 | In reality, EEXIST is a previous value from some of the system calls, and the real errno result is 0. |
tests/sys/net/routing/test_rtsock_l3.c | ||
---|---|---|
452 | I'm not sure if this one should actually be a success test, but it does succeed right now. |
ping? This test has been failing for the past 208 Jenkins test runs and I'd really like to get CI back to green, so we can actually catch regressions.
I've posted D29528 to get CI green again and allow for more time for this patch to be reviewed.
I've posted D29528 to get CI green again and allow for more time for this patch to be reviewed.
IMO this is the generally correct approach - once we have a failing test issue identified and a PR open or review in progress it makes sense to XFAIL the test
@melifaro should I split the change to rtm_add_v4_no_rtf_host_failure into a separate review?
In case of system builded without epair, previously those tests were skipped because the line 'ATF_REQUIRE_KERNEL_MODULE("if_epair");'.
But now it seems they are failing in place of being skipped if epair not builded with message like:
/tests/sys/net/routing/rtsock_config.h:134: Expected errno 17, got 2, in true