I'm not sure that is what happened on this particular patch. Please note that Jenkins
and CH test pool gave same negative result on patch set 2. Meaning both caught an error.
The abnormality here is there are two Jenkins runs on patch set 1. First run failed due to
nvme-cli being different version than CH test pool. It happened on quite a few patches, so
today morning Karol re-ran the patches which failed due to this particular issue. Seems
like new score from patch set 1 overwrote that of patch set 2 (probably due to manual
retrigger of tests).
PS. Nvme-cli issue is reported here https://github.com/spdk/spdk/issues/366
From: SPDK [mailto:firstname.lastname@example.org] On Behalf Of Luse, Paul E
Sent: Tuesday, July 17, 2018 3:49 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Jenkins scan-build
I had a typo in a patch last night that failed CH test pool due to a correct scan-build
catch however it passed on Jenkins. Can one of you please take a look and see why it
passed on Jenkins?
patch set 2 (3 is the fix)