From: Romain Naour <romain.naour@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>,
Buildroot Mailing List <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@smile.fr>
Subject: Re: [Buildroot] Failing tests on gitlab
Date: Tue, 9 Nov 2021 23:21:45 +0100 [thread overview]
Message-ID: <d13e37ce-b5d7-1dfe-e2fd-55887e9b6065@gmail.com> (raw)
In-Reply-To: <75228581-2222-7bea-1a96-20202d5c9015@mind.be>
Hello Arnout,
Le 09/11/2021 à 21:30, Arnout Vandecappelle a écrit :
> Hi all,
>
> The 2021.11-rc1 tag triggered a complete run of all the defconfigs and all the
> tests. 148 out of 725 jobs failed [0].
>
>
> There are two main causes for failures:
>
>
> 1. multiple definition of `yylloc' in u-boot or linux, e.g. [1]. This is
> triggered by the update of the docker image which has a new (host) gcc version
> 10, which defaults to -fno-common. Since there are more than 100 defconfigs that
> suffer from this problem, I think it would be best to solve this in uboot.mk and
> linux.mk rather than patching all the defconfigs. The fix is rather simple:
> remove the definition "YYLTYPE yylloc" from scripts/dtc/dtc-lexer.l. There's a
> slight complication that older kernels still have a "shipped" version of the
> file, but that can be solved with wildcard matching. This will need a bit of
> testing though to see how it behaves with older kernel/uboot versions, because
> that code *has* changed a couple of times. Also, for the cases where there's a
> shipped version, we should probably take care with the timestamps, to avoid that
> the c file is regenerated.
Actually this problem already affect users using a recent Linux distribution. We
used for too long the previous docker image based on Debian Stretch snapshot
(20171210).
>
>
> 2. Job timeout, e.g. [2]. I'm not entirely sure what this timeout is. It's
> definitely not the 6h job timeout, because the job hasn't even started. I
> suspect that there's some hidden overall 24h timeout for the entire pipeline,
> and that because we have so many jobs, we're not able to finish all of them
> within that time. The only solution for that is to add additional runners. So,
> if there's anybody out there with spare cycles, please volunteer to add a
> runner! You can contact me or Romain to learn how to set one up.
We can also reduce the number of long jobs:
http://patchwork.ozlabs.org/project/buildroot/patch/20211109220328.388872-1-romain.naour@gmail.com/
Building all boards defconfigs are time consuming for the CI and doesn't provide
much benefit. All defconfigs are build every weeks by a scheduled trigged pipeline.
>
>
> Hopefully, we can get better results by -rc2!
Well, except for the gcc 10 issue, the results are already good.
Only one issue left in the runtime testing!
Best regards,
Romain
>
>
> Regards,
> Arnout
>
>
>
> [0] https://gitlab.com/buildroot.org/buildroot/-/pipelines/404249740/failures
>
> [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/1758966028
>
> [2] https://gitlab.com/buildroot.org/buildroot/-/jobs/1758966567
>
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-11-09 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 20:30 [Buildroot] Failing tests on gitlab Arnout Vandecappelle
2021-11-09 22:21 ` Romain Naour [this message]
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=d13e37ce-b5d7-1dfe-e2fd-55887e9b6065@gmail.com \
--to=romain.naour@gmail.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
/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