DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	test-report@dpdk.org, ci@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
Date: Tue, 14 Jan 2020 11:51:46 -0500	[thread overview]
Message-ID: <f7tftgim15p.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <f7t4kwynkay.fsf@dhcp-25.97.bos.redhat.com> (Aaron Conole's message of "Tue, 14 Jan 2020 10:12:53 -0500")

Aaron Conole <aconole@redhat.com> writes:

> Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> writes:
>
>> Hi Aaron,
>> I am not able to understand the error, looks like there is no
>> particular error. Can you please take a look?
>
> Gladly.  A number of the systems that were running the build stopped
> their output for an unknown reason (looks like this was a 1-time
> thing).  See the error:
>
>   [2164/2165] Compiling C object 'app/te...st@@dpdk-test@exe/test_ring_perf.c.o'.
>
>   No output has been received in the last 10m0s, this potentially
>   indicates a stalled build or something wrong with the build itself.

I see this continually happening (I've kicked it off a number of times).

This patch might need more investigation, since it's always failing when
building 2164/2165 object.

I'll note that it seems to be clang related, rather than gcc related.

> My guess is some kind of infrastructure change happened during the
> build?  Maybe compiling the test_ring_perf.c object has been pushed out
> too far.  I've restarted one of the jobs to see if it will successfully
> execute.  If so, it's just a fluke.
>
> As for the fluke part, the intent is to enhance the robot to detect
> these "error" conditions and issue a restart for the travis build
> (rather than not report a valid state).  That's work TBD (but patches
> are welcome - see https://github.com/orgcandman/pw-ci for all the bot
> code).
>
>> Thank you,
>> Honnappa
>>
>> -----Original Message-----
>> From: 0-day Robot <robot@bytheb.org>
>> Sent: Monday, January 13, 2020 10:58 PM
>> To: test-report@dpdk.org
>> Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; robot@bytheb.org
>> Subject: || pw64572 lib/eventdev: use custom element size ring for event rings
>>
>> From: robot@bytheb.org
>>
>> Test-Label: travis-robot
>> Test-Status:
>> http://dpdk.org/patch/64572
>>
>> _Travis build: errored_
>> Build URL: https://travis-ci.com/ovsrobot/dpdk/builds/144202958
>> IMPORTANT NOTICE: The contents of this email and any attachments are
>> confidential and may also be privileged. If you are not the intended
>> recipient, please notify the sender immediately and do not disclose
>> the contents to any other person, use it for any purpose, or store or
>> copy the information in any medium. Thank you.
>> IMPORTANT NOTICE: The contents of this email and any attachments are
>> confidential and may also be privileged. If you are not the intended
>> recipient, please notify the sender immediately and do not disclose
>> the contents to any other person, use it for any purpose, or store or
>> copy the information in any medium. Thank you.


  reply	other threads:[~2020-01-14 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200113172518.37815-7-honnappa.nagarahalli@arm.com>
     [not found] ` <1578977880-13011-1-git-send-email-robot@bytheb.org>
     [not found]   ` <VE1PR08MB5149BE79083CD66A41CBD6D198340@VE1PR08MB5149.eurprd08.prod.outlook.com>
2020-01-14 15:12     ` Aaron Conole
2020-01-14 16:51       ` Aaron Conole [this message]
2020-01-14 19:35         ` Honnappa Nagarahalli
2020-01-14 20:44           ` Aaron Conole
2020-01-15  0:55             ` Honnappa Nagarahalli
2020-01-15  4:43             ` Honnappa Nagarahalli
2020-01-15  5:05               ` Honnappa Nagarahalli
2020-01-15 18:22                 ` Aaron Conole
2020-01-15 18:38                   ` Honnappa Nagarahalli
2020-01-16  5:27                     ` Honnappa Nagarahalli

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=f7tftgim15p.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=test-report@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).