From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: daggs <daggs@gmx.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-04
Date: Sat, 5 Nov 2022 13:34:17 +0100 [thread overview]
Message-ID: <20221105123417.GD3918838@scaer> (raw)
In-Reply-To: <trinity-5e5104ec-f62c-4643-b0ac-dfd2df7c6f42-1667640576096@3c-app-mailcom-bs11>
daggs, All,
On 2022-11-05 10:29 +0100, daggs spake thusly:
> > Sent: Saturday, November 05, 2022 at 9:37 AM
> > From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> > To: "Dagg Stompler" <daggs@gmx.com>
> > Subject: [autobuild.buildroot.net] Your daily results for 2022-11-04
> >
> > Build failures related to your defconfigs:
> > odroidc2 | https://gitlab.com/buildroot.org/buildroot/-/jobs/3267233868
> I've tried to reproduce it on latest master and the didn't reproduced, any idea how to reproduce it?
Err... This is simply a case where the disk is full:
xzcat /builds/buildroot.org/buildroot/dl/linux/linux-5.7.tar.xz | tar --strip-components=1 -C /builds/buildroot.org/buildroot/output/build/linux-5.7 -xf -
tar: drivers/watchdog/ftwdt010_wdt.c: Wrote only 4096 of 5381 bytes
tar: drivers/watchdog/gef_wdt.c: Cannot write: No space left on device
[...]
I don't think there is much issue to try to reproduce...
The runner is gcc159, so probably the disk got filled with build stuff
that did not get cleaned somehow...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-05 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 9:29 [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-04 daggs
2022-11-05 12:34 ` Yann E. MORIN [this message]
2022-11-05 12:50 ` daggs
2022-11-05 19:39 ` Thomas Petazzoni via buildroot
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=20221105123417.GD3918838@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=daggs@gmx.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox