From: Aaron Conole <aconole@redhat.com>
To: 0-day Robot <robot@bytheb.org>
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
Michael Santana <msantana@redhat.com>
Subject: Re: [dpdk-dev] |FAILURE| pw devtools: add llx format specifier check
Date: Tue, 09 Feb 2021 14:33:01 -0500 [thread overview]
Message-ID: <f7tv9b13uky.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <20210209191748.26161-1-robot@bytheb.org> (robot@bytheb.org's message of "Tue, 9 Feb 2021 14:17:48 -0500")
0-day Robot <robot@bytheb.org> writes:
> From: robot@bytheb.org
>
> Test-Label: travis-robot
> Test-Status: FAILURE
>
>
> _travis build: failed_
> Build URL: /build/216558092
Sorry for the noise here. We hooked up some new features for the robot
and introduced a misconfiguration. It should be fixed shortly, and we
should get messages populated correctly.
prev parent reply other threads:[~2021-02-09 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 19:17 0-day Robot
2021-02-09 19:33 ` Aaron Conole [this message]
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=f7tv9b13uky.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=msantana@redhat.com \
--cc=robot@bytheb.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).