All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105617] [CI] [CNL only] igt@* - incomplete - Build timed out (after 18 minutes). Marking the build as aborted.
Date: Tue, 20 Mar 2018 07:43:54 +0000	[thread overview]
Message-ID: <bug-105617-502-sIqzUQJlVj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105617-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1880 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105617

--- Comment #1 from Marta Löfstedt <marta.lofstedt@intel.com> ---
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_4/fi-cnl-y3/igt@perf_pmu@busy-accuracy-50-vecs0.html

this is kind of funny:

[68/97] skip: 18, pass: 40, fail: 10 \
running: igt/perf_pmu/busy-accuracy-50-vecs0

[68/97] skip: 18, pass: 40, fail: 10 |      
owatch: TIMEOUT!
owatch: timeout for /dev/watchdog0 set to 10 (requested 10)
Build timed out (after 18 minutes). Marking the build as aborted.
Agent went offline during the build
ERROR: Connection was broken: java.io.EOFException
        at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2675)
        at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3150)
        at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:859)
        at java.io.ObjectInputStream.<init>(ObjectInputStream.java:355)
        at
hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)
        at
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
        at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
        at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

Build step 'Execute shell' marked build as failure
Set build name.
Workspace is not accessible
ERROR: no workspace for CI_IGT_test #1059909
Notifying upstream projects of job completion
Finished: FAILURE
Completed CI_IGT_test drmtip_4/fi-cnl-y3/24 : FAILURE
CI_IGT_test runtime 1091 seconds
Rebooting fi-cnl-y3

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2928 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-03-20  7:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-105617-502@http.bugs.freedesktop.org/>
2018-03-20  7:42 ` [Bug 105617] [CI] [CNL only] igt@* - incomplete - Build timed out (after 18 minutes). Marking the build as aborted bugzilla-daemon
2018-03-20  7:43 ` bugzilla-daemon [this message]
2018-03-20  7:44 ` bugzilla-daemon
2018-03-20  7:45 ` bugzilla-daemon
2018-03-20  7:47 ` bugzilla-daemon
2018-03-23  9:12 ` bugzilla-daemon
2018-03-26 13:18 ` bugzilla-daemon
2018-03-26 13:20 ` bugzilla-daemon
2018-04-11  9:47 ` bugzilla-daemon
2018-04-19  6:31 ` bugzilla-daemon
2018-04-26  8:11 ` bugzilla-daemon
2018-04-26  8:12 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105617-502-sIqzUQJlVj@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.