Summary: | Lock-order reversals triggered by tests under sys.net.if_lagg_test.* on i386 | ||
---|---|---|---|
Product: | Base System | Reporter: | Li-Wen Hsu <lwhsu> |
Component: | tests | Assignee: | freebsd-testing (Nobody) <testing> |
Status: | Open --- | ||
Severity: | Affects Only Me | CC: | bdrewery |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | i386 | ||
OS: | Any |
Description
Li-Wen Hsu
![]() ![]() A commit references this bug: Author: lwhsu Date: Sun Feb 16 11:16:06 UTC 2020 New revision: 357997 URL: https://svnweb.freebsd.org/changeset/base/357997 Log: Temporarily skip failing sys.net.if_lagg_test.witness on i386 CI PR: 244163 Sponsored by: The FreeBSD Foundation Changes: head/tests/sys/net/if_lagg_test.sh This is weird. Is lagg actually involved here? (In reply to Bryan Drewery from comment #2) This test case is simply doing: `sysctl -n debug.witness.badstacks | grep -q 'at lagg_'` and fails if there is anything found. Is it possible due to kyua has running other tests before and affects this? |