Re: [SPDK] Strange CI failure

https://ci.spdk.io/spdk-jenkins/results/autotest-per-patch/builds/21382/a... I can copy paste it if you cannot reach the link. ________________________________ From: SPDK <spdk-bounces(a)lists.01.org&gt; on behalf of Luse, Paul E <paul.e.luse(a)intel.com&gt; Sent: Tuesday, January 29, 2019 5:22 PM To: Storage Performance Development Kit Subject: Re: [SPDK] Strange CI failure Can you send a link to the full log? -----Original Message----- From: SPDK [mailto:spdk-bounces@lists.01.org] On Behalf Of Shahar Salzman Sent: Tuesday, January 29, 2019 8:21 AM To: Storage Performance Development Kit <spdk(a)lists.01.org&gt; Subject: [SPDK] Strange CI failure Hi, I have encountered a CI failure that has nothing to do with my code. The reason that I know it has nothing to do with it, is that the change is a gdb macro. Do we know that this test machine is unstable? Here is the backtrace: ========== Backtrace start: ========== in test/nvme/nvme.sh:108 -> main() ... 103 report_test_completion "nightly_nvme_reset" 104 timing_exit reset 105 fi 106 107 timing_enter identify => 108 $rootdir/examples/nvme/identify/identify -i 0 109 for bdf in $(iter_pci_class_code 01 08 02); do 110 $rootdir/examples/nvme/identify/identify -r "trtype:PCIe traddr:${bdf}" -i 0 111 done 112 timing_exit identify 113 ... Shahar _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk