DPDK CI discussions
 help / color / Atom feed
* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
       [not found]   ` <VE1PR08MB5149BE79083CD66A41CBD6D198340@VE1PR08MB5149.eurprd08.prod.outlook.com>
@ 2020-01-14 15:12     ` Aaron Conole
  2020-01-14 16:51       ` Aaron Conole
  0 siblings, 1 reply; 10+ messages in thread
From: Aaron Conole @ 2020-01-14 15:12 UTC (permalink / raw)
  To: Honnappa Nagarahalli; +Cc: test-report, ci, dev

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.

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.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  2020-01-14 15:12     ` [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings Aaron Conole
@ 2020-01-14 16:51       ` Aaron Conole
  2020-01-14 19:35         ` Honnappa Nagarahalli
  0 siblings, 1 reply; 10+ messages in thread
From: Aaron Conole @ 2020-01-14 16:51 UTC (permalink / raw)
  To: Aaron Conole; +Cc: Honnappa Nagarahalli, test-report, ci, dev

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.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  2020-01-14 16:51       ` Aaron Conole
@ 2020-01-14 19:35         ` Honnappa Nagarahalli
  2020-01-14 20:44           ` Aaron Conole
  0 siblings, 1 reply; 10+ messages in thread
From: Honnappa Nagarahalli @ 2020-01-14 19:35 UTC (permalink / raw)
  To: Aaron Conole; +Cc: test-report, ci, dev, nd, nd

<snip>
> 
> 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 compiled with clang-7. Compiler seems to hang while compiling test_ring.c

> 
> 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

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  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
  0 siblings, 2 replies; 10+ messages in thread
From: Aaron Conole @ 2020-01-14 20:44 UTC (permalink / raw)
  To: Honnappa Nagarahalli; +Cc: test-report\, ci\, dev\, nd

Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> writes:

> <snip>
>> 
>> 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 compiled with clang-7. Compiler seems to hang while compiling test_ring.c

Cool.  Looks like a good catch, then :)

>> 
>> 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


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  2020-01-14 20:44           ` Aaron Conole
@ 2020-01-15  0:55             ` Honnappa Nagarahalli
  2020-01-15  4:43             ` Honnappa Nagarahalli
  1 sibling, 0 replies; 10+ messages in thread
From: Honnappa Nagarahalli @ 2020-01-15  0:55 UTC (permalink / raw)
  To: Aaron Conole; +Cc: test-report, ci, dev, nd, nd

<snip>
> >>
> >> 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 compiled with clang-7. Compiler seems to hang while compiling
> > test_ring.c
> 
> Cool.  Looks like a good catch, then :)
Good test for Clang CI 😊

<snip>

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  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
  1 sibling, 1 reply; 10+ messages in thread
From: Honnappa Nagarahalli @ 2020-01-15  4:43 UTC (permalink / raw)
  To: Aaron Conole; +Cc: test-report, ci, dev, nd, Honnappa Nagarahalli, nd

<snip>
> >>
> >> 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 compiled with clang-7. Compiler seems to hang while compiling
> > test_ring.c
> 
> Cool.  Looks like a good catch, then :)
Update:
x86 - compilation succeeds, but take a long time - ~1hr.
On 2 different Arm platforms - compilation succeeds in normal amount of time.
Does anyone have any experience dealing with this kind of issue?

<snip>

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  2020-01-15  4:43             ` Honnappa Nagarahalli
@ 2020-01-15  5:05               ` Honnappa Nagarahalli
  2020-01-15 18:22                 ` Aaron Conole
  0 siblings, 1 reply; 10+ messages in thread
From: Honnappa Nagarahalli @ 2020-01-15  5:05 UTC (permalink / raw)
  To: Aaron Conole; +Cc: test-report, ci, dev, nd, Honnappa Nagarahalli, nd

<snip>
> > >>
> > >> 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 compiled with clang-7. Compiler seems to hang while compiling
> > > test_ring.c
> >
> > Cool.  Looks like a good catch, then :)
> Update:
> x86 - compilation succeeds, but take a long time - ~1hr.
> On 2 different Arm platforms - compilation succeeds in normal amount of
> time.
> Does anyone have any experience dealing with this kind of issue?
> 
I ran this on another x86 server - this patch takes ~8mns. The master (without this patch) takes ~1.02mns.

> <snip>


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  2020-01-15  5:05               ` Honnappa Nagarahalli
@ 2020-01-15 18:22                 ` Aaron Conole
  2020-01-15 18:38                   ` Honnappa Nagarahalli
  0 siblings, 1 reply; 10+ messages in thread
From: Aaron Conole @ 2020-01-15 18:22 UTC (permalink / raw)
  To: Honnappa Nagarahalli; +Cc: Aaron Conole, test-report\, ci\, dev\, nd

Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> writes:

> <snip>
>> > >>
>> > >> 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 compiled with clang-7. Compiler seems to hang while compiling
>> > > test_ring.c
>> >
>> > Cool.  Looks like a good catch, then :)
>> Update:
>> x86 - compilation succeeds, but take a long time - ~1hr.
>> On 2 different Arm platforms - compilation succeeds in normal amount of
>> time.
>> Does anyone have any experience dealing with this kind of issue?
>> 
> I ran this on another x86 server - this patch takes ~8mns. The master
> (without this patch) takes ~1.02mns.

It doesn't reproduce with clang-8.

>> <snip>


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  2020-01-15 18:22                 ` Aaron Conole
@ 2020-01-15 18:38                   ` Honnappa Nagarahalli
  2020-01-16  5:27                     ` Honnappa Nagarahalli
  0 siblings, 1 reply; 10+ messages in thread
From: Honnappa Nagarahalli @ 2020-01-15 18:38 UTC (permalink / raw)
  To: Aaron Conole; +Cc: test-report, ci, dev, nd, Honnappa Nagarahalli, nd

<snip>
> >> > >>
> >> > >> 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 compiled with clang-7. Compiler seems to hang while compiling
> >> > > test_ring.c
> >> >
> >> > Cool.  Looks like a good catch, then :)
> >> Update:
> >> x86 - compilation succeeds, but take a long time - ~1hr.
> >> On 2 different Arm platforms - compilation succeeds in normal amount
> >> of time.
> >> Does anyone have any experience dealing with this kind of issue?
> >>
> > I ran this on another x86 server - this patch takes ~8mns. The master
> > (without this patch) takes ~1.02mns.
> 
> It doesn't reproduce with clang-8.
Ok, do you want to update the Travis CI and re-run?

> 
> >> <snip>

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings
  2020-01-15 18:38                   ` Honnappa Nagarahalli
@ 2020-01-16  5:27                     ` Honnappa Nagarahalli
  0 siblings, 0 replies; 10+ messages in thread
From: Honnappa Nagarahalli @ 2020-01-16  5:27 UTC (permalink / raw)
  To: Aaron Conole; +Cc: test-report, ci, dev, nd, Honnappa Nagarahalli, nd

<snip>
> > >> > >>
> > >> > >> 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 compiled with clang-7. Compiler seems to hang while compiling
> > >> > > test_ring.c
> > >> >
> > >> > Cool.  Looks like a good catch, then :)
> > >> Update:
> > >> x86 - compilation succeeds, but take a long time - ~1hr.
> > >> On 2 different Arm platforms - compilation succeeds in normal
> > >> amount of time.
> > >> Does anyone have any experience dealing with this kind of issue?
> > >>
> > > I ran this on another x86 server - this patch takes ~8mns. The
> > > master (without this patch) takes ~1.02mns.
> >
> > It doesn't reproduce with clang-8.
> Ok, do you want to update the Travis CI and re-run?
I isolated the compilation issue to one of the test cases. It was a large function and I have split it into smaller functions. The compilation time reduces significantly. I have submitted a new version.

> 
> >
> > >> <snip>


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, back to index

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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     ` [dpdk-ci] FW: || pw64572 lib/eventdev: use custom element size ring for event rings Aaron Conole
2020-01-14 16:51       ` Aaron Conole
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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox