From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-13
Date: Mon, 16 Sep 2019 23:36:23 +0200 [thread overview]
Message-ID: <20190916233623.676bd27d@windsurf> (raw)
In-Reply-To: <c7f9da15-ae5d-c457-955e-94463962c10b@arcturusnetworks.com>
Hello Oleksandr,
On Mon, 16 Sep 2019 15:19:15 -0400
Oleksandr G Zhadan <oleks@arcturusnetworks.com> wrote:
> I? re-built and re-tested images from fresh today's clone of buildroot
> on both, uCLS1012A and uCP1020 modules . Everything works OK on real
> hardware.
>
> I am not familiar with your run-time test procedures and have not enough
> info to "fix" working images to pass that test.
defconfigs are not runtime tested, they are only build tested.
>
> Base on the error from link you pointed to:
>
> ERROR: Job failed (system failure): Error response from daemon: mkdir
> /home/docker/aufs/mnt/2d951eb14738916f4779f5f7633bd64272a8286b6fcac64f191e7c5d61b0e678-init:
> no space left on device (executor_docker.go:743:0s)
As you can see from the error, it was just the build machine that was
used to build these particular defconfigs that ran out of disk space.
I fixed the disk space issue on this build server, and restarted a new
test of all defconfigs. This new test is at
https://gitlab.com/buildroot.org/buildroot/pipelines/82198743/builds,
and you can see that both of your defconfigs built correctly.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2019-09-16 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cmu-lmtpd-8902-1568441566-0@mail>
[not found] ` <c7f9da15-ae5d-c457-955e-94463962c10b@arcturusnetworks.com>
2019-09-16 21:36 ` Thomas Petazzoni [this message]
2019-09-16 21:41 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-13 Oleksandr G Zhadan
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=20190916233623.676bd27d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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