DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Michael Santana <maicolgabriel@hotmail.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	Aaron Conole <aconole@redhat.com>, nd <nd@arm.com>,
	nd <nd@arm.com>
Subject: RE: [PATCH] ci: do not dump error logs in GHA containers
Date: Fri, 29 Apr 2022 04:16:23 +0000	[thread overview]
Message-ID: <DBAPR08MB581426BA1C77DADE0EDFA61398FC9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wuMHnEQmh0Zybk8B757_yEkx290NvoqKM+woZt4A=TTQ@mail.gmail.com>

<snip>

> 
> On Tue, Apr 26, 2022 at 5:05 PM Aaron Conole <aconole@redhat.com>
> wrote:
> > >
> > > TBH, I did not test Travis by lack of interest (plus I don't want to
> > > be bothered with their ui / credit stuff).
> > > We could consider dropping Travis in the near future.
> > >
> > > Opinions?
> >
> > I think it makes sense.  We haven't had travis reports in a while
> > because their credit system made it impossible to use.  We had kept it
> > around for users of travis, but at this point, I think most people
> > have migrated to GHA.
> >
> 
> Honnappa, do you see an issue if we stop maintaining the Travis configuration
> in the DPDK repo?
I do not see much of an issue from Arm side. The machines in the UNH lab provide the cover.

I am wondering that this might still be useful for individual developers who I believe are not affected by the Travis's credit system (I am not sure on this). 

> 
> Thanks.
> 
> --
> David Marchand


  reply	other threads:[~2022-04-29  4:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  7:09 David Marchand
2022-04-26  7:18 ` David Marchand
2022-04-26 15:05   ` Aaron Conole
2022-04-28  9:51     ` David Marchand
2022-04-29  4:16       ` Honnappa Nagarahalli [this message]
2022-04-29 20:12         ` Aaron Conole

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=DBAPR08MB581426BA1C77DADE0EDFA61398FC9@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maicolgabriel@hotmail.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).