From: David Marchand <david.marchand@redhat.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>
Cc: "aconole@redhat.com" <aconole@redhat.com>,
"ci@dpdk.org" <ci@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-ci] query about Travis CI running status
Date: Fri, 22 Jan 2021 08:48:52 +0100 [thread overview]
Message-ID: <CAJFAV8z5hqDXG5Dt18azSgMT1do3gC+vg5rXFSeEzDpynjweww@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0802MB2351A30AB7A81C5FC0B066959EA00@VI1PR0802MB2351.eurprd08.prod.outlook.com>
On Fri, Jan 22, 2021 at 8:28 AM Ruifeng Wang <Ruifeng.Wang@arm.com> wrote:
> Can you tell whether Travis CI is still running or have been disabled?
>
> It seems there is no Travis build since Dec 16, 2020.
> https://travis-ci.com/github/ovsrobot/dpdk/builds
>
> I think now DPDK can use Travis CI as usual as a result of Arm’s communication with Travis.
> DPDK should be on a whitelist and free from credit issue.
Can you share details on this?
Do you mean the main DPDK/dpdk repo gets free credits?
Or the ovsrobot/DPDK? or both?
What of other individual's forks?
>
> Just want to know if it works as expected.
From the webui, I still see a complaint on missing credits for
DPDK/dpdk and ovsrobot/dpdk, but I can't tell if this warning is
linked to my account.
--
David Marchand
next prev parent reply other threads:[~2021-01-22 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 7:28 Ruifeng Wang
2021-01-22 7:48 ` David Marchand [this message]
2021-01-22 8:05 ` Ruifeng Wang
2021-01-22 14:16 ` Aaron Conole
2021-01-22 14:18 ` Honnappa Nagarahalli
2021-01-25 9:44 ` David Marchand
2021-01-26 13:56 ` Honnappa Nagarahalli
2021-01-26 14:29 ` Aaron Conole
2021-01-26 16:06 ` 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=CAJFAV8z5hqDXG5Dt18azSgMT1do3gC+vg5rXFSeEzDpynjweww@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=nd@arm.com \
/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).