DPDK CI discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Aaron Conole <aconole@redhat.com>
Cc: David Marchand <david.marchand@redhat.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>, "ci@dpdk.org" <ci@dpdk.org>,
	nd <nd@arm.com>
Subject: Re: [dpdk-ci] query about Travis CI running status
Date: Tue, 26 Jan 2021 16:06:08 +0000	[thread overview]
Message-ID: <DBAPR08MB58149070150BA0F69E3ACBC598BC0@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <f7tbldblqju.fsf@dhcp-25.97.bos.redhat.com>

<snip>

> 
> Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> writes:
> 
> > <snip>
> >
> > Thanks for keeping this off the list, I was not comfortable discussing
> > things on the list 😊
> >
> >
> >
> >>
> >
> >> Hello,
> >
> >>
> >
> >> On Fri, Jan 22, 2021 at 3:18 PM Honnappa Nagarahalli
> >
> >> <Honnappa.Nagarahalli@arm.com> wrote:
> >
> >> > > > 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?
> >
> >> > It is the main repo: https://github.com/DPDK/dpdk
> >
> >>
> >
> >> I re-enabled a weekly build in the cron settings and set the "build on
> push"
> >
> >> option for the main repository DPDK/dpdk.
> >
> >> Travis started one build for the weekly schedule, which got cancelled
> >> with
> >
> >> "Owner DPDK does not have enough credits.".
> >
> >> I then merged a simple fix in the main repo, Travis triggered a job
> >> which got
> >
> >> cancelled with the same message.
> >
> >>
> >
> >> So I disabled all of Travis jobs again for DPDK/dpdk (no weekly
> >> build, no build on
> >
> >> push).
> >
> >>
> >
> >>
> >
> >> > > > Or the ovsrobot/DPDK? or both?
> >
> >> > This was not requested. Which one do we need?
> >
> >>
> >
> >> I'd like to hear about others but for me, ovsrobot/dpdk is the more
> >> important
> >
> >> (and the more credits-hungry btw).
> >
> >> DPDK/dpdk is a bonus.
> >
> >>
> >
> >>
> >
> >> > > > What of other individual's forks?
> >
> >> > I have not discussed this.
> >
> >> > Is this required? May be at least for the maintainers?
> >
> >>
> >
> >> I wanted to know what had been discussed/agreed with Travis.
> >
> >> This is not required, but nice for contributors.
> >
> > I definitely agree, this is good to have. The discussion has been
> > happening between Arm Ecosystem development team and Travis. So, info
> > on how things are implemented is scarce. I had provided the link to
> > DPDK/dpdk github and it was supposed to be on the 'allow list' and being
> monitored by Travis Support to ensure that credits are getting topped off. I
> will pass this email to our team and see what they say.
> >
> >
> >
> > We are also working on getting Arm owned GitLab instance integrated.
> > It should happen in the next 3 months (there are other projects too
> > which are affected). I had planned for DPDK/dpdk, but I will change it to
> ovsrobot/dpdk. I will check to see if we can provide access to maintainers.
> This will be a permanent solution.
> 
> That's good to know.  We have been discussing internally what to do when
> Github Actions inevitably goes the same way as Travis (pay $$$ or no builds),
> and I'm happy to hear that you have a permanent solution in mind.
Please note that this covers only Arm architecture. Other architectures are not covered.

> 
> >
> >
> >>
> >
> >>
> >
> >> >
> >
> >> > >
> >
> >> > > Sorry I don't know how the whitelist works in detail. Need to
> >> > > check
> >
> >> > > and get back.
> >
> >> > > Just wanted to know if Travis CI had chance to run.
> >
> >> > >
> >
> >> > > >
> >
> >> > > > >
> >
> >> > > > > 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.
> >
> >> > Can you please provide a link to this?
> >
> >>
> >
> >> You can see here:
> >
> >> https://travis-ci.com/github/DPDK/dpdk/requests
> >
> >> https://travis-ci.com/github/ovsrobot/dpdk/requests
> >
> >>
> >
> >>
> >
> >> --
> >
> >> David Marchand


      reply	other threads:[~2021-01-26 16:06 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
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 [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=DBAPR08MB58149070150BA0F69E3ACBC598BC0@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    /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).