All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wl@xen.org>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, famzheng@amazon.com,
	cardoe@cardoe.com, wl@xen.org, Bertrand.Marquis@arm.com,
	julien@xen.org, andrew.cooper3@citrix.com
Subject: Re: [PATCH v6 00/25] xl / libxl: named PCI pass-through devices
Date: Wed, 9 Dec 2020 16:14:33 +0000	[thread overview]
Message-ID: <20201209161433.d7xpx5zwtikd3fmk@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <alpine.DEB.2.21.2012081702420.20986@sstabellini-ThinkPad-T480s>

On Tue, Dec 08, 2020 at 05:02:50PM -0800, Stefano Stabellini wrote:
> The pipeline failed because the "fedora-gcc-debug" build failed with a
> timeout: 
> 
> ERROR: Job failed: execution took longer than 1h0m0s seconds
> 
> given that all the other jobs passed (including the other Fedora job), I
> take this failed because the gitlab-ci x86 runners were overloaded?
> 

The CI system is configured to auto-scale as the number of jobs grows.
The limit is set to 10 (VMs) at the moment.

https://gitlab.com/xen-project/xen-gitlab-ci/-/commit/832bfd72ea3a227283bf3df88b418a9aae95a5a4

I haven't looked at the log, but the number of build jobs looks rather
larger than when we get started. Maybe the limit of 10 is not good
enough?

Wei.


  reply	other threads:[~2020-12-09 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <160746448732.12203.10647684023172140005@600e7e483b3a>
2020-12-09  1:02 ` [PATCH v6 00/25] xl / libxl: named PCI pass-through devices Stefano Stabellini
2020-12-09 16:14   ` Wei Liu [this message]
2020-12-09 18:47     ` Stefano Stabellini
2020-12-10  2:41       ` Stefano Stabellini
2020-12-10 15:56         ` Wei Liu
2020-12-10 21:08           ` gitlab-docker-machine-oyster failure, Was: " Stefano Stabellini
2020-12-08 19:30 Paul Durrant

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=20201209161433.d7xpx5zwtikd3fmk@liuwe-devbox-debian-v2 \
    --to=wl@xen.org \
    --cc=Bertrand.Marquis@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=famzheng@amazon.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 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.