[SPDK] Re: Build failure for change https://review.spdk.io/gerrit/c/spdk/spdk/+/2140

Zawadzki, Tomasz <tomasz.zawadzki at intel.com>
Newsgroups dev.linux.lists.spdk
Message-ID <DM6PR11MB4220103BC7579EE7931953AEEEBE0@DM6PR11MB4220.namprd11.prod.outlook.com>
Hi Wenhua Liu,

Looks like patch adding timestamps was introduced by Vitaliy very recently. Please see:
https://review.spdk.io/gerrit/c/spdk/spdk/+/2023

Going by the commit message, it looks like the rocksdb test depended on specific log output.

Thanks,
Tomek

> -----Original Message-----
> From: Wenhua Liu <liuw(a)vmware.com>
> Sent: Tuesday, May 12, 2020 10:44 AM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: [SPDK] Build failure for change
> https://review.spdk.io/gerrit/c/spdk/spdk/+/2140
> 
> Hi,
> 
> I submitted a change (the 2nd time) a few days ago after fixing some
> compiling issue, but this time it still failed on build testing.
> 
> The change is here:
> https://review.spdk.io/gerrit/c/spdk/spdk/+/2140
> 
> The build log is here:
> https://ci.spdk.io/results/autotest-per-patch/builds/12800/archive/BlobFS-
> autotest/build.log
> 
> The following log snippet is probably what failure is. As after this, I see all log
> messages prefixed with “(FAILED)”.
> 
> 00:03:48.189  ========== Backtrace start: ==========
> 00:03:48.189
> 00:03:48.192  in ./test/blobfs/rocksdb/rocksdb.sh:34 -> run_step(["insert"])
> 00:03:48.192       ...
> 00:03:48.192  backtrace unavailable
> 00:03:48.192       ...
> 00:03:48.198  in /var/jenkins/workspace/BlobFS-
> autotest/spdk/test/common/autotest_common.sh:772 ->
> run_test(["rocksdb_insert"],["run_step"],["insert"])
> 00:03:48.198       ...
> 00:03:48.198     767           timing_enter $test_name
> 00:03:48.198     768           echo
> "************************************"
> 00:03:48.198     769           echo "START TEST $test_name"
> 00:03:48.198     770           echo
> "************************************"
> 00:03:48.198     771           xtrace_restore
> 00:03:48.198  => 772           time "$@"
> 00:03:48.198     773           xtrace_disable
> 00:03:48.198     774           echo
> "************************************"
> 00:03:48.198     775           echo "END TEST $test_name"
> 00:03:48.198     776           echo
> "************************************"
> 00:03:48.198     777           timing_exit $test_name
> 00:03:48.198       ...
> 00:03:48.199  in ./test/blobfs/rocksdb/rocksdb.sh:146 -> main([])
> 00:03:48.199       ...
> 00:03:48.199  backtrace unavailable
> 00:03:48.199       ...
> 00:03:48.199
> 00:03:48.199  ========== Backtrace end ==========
> 
> From my understanding, it’s not possible my change can cause such problem.
> Could someone help take a look what is really wrong and tell me how I can
> move forward?
> 
> Thanks,
> -Wenhua Liu
> 
> 
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.