On Fri, 2022-02-25 at 13:58 -0600, Joshua Watt wrote:
On Fri, Feb 25, 2022 at 12:50 PM Steve Sakoman <steve@...> wrote:
I agree. I assume the change is simple enough to make that we can
On Fri, Feb 25, 2022 at 8:09 AM Richard Purdie
I support this. It has been quite some time since dunfell encountered
As the project develops, some tests are valuable and some become less valuable
When we first started reproducible builds work, testing reproducibility heavily
across multiple distros highlighted some unusual bugs and let us improve things.
We therefore currently run a-full with the targets:
I've noticed we pretty much always see the same set of failures with these
targets now, i.e. if one fails, they all fail the same way.
Those targets are heavy builds which don't reuse sstate for one of the build
streams and hence load the autobuilder heavily.
I'm thinking they've served their purpose and that a-full should go back to just
the randomly selected reproduiclbe target.
Does anyone feel we shouldn't do that?
a distro specific reproducibility issue.
bring them back easily if we think it might be helpful is some
Yes, I'll leave the targets available, we'd just run them manually or re-enable
them but I'd take them off a-full for now.
Also, just to clarify, those workers will still contribute to the
initial sstate, so they will still help find cross-host reproducible
problems, they just might not find it themselves?