From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Ramon Fried <rfried.dev@gmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-05-20
Date: Mon, 23 May 2022 17:46:42 +0200 [thread overview]
Message-ID: <20220523174642.0c7a2fc2@windsurf> (raw)
In-Reply-To: <CAGi-RU+TOb+RCRzU=WeWw2DDwtcxk9_2gptgDpZJRZNonMGZUQ@mail.gmail.com>
Hello Ramon,
On Sat, 21 May 2022 19:47:24 +0300
Ramon Fried <rfried.dev@gmail.com> wrote:
> > Let me know if this helps!
> Yes.
> I managed to reproduce.
> How do I know if it's a regression, or a new configuration that was tested ?
> How was the configuration generated ?
Configurations are randomly generated. So it can either be a
configuration that was never tested before, or some other package that
was updated, and which has an impact on bitwise.
If you look at:
http://autobuild.buildroot.net/?reason=bitwise-0.43
You can see that the problem started appearing on May 1, 2022. It
affects only riscv64 and m68k/5208, which is extremely strange (which
only those architectures ?).
What can be tried is take the first of those build issues (from May 1),
reproduce it. And then checkout progressively older commits of
Buildroot (before May 1), and see when it started failing.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-23 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62886d67.1c69fb81.ac372.4710SMTPIN_ADDED_MISSING@mx.google.com>
[not found] ` <CAGi-RUKF09JmK_EACoQdBnS_Aw8G6Ep88Lx3rCHY3ZkxrqLvmQ@mail.gmail.com>
2022-05-21 14:44 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-05-20 Thomas Petazzoni via buildroot
2022-05-21 16:47 ` Ramon Fried
2022-05-23 15:46 ` Thomas Petazzoni via buildroot [this message]
2022-05-23 18:24 ` James Hilliard
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=20220523174642.0c7a2fc2@windsurf \
--to=buildroot@buildroot.org \
--cc=rfried.dev@gmail.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