From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Help with intermittent autobuilder exposed bugs
Date: Mon, 21 Oct 2019 17:48:39 +0100 [thread overview]
Message-ID: <46eada65-ea51-a311-3ebc-af0ce5c2d18b@intel.com> (raw)
In-Reply-To: <db51470b-812f-d60d-b9e9-7741c536f3e2@gmail.com>
On 20/10/2019 16:54, akuster808 wrote:
>
>
> On 10/20/19 5:54 AM, Richard Purdie wrote:
>> We have a situation brewing on the autobuilder. Each run there are some
>> bugs which sometimes can appear. Law of averages says one or more of
>> the issues below will now appear as we have so many of them. The
>> project's standard processes aren't helping to capture the issues or
>> track them down.
>>
>> With the release mostly sorted out from my perspective I can look at
>> some of the other health aspects of the project.
>>
>> In theory SWAT should have filed bugs for these. In most cases they
>> haven't. If they did, we'd discuss them at triage, decide they looked
>> hard and then there wouldn't be anyone to "assign" to them so they'd
>> most likely end up on my plate anyway. I find it hard to know what to
>> do with these. I already have a load in my bug backlog which I've not
>> gotten sorted out so adding more probably won't help.
>>
>> To summarise the issues [just from the last few builds]:
>
> I'll get started logging bugs
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/756
>> oe-selftest recipetool.RecipetoolTests.test_recipetool_load_plugin
>> RP has a long standing bug:
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13070
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/1177
>> qa-extras2 step2c testimage logrotate.LogrotateTest.test_2_logrotate
>> for core-image-sato
>> [no open bug?]
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13602
>
>
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/441
>> oe-selftest devtool.DevtoolExtractTests.test_devtool_deploy_target
>> [no open bug, unhelpful backtrace from tinfoil]
>
> Bug #13601, seen with stable/warrior-nmut and on same host - fedora30-ty-1
>
>
>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/440
>> oe-sefltest signing.LockedSignatures.test_locked_signatures
>> [no open bug or any idea why it failed]
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13605
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/440
>> oe-selftest distrodata.Distrodata.test_maintainer
>> [no open bug, same unhelpful backtrace from tinfoil]
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13604
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/440
>> oe-selftest reproducible.ReproducibleTests.test_reproducible_builds
>> [no open bug?, fedora specific perldoc reproducibility issue]
> Think its the same as
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13602
I think you got the wrong number?
If you meant the bug where pod2man writes its version number into the
manpages then that isn't Fedora-specific, nor impacts these files:
perl-dbg_5.30.0-r0_amd64.deb
perl-module-config-heavy_5.30.0-r0_amd64.deb
perl-module-digest-md5_5.30.0-r0_amd64.deb
perl-module-encode-byte_5.30.0-r0_amd64.deb
perl-module-encode-cn_5.30.0-r0_amd64.deb
perl-module-encode-ebcdic_5.30.0-r0_amd64.deb
perl-module-encode-jp_5.30.0-r0_amd64.deb
perl-module-encode-kr_5.30.0-r0_amd64.deb
perl-module-encode-symbol_5.30.0-r0_amd64.deb
perl-module-encode-tw_5.30.0-r0_amd64.deb
perl-module-encode_5.30.0-r0_amd64.deb
perl-module-tie-hash-namedcapture_5.30.0-r0_amd64.deb
perl-ptest_5.30.0-r0_amd64.deb
perl-src_5.30.0-r0_amd64.deb
I don't actually have a Fedora machine to hand right now but if anyone
does, this should be fairly trivial to replicate/isolate.
Ross
next prev parent reply other threads:[~2019-10-21 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 12:54 Help with intermittent autobuilder exposed bugs Richard Purdie
2019-10-20 15:54 ` akuster808
2019-10-21 16:48 ` Ross Burton [this message]
2019-10-21 16:50 ` Ross Burton
2019-10-21 17:22 ` Joshua Watt
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=46eada65-ea51-a311-3ebc-af0ce5c2d18b@intel.com \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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