Bug 246443

Summary: sys.net.if_clone_test.epair_stress sometimes exceeds timeout limit but not caught by kyua
Product: Base System Reporter: Li-Wen Hsu <lwhsu>
Component: testsAssignee: freebsd-testing (Nobody) <testing>
Status: New ---    
Severity: Affects Only Me    
Priority: ---    
Version: CURRENT   
Hardware: Any   
OS: Any   

Description Li-Wen Hsu freebsd_committer freebsd_triage 2020-05-13 19:21:03 UTC
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 test 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.
Comment 1 commit-hook freebsd_committer freebsd_triage 2020-05-13 19:30:23 UTC
A commit references this bug:

Author: lwhsu
Date: Wed May 13 19:29:15 UTC 2020
New revision: 361017
URL: https://svnweb.freebsd.org/changeset/base/361017

Log:
  Temporarily skip sys.net.if_clone_test.epair_stress

  This case timed out so often

  PR:		246443
  Sponsored by:	The FreeBSD Foundation

Changes:
  head/tests/sys/net/if_clone_test.sh
Comment 2 commit-hook freebsd_committer freebsd_triage 2020-05-13 20:38:31 UTC
A commit references this bug:

Author: lwhsu
Date: Wed May 13 20:37:46 UTC 2020
New revision: 361019
URL: https://svnweb.freebsd.org/changeset/base/361019

Log:
  Only skip sys.net.if_clone_test.epair_stress in CI env

  PR:		246443
  Sponsored by:	The FreeBSD Foundation

Changes:
  head/tests/sys/net/if_clone_test.sh