On Thu, Jun 2, 2016 at 2:11 AM, Nathan Cutler <ncutler@xxxxxxx> wrote: >> - 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? This sounds like a network issue in OVH (cloud provider where Jenkins is hosted)? -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
