All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Aaron Conole <aconole@redhat.com>,
	David Marchand <david.marchand@redhat.com>
Cc: "Somalapuram, Amaranath" <Amaranath.Somalapuram@amd.com>,
	"Kumar, Ravi1" <Ravi1.Kumar@amd.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@mellanox.com>,
	Ali Alnubani <alialnu@mellanox.com>,
	dpdklab@iol.unh.edu
Subject: Re: [dpdk-dev] [PATCH v1] maintainers: update for AMD xgbe and ccp crypto
Date: Mon, 27 Apr 2020 17:00:26 +0200	[thread overview]
Message-ID: <529334320.JY4mfKhWER@thomas> (raw)
In-Reply-To: <f7tftcpkrv7.fsf@dhcp-25.97.bos.redhat.com>

27/04/2020 14:58, Aaron Conole:
> Ferruh Yigit <ferruh.yigit@intel.com> writes:
> > [1] Two issues reported
> > a) ninja: build stopped: Error writing to build log: Disk quota
> > exceeded.
> 
> This occurs on some of the ARM64 builds.  Travis is aware of the issue,
> but don't seem urgently fixing it. :-/  I think we have a series
> outstanding that should be applied to drop those builds for now.

I saw some "Disk quota exceeded" on x86 static builds.
So I changed my mind, I am not sure dropping only Arm from Travis
is a solution, even temporary.


> > b) No output has been received in the last 10m0s, this potentially indicates a
> > stalled build or something wrong with the build itself.
> 
> This is a future enhancement I need to work on.  When a build has jobs
> that are stalled / errored, we need to restart them (at least once).  Or
> otherwise flag it.  It especially happens when internal travis
> infrastructure fails.

Yes Travis infrastructure fails. Always.
Travis is free, but it is not a reason to provide a randomly failing tool.
I suggest switching to other platforms like OBS or our community lab,
preferring the most reliable one.



  reply	other threads:[~2020-04-27 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  6:11 [dpdk-dev] [PATCH v1] maintainers: update for AMD xgbe and ccp crypto asomalap
2020-04-27  6:14 ` Kumar, Ravi1
2020-04-27 10:58   ` Ferruh Yigit
2020-04-27 11:24     ` Somalapuram, Amaranath
2020-04-27 12:07       ` Ferruh Yigit
2020-04-27 12:58         ` Aaron Conole
2020-04-27 15:00           ` Thomas Monjalon [this message]
2020-04-28 13:31             ` Aaron Conole
2020-04-27 20:05     ` 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=529334320.JY4mfKhWER@thomas \
    --to=thomas@monjalon.net \
    --cc=Amaranath.Somalapuram@amd.com \
    --cc=Ravi1.Kumar@amd.com \
    --cc=aconole@redhat.com \
    --cc=alialnu@mellanox.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=ferruh.yigit@intel.com \
    --cc=rasland@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.