On Sun, Jul 2, 2017 at 7:36 AM, Nathan Cutler <ncutler@xxxxxxx> wrote: > Sorry, please forget everything I wrote above. The kraken make check failure > is not a case of "Unix Domain socket path too long", after all. (Jenkins is > set up to grep the log for certain strings and display them as possible > causes if they are found, and that string appears in a later test, but > AFAICT it doesn't cause the test to fail.) > > Several tests seem to fail, including the very first test: > > 2/156 Test #1: test-ceph-helpers.sh ....................***Failed 44.06 > sec > > The log of that failed test is here: https://paste2.org/DB8z1kzV Looks like this http://tracker.ceph.com/issues/20345 > > Since this is happening on all kraken PRs, it looks like a regression. I > will bisect. > > > Nathan > -- > 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 -- Cheers, Brad -- 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
