All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shahar Salzman <shahar.salzman at kaminario.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Strange CI failure
Date: Tue, 29 Jan 2019 15:35:04 +0000	[thread overview]
Message-ID: <AM6PR04MB5127666EDCEFF3C98B73ECDA89970@AM6PR04MB5127.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 82C9F782B054C94B9FC04A331649C77AB8CAA69E@FMSMSX126.amr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]

https://ci.spdk.io/spdk-jenkins/results/autotest-per-patch/builds/21382/archive/nvme_phy_autotest/build.log

I can copy paste it if you cannot reach the link.
________________________________
From: SPDK <spdk-bounces(a)lists.01.org> on behalf of Luse, Paul E <paul.e.luse(a)intel.com>
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(a)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>
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

             reply	other threads:[~2019-01-29 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 15:35 Shahar Salzman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-31  8:47 [SPDK] Strange CI failure Shahar Salzman
2019-01-30 14:28 Howell, Seth
2019-01-30 12:18 Shahar Salzman
2019-01-29 18:29 Luse, Paul E
2019-01-29 16:09 Harris, James R
2019-01-29 16:08 Shahar Salzman
2019-01-29 15:47 Luse, Paul E
2019-01-29 15:22 Luse, Paul E
2019-01-29 15:20 Shahar Salzman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM6PR04MB5127666EDCEFF3C98B73ECDA89970@AM6PR04MB5127.eurprd04.prod.outlook.com \
    --to=spdk@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.