CEPH filesystem development
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Erwan Velu <evelu@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: Little update on the build platform
Date: Thu, 2 Jun 2016 10:11:21 +0200	[thread overview]
Message-ID: <574FEA29.7040508@suse.cz> (raw)
In-Reply-To: <902296593.97770947.1464716952266.JavaMail.zimbra@redhat.com>

> - An diagnosis helper is now in place to spot known build failures  :
> A list of common issues have been entered (like gcc or jenkins failures, segfaults, etc...)
> A typical output looks like : https://jenkins.ceph.com/job/ceph-pull-requests/6448/

Thanks, guys, this looks like an excellent improvement.

Now I have a PR with failing make check and it appears that Jenkins is 
aware of the failures:

https://jenkins.ceph.com/job/ceph-pull-requests/6550/consoleFull#17782142537ba86caa-bd6c-4071-8005-3f6d80f92e07

The two recognized failures are highlighted in red:

FATAL: java.io.IOException: Unexpected termination of the channel

java.lang.NullPointerException: no workspace from node 
hudson.slaves.DumbSlave[158.69.84.81+trusty_huge__c69f129f-3dff-46c2-9bd4-d14364fcb62f] 
which is computer hudson.slaves.SlaveComputer@1957dd58 and has channel null

But I don't know what to do about them? Do we have documentation of the 
common failure cases and what can be done to fix them?

Nathan

  parent reply	other threads:[~2016-06-02  8:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1236727659.97766119.1464716235552.JavaMail.zimbra@redhat.com>
2016-05-31 17:49 ` Little update on the build platform Erwan Velu
2016-05-31 17:58   ` Piotr Dałek
2016-05-31 18:02     ` Erwan Velu
2016-05-31 18:16       ` Piotr Dałek
2016-05-31 18:44   ` John Spray
2016-05-31 19:14     ` Ken Dreyer
2016-06-01 14:40       ` Erwan Velu
2016-06-01 14:57         ` Sage Weil
2016-06-02  8:11   ` Nathan Cutler [this message]
2016-06-13 15:41     ` Ken Dreyer

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=574FEA29.7040508@suse.cz \
    --to=ncutler@suse.cz \
    --cc=ceph-devel@vger.kernel.org \
    --cc=evelu@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox