Date: Wed, 13 May 2020 19:21:03 +0000 From: bugzilla-noreply@freebsd.org To: testing@freebsd.org Subject: [Bug 246443] sys.net.if_clone_test.epair_stress sometimes exceeds timeout limit but not caught by kyua Message-ID: <bug-246443-32464@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246443 Bug ID: 246443 Summary: sys.net.if_clone_test.epair_stress sometimes exceeds timeout limit but not caught by kyua Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: tests Assignee: testing@freebsd.org Reporter: lwhsu@FreeBSD.org Since https://ci.freebsd.org/job/FreeBSD-head-amd64-test/15098 (not related to that commit, and it maybe because of the updates of the tes= t vm starts to trigger this issue.) sys.net.if_clone_test.epair_stress now sometimes exceeds the default timeout limit (300s) but was not stopped by kyua, or got stopped far after timeout limit. For example, it took 2154.252s in build 15098, and was not caught in build 15187. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246443-32464>