public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/102904] New: go testsuite does not always cause a timeout
@ 2021-10-22 18:40 pinskia at gcc dot gnu.org
  2021-10-23 19:45 ` [Bug testsuite/102904] " hjl.tools at gmail dot com
  2021-10-27 16:08 ` msebor at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-10-22 18:40 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102904

            Bug ID: 102904
           Summary: go testsuite does not always cause a timeout
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

I just ran into this on aarch64-linux-gnu.  It seems like the gotest timeout
mechanism is not working fully.

go.test/test/fixedbugs/issue16095.go was running for 298:53.85
(minues:seconds).

If I can reproduce it again, I will try to have more data.

^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug testsuite/102904] go testsuite does not always cause a timeout
  2021-10-22 18:40 [Bug testsuite/102904] New: go testsuite does not always cause a timeout pinskia at gcc dot gnu.org
@ 2021-10-23 19:45 ` hjl.tools at gmail dot com
  2021-10-27 16:08 ` msebor at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: hjl.tools at gmail dot com @ 2021-10-23 19:45 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102904

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2021-10-23

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
I saw

WARNING: program timed out.
FAIL: go.test/test/fixedbugs/issue16095.go execution,  -O2 -g

But the hanging issue16095.go wasn't terminated until I killed it by hand.

^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug testsuite/102904] go testsuite does not always cause a timeout
  2021-10-22 18:40 [Bug testsuite/102904] New: go testsuite does not always cause a timeout pinskia at gcc dot gnu.org
  2021-10-23 19:45 ` [Bug testsuite/102904] " hjl.tools at gmail dot com
@ 2021-10-27 16:08 ` msebor at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: msebor at gcc dot gnu.org @ 2021-10-27 16:08 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102904

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=91992

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
See also pr91992 for a similar problem with the Go test suite.  I haven't been
testing Go to avoid it so I can't say if it's still present.

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-10-27 16:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-22 18:40 [Bug testsuite/102904] New: go testsuite does not always cause a timeout pinskia at gcc dot gnu.org
2021-10-23 19:45 ` [Bug testsuite/102904] " hjl.tools at gmail dot com
2021-10-27 16:08 ` msebor at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).