From: David Marchand <david.marchand@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [RFC PATCH] ci: reduce examples built for static builds
Date: Tue, 17 Mar 2020 11:44:44 +0100 [thread overview]
Message-ID: <CAJFAV8wrLungaiXPgMp6-NzQHzxnYwJ1v6fPJax-Gz1ksHi=dg@mail.gmail.com> (raw)
In-Reply-To: <f7tmu8g6w2f.fsf@dhcp-25.97.bos.redhat.com>
On Mon, Mar 16, 2020 at 6:53 PM Aaron Conole <aconole@redhat.com> wrote:
>
> Bruce Richardson <bruce.richardson@intel.com> writes:
>
> > Static builds can take a lot of space, so reduce the number of examples
> > built when doing those static builds.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
>
> It looks good to me. I'll try a run with Ruifeng's no-huge series and
> see if I can trigger errors on my side (and then see what happens with
> the cache sizes, too). Might take some time as I adjust some things
> here.
- The disk quota issue was reproduced on master without Ruifeng patches:
https://travis-ci.com/github/DPDK/dpdk/jobs/298584616
https://travis-ci.com/github/DPDK/dpdk/jobs/298858638
And for this, the cache is not really big.
cache-arm64-linux-bionic-a550182015679db90d1e0a2460464d106712e1c2c29f3efc7db1dc1b6fd86ebb--compiler-gcc.tgz
last modified: 2020-03-16 11:28:59 size: 160.84 MiB
I remember bigger caches in the past.
I deleted this job cache and restarted the first job, and it passed.
Restarted again, and then it failed o_O.
- So I went and restarted a couple of times both of those jobs
(leaving the cache as is, which now contains 60MB of data).
I get random failures.
It does not seem to depend on the system: it failed once on
f432ae31-ccac-4caa-92ca-8156fabad86f@6138.lxd-arm64-02-com, then
worked later.
hostname: f432ae31-ccac-4caa-92ca-8156fabad86f@6138.lxd-arm64-02-com: KO
hostname: edb47637-c344-4a03-8538-711046469ad4@14975.lxd-arm64-01-com: ok
hostname: 386fc0aa-a84a-4a77-b2bd-e1e754bfe51d@14975.lxd-arm64-01-com: ok
hostname: 43c67d46-c94c-498a-816f-2eddce2a58a6@14975.lxd-arm64-01-com: ok
hostname: f432ae31-ccac-4caa-92ca-8156fabad86f@6138.lxd-arm64-02-com: ok
hostname: a59a18bb-6f7f-4c0f-bb98-a8075cb61063@6138.lxd-arm64-02-com: KO
hostname: 743ab211-a1ba-480e-be85-2b1c01ce8b86@14975.lxd-arm64-01-com: ok
hostname: 8ac56afe-df63-464a-8c85-9b2e8b141b94@25560.lxd-arm64-03-com: ok
hostname: 306788d5-7614-4e9d-856a-1043cb4aeaf4@6138.lxd-arm64-02-com: KO
hostname: b6c5307c-7e65-4feb-a46a-7e2bc9a17fb8@6138.lxd-arm64-02-com: ok
--
David Marchand
next prev parent reply other threads:[~2020-03-17 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 17:09 Bruce Richardson
2020-03-16 17:36 ` Aaron Conole
2020-03-17 10:44 ` David Marchand [this message]
2020-03-17 12:48 ` Aaron Conole
2020-03-16 18:37 ` Thomas Monjalon
2020-03-18 9:45 ` Bruce Richardson
2020-04-17 21:58 ` 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='CAJFAV8wrLungaiXPgMp6-NzQHzxnYwJ1v6fPJax-Gz1ksHi=dg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ruifeng.wang@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).