From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>
Subject: [dpdk-dev] aesni mb on Centos KO for three weeks
Date: Wed, 5 Jun 2019 14:05:42 +0200 [thread overview]
Message-ID: <CAJFAV8xBF_6T295aGi7QuYB2ccU-qepxbJzXsskKybU5NfX4Cw@mail.gmail.com> (raw)
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
next reply other threads:[~2019-06-05 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 12:05 David Marchand [this message]
2019-06-05 12:25 ` Thomas Monjalon
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=CAJFAV8xBF_6T295aGi7QuYB2ccU-qepxbJzXsskKybU5NfX4Cw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@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).