From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5390380011942706058==" MIME-Version: 1.0 From: Shahar Salzman Subject: [SPDK] Strange CI failure Date: Tue, 29 Jan 2019 15:20:37 +0000 Message-ID: List-ID: To: spdk@lists.01.org --===============5390380011942706058== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Backtrace start: =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D 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 =3D> 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 --===============5390380011942706058==--