Bug 197600 - lib.libc.sys.poll_test:poll_3way timed out
Summary: lib.libc.sys.poll_test:poll_3way timed out
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: tests (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-testing (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-13 20:42 UTC by Enji Cooper
Modified: 2019-01-24 07:56 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enji Cooper freebsd_committer freebsd_triage 2015-02-13 20:42:25 UTC
From https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/689/testReport/junit/lib.libc.sys/poll_test/poll_3way/ :

Error Message

Test case body timed out
Standard Error

Test case metadata
------------------

allowed_architectures is empty
allowed_platforms is empty
description = Check for 3-way collision for descriptor. First child comes and polls on descriptor, second child comes and polls, first child times out and exits, third child comes and polls. When the wakeup event happens, the two remaining children should both be awaken. (kern/17517)
has_cleanup = false
required_configs is empty
required_disk_space = 0
required_files is empty
required_memory = 0
required_programs is empty
required_user is empty
timeout = 15

Original stderr
---------------

Subprocess timed out; sending KILL signal...
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2018-01-08 04:14:48 UTC
For the following conditions
Product: Base System, Documentation Status: New, Open, In Progress, UNCONFIRMED 
Assignee: Former FreeBSD committer 

Reset to default assignee. Reset status to "Open".
Comment 2 Li-Wen Hsu freebsd_committer freebsd_triage 2019-01-21 23:01:59 UTC
I do not see lib.libc.sys.poll_test.poll_3way fails on ci.freebsd.org for a long time.  I suggest close this ticket and reopen when it fails more often.
Comment 3 Li-Wen Hsu freebsd_committer freebsd_triage 2019-01-24 07:56:06 UTC
This test case runs fine on new CI infrastructure.