On Thu, Nov 16, 2017 at 4:58 PM, akuster808 wrote:
>
> Version 2 of patches came in between builds so lots of
> "version-going-backwards"
>
>
> == Failed tasks 2017-11-15 ==
>
> INFO: jenkins-job.sh-1.8.43 Complete log available at
>
Version 2 of patches came in between builds so lots of
"version-going-backwards"
== Failed tasks 2017-11-15 ==
INFO: jenkins-job.sh-1.8.43 Complete log available at
http://logs.nslu2-linux.org/buildlogs/oe/world/sumo/log.report.20171116_060616.log
=== common (3) ===
*
On Thu, Nov 9, 2017 at 8:14 AM Martin Jansa wrote:
> FYI: You can use PV = "2.0.99+2.1.0-beta3" to make sure that it's sorted
> higher than any 2.0.* release and that final 2.1.0 again sorts higher than
> this beta3 without PE bump.
>
There are some packages which
On 11/01/2017 08:30 AM, Khem Raj wrote:
> Hi Martin/Armin
>
> I looked at the first report with musl from Martin. Most of the
> failures are familiar except 2 I think which I plan to look at. I
> haven't blacklisted them intentionally, to get annoyed enough to keep
> fixing them as time permits.
FYI: You can use PV = "2.0.99+2.1.0-beta3" to make sure that it's sorted
higher than any 2.0.* release and that final 2.1.0 again sorts higher than
this beta3 without PE bump.
On Thu, Nov 9, 2017 at 4:23 PM, akuster808 wrote:
>
>
> On 11/08/2017 11:05 AM, Martin Jansa
On 11/08/2017 11:05 AM, Martin Jansa wrote:
> The only change from previous report is slightly newer oe-core and bitbake.
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='4'|Failed tasks
On Thu, Nov 9, 2017 at 10:43 AM, Andrea Adami wrote:
> On Wed, Nov 8, 2017 at 8:05 PM, Martin Jansa wrote:
>> The only change from previous report is slightly newer oe-core and bitbake.
>>
>>
>> http://www.openembedded.org/wiki/Bitbake_World_Status
On Wed, Nov 8, 2017 at 8:05 PM, Martin Jansa wrote:
> The only change from previous report is slightly newer oe-core and bitbake.
>
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date
Hi Martin/Armin
I looked at the first report with musl from Martin. Most of the
failures are familiar except 2 I think which I plan to look at. I
haven't blacklisted them intentionally, to get annoyed enough to keep
fixing them as time permits.
infact none of the build failures are due to musl
Hi Armin,
I'll leave this question to Khem, this was my just 2nd build with musl,
Khem is doing musl builds for very long time and fixing all the issue he
finds, maybe some of the issues detected in world builds already have fixes
in Khem's queue.
Regards,
On Wed, Nov 1, 2017 at 5:53 AM,
Martin,
On 10/31/2017 01:58 PM, Martin Jansa wrote:
> With 2 pending patches from Khem to build systemd with musl:
> 62c7c98 systemd: Fix build on musl
> de68252 systemd: Fix build with musl/mips64
> the qemux86+musl build was able to progress much further and fewer ERROR
> messages were shown.
With 2 pending patches from Khem to build systemd with musl:
62c7c98 systemd: Fix build on musl
de68252 systemd: Fix build with musl/mips64
the qemux86+musl build was able to progress much further and fewer
ERROR messages were shown. Basically only uim recipe now depends on
glibc and fails to be
This is first report which includes qemuarm64 MACHINE.
Next one will use musl for qemux86 build (other MACHINEs will continue to
use default glibc).
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='4'|Failed tasks
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks !!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64 ||all ||already-stripped ||libdir
||textrel ||build-deps
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks !!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64 ||all ||already-stripped ||libdir
||textrel ||build-deps
The qemux86-64 failures (except mongodb do_patch) are caused by rpcgen
removal from HOSTTOOLs, will drop that change from next run, but it
also means that latest Gentoo glibc (drops rpc support) cannot be used
for OE builds anymore.
http://www.openembedded.org/wiki/Bitbake_World_Status
==
Done
https://github.com/shr-project/jenkins-jobs/commit/dbb5e4e4e2c5821381eda729ab746a21238c8801
On Sat, Sep 16, 2017 at 5:01 PM, Khem Raj wrote:
> On Sat, Sep 16, 2017 at 7:41 AM, Martin Jansa
> wrote:
> > Just the commit IDs from the top won't be
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
On Sat, Sep 16, 2017 at 7:41 AM, Martin Jansa wrote:
> Just the commit IDs from the top won't be very useful, because it's from
> jansa/master branches which are rebased even more often than master-next.
>
> If you really want to see them, then there are links to the build
On Sat, Sep 16, 2017 at 2:00 AM, Martin Jansa wrote:
> Probably is, qemux86 was built from slightly older metadata, so probably
> including previous versions of your klibc changes.
>
> I know it's confusing in the report, but still each build takes around 24
> hours per
Probably is, qemux86 was built from slightly older metadata, so probably
including previous versions of your klibc changes.
I know it's confusing in the report, but still each build takes around 24
hours per machine and I have only 2 builders. e.g. this qemux86 build was
started 20170912_234104
On Fri, Sep 15, 2017 at 3:08 PM, Martin Jansa wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='3'|Failed tasks !!|Signatures !!colspan='14'|QA
> !!Comment
> |-
> ||
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks !!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64 ||all ||already-stripped ||libdir
||textrel ||build-deps
qemux86 shows a bit more failures, because it's built from slightly
older metadata (I've removed some pending changes from master-next after
that build).
Also big chunk of meta-networking changes was finally merged, so the list
of tested changes in next report should be significantly shorter
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
On Sat, Sep 2, 2017 at 11:49 PM, Martin Jansa wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='3'|Failed tasks!!|Signatures
> !!colspan='14'|QA !!Comment
> |-
> || ||qemuarm
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
3 unblacklisted recipes are still causing issues, so unblacklist will
be dropped now from master-next (the recipes will stay with
PNBLACKLIST for a bit longer) and removal of other blacklisted recipes
will be merged later today.
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
And this one with Qt 5.9.2
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks!!|Signatures !!colspan='14'|QA
!!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64 ||all ||already-stripped ||libdir
On Sat, Aug 26, 2017 at 1:59 PM, Martin Jansa
wrote:
> Issues in meta-qt5 caused by security_flags.inc were fixed in this round, for
> next round I'll test fixed 5.9.0 upgrade and then final 5.9.2 upgrade.
>
>
> Thanks for fixes for QA issues, few more are included in
Issues in meta-qt5 caused by security_flags.inc were fixed in this
round, for next round I'll test fixed 5.9.0 upgrade and then final
5.9.2 upgrade.
Thanks for fixes for QA issues, few more are included in next round.
Hopefully we'll get back to clean state before Rocko is released.
This
Openssl was reverted back to 1.0 version being default, so there is
fewer errors now, but there was also a fix for package.bbclass:
http://lists.openembedded.org/pipermail/openembedded-core/2017-August/141127.html
which causes many do_package_qa tasks to fail.
Please help by sending fixes for
Another build with openssl-1.1.
Next build will use openssl-1.0 again.
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA
Most of these issues are probably caused by openssl upgrade in oe-core.
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA
On Sat, Aug 12, 2017 at 11:53 AM, Martin Jansa wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='3'|Failed tasks
> !!|Signatures
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
It got significantly worse again.
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
qemux86 shows few more issues, because it was built from slightly
older metadata (I've dropped 4 patches from master-next after this build
- before qemux86-64 and qemuarm were executed).
== Number of issues - stats ==
{| class='wikitable'
On Tue, Jul 18, 2017 at 4:22 AM, Martin Jansa wrote:
> I don't know what setup you're using, but my is described here:
> http://www.openembedded.org/wiki/Bitbake_World_Status_Setup
>
interesting parts are
I don't know what setup you're using, but my is described here:
http://www.openembedded.org/wiki/Bitbake_World_Status_Setup
and the current version published with the results:
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemuarm.20170717_011149.log/world_fixes.inc
now I see
firefox and ipppool seems to not fail for me here.
so I wonder what might be different.
On Mon, Jul 17, 2017 at 11:49 AM, Martin Jansa wrote:
> The v2s of those patches really helped:
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues -
The v2s of those patches really helped:
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
||
This time with conf/distro/include/security_flags.inc included as
requested by Khem
systemd-bootchart is broken since glibc upgrade, Khem already suggested
the fix, hopefully Chen Qi or someone else will fix it soon.
nmon is broken even without security_flags.inc but v2 from Khem looks
like it
On Fri, Jul 14, 2017 at 10:03 AM, Martin Jansa wrote:
> OK, I'll merge current batch of pending changes and before next build I'll
> include
> conf/distro/include/security_flags.inc
>
> Is that all I need to do?
>
yep
> On Fri, Jul 14, 2017 at 6:49 PM, Khem Raj
OK, I'll merge current batch of pending changes and before next build I'll
include
conf/distro/include/security_flags.inc
Is that all I need to do?
On Fri, Jul 14, 2017 at 6:49 PM, Khem Raj wrote:
> Hi Martin
>
> On Fri, Jul 14, 2017 at 9:43 AM, Martin Jansa
Hi Martin
On Fri, Jul 14, 2017 at 9:43 AM, Martin Jansa wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
The results looks good. I wanted to suggest to start building with
hardening flags on if possible. I have ensured that there are no
regressions with
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
There is pending fix for valgrind and klibc, I've dropped udevil until v2 is
sent, so
hopefully next build will show only new issues caused by glibc upgrade.
== Number of issues - stats ==
{| class='wikitable'
!|Date
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
On Mon, Jul 3, 2017 at 4:20 AM, Martin Jansa wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='3'|Failed tasks!!|Signatures
> !!colspan='14'|QA !!Comment
> |-
> || ||qemuarm
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
On Sun, Jun 18, 2017 at 10:19 PM, Martin Jansa wrote:
> Firefox and chromium-* fixed few more to go, but not bad for big gcc
> upgrade.
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date
Firefox and chromium-* fixed few more to go, but not bad for big gcc
upgrade.
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
http://www.openembedded.org/wiki/Bitbake_World_Status
This time with gcc7 and with complete QA list, because sstate (and
prserv cache) were dropped for all the builds).
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures !!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
This might be the last report from pyro, I'll update meta-oe pyro from master
once meta-networking changes are merged as well.
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
One of the builds was showing tiptop failure:
http://errors.yoctoproject.org/Errors/Details/141293/
I wonder if there is still some undeterministic behavior related to flex.
It shouldn't be able to use host's flex due to HOSTTOOLS filtering.
It doesn't have the dependency on flex-native, but
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
On Mon, Apr 03, 2017 at 02:57:01PM +0200, Andrea Adami wrote:
> On Mon, Apr 3, 2017 at 2:34 PM, Martin Jansa wrote:
> > On Mon, Apr 03, 2017 at 02:17:49PM +0200, Martin Jansa wrote:
> >> qemux86 shows more failures, I've dropped few master-next changes
> >> after this
On Mon, Apr 3, 2017 at 2:34 PM, Martin Jansa wrote:
> On Mon, Apr 03, 2017 at 02:17:49PM +0200, Martin Jansa wrote:
>> qemux86 shows more failures, I've dropped few master-next changes
>> after this build.
>
> I've noticed that the report doesn't cover all currently
On Mon, Apr 03, 2017 at 02:17:49PM +0200, Martin Jansa wrote:
> qemux86 shows more failures, I've dropped few master-next changes
> after this build.
I've noticed that the report doesn't cover all currently triggered QA
issues at least these 2 were missing in the report:
count: 27 issue:
qemux86 shows more failures, I've dropped few master-next changes
after this build.
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
opencv issue is fixed by removing one of pending master-next changes:
gflags: correct S and update library install directory
and ovmf was fixed in newer oe-core, so next report should be clean, unless
one of 50+ new changes break more stuff.
== Number of issues - stats ==
{| class='wikitable'
On Wed, 2017-03-29 at 12:14 +0200, Martin Jansa wrote:
> > Can individual recipes choose to be built using the normal ld?
>
>
>
> yes, see example in:
> meta/recipes-bsp/u-boot/u-boot.inc
>
> meta/recipes-support/libunwind/libunwind_git.bb
Thanks. I'll try to do something similar.
> but it
> Can individual recipes choose to be built using the normal ld?
yes, see example in:
meta/recipes-bsp/u-boot/u-boot.inc
meta/recipes-support/libunwind/libunwind_git.bb
but it was working with older binutils, so maybe worth tracking down where
it got borken.
On Wed, Mar 29, 2017 at 11:38 AM,
On Wed, 2017-03-29 at 11:14 +0200, Martin Jansa wrote:
> On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> > On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > > INFO: jenkins-job.sh-1.8.19 Complete log available at
> > >
On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > INFO: jenkins-job.sh-1.8.19 Complete log available at
> > http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
>
> That used OE-core 552bd78,
On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> INFO: jenkins-job.sh-1.8.19 Complete log available at
> http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
That used OE-core 552bd78, if I read this right:
== Tested changes (not included in master
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
This time executed without sstate-cache and downloads directory from
previous builds, so there is complete list of QA issues and couple
do_fetch failures.
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed
For next run I've removed sstate-cache and downloads directory to detect
broken SRC_URIs, here is the list:
/home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-extended/libqb/libqb_0.17.2.bb:do_fetch
On 03/16/2017 04:34 PM, Martin Jansa wrote:
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
||
On 03/16/2017 04:34 PM, Martin Jansa wrote:
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
||
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
On Sat, Mar 11, 2017 at 07:02:53PM +0100, Martin Jansa wrote:
> This time the results are very inconsistent across different MACHINEs
> because they were using significantly different metadata.
>
> qemuarm is oldest 3 from 4 failures were causes by pending meta-oe
> changes which I've removed
1 - 100 of 500 matches
Mail list logo