DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] aesni mb on Centos KO for three weeks
@ 2019-06-05 12:05 David Marchand
  2019-06-05 12:25 ` Thomas Monjalon
  0 siblings, 1 reply; 2+ messages in thread
From: David Marchand @ 2019-06-05 12:05 UTC (permalink / raw)
  To: dev

I noticed build errors on patches I sent yesterday:
http://mails.dpdk.org/archives/test-report/2019-June/084633.html

I went and looked at the test-report mailing list.

The failures on master builds started on May 14th:
http://mails.dpdk.org/archives/test-report/2019-May/082432.html
But still, the test was reported as successfull.

The status got properly reported starting May 28th:
http://mails.dpdk.org/archives/test-report/2019-May/083421.html
Looking at patchwork this day, I can see that it changed between
http://patchwork.dpdk.org/patch/53721/ and
http://patchwork.dpdk.org/patch/53722/

So I suppose someone noticed that the meson build failures were not
properly reported and fixed it, but the error still remained.

So, we have this error for 3 weeks, is there someone looking at fixing it
please?
I did not manage to build the ipsec_mb thing on my rhel.
Not sure what is wrong, but I don't want to waste more time on it.


As a sidenote, we don't have Intel build reports on the patches since this
morning, around
http://mails.dpdk.org/archives/test-report/2019-June/084647.html
Has it been disabled intentionnally?


-- 
David Marchand

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

end of thread, other threads:[~2019-06-05 12:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-05 12:05 [dpdk-dev] aesni mb on Centos KO for three weeks David Marchand
2019-06-05 12:25 ` Thomas Monjalon

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