public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org, steve@sakoman.com
Subject: Re: [PATCH 0/5] linux-yocto: consolidated pull request
Date: Mon, 04 May 2020 09:30:57 +0100	[thread overview]
Message-ID: <70c6d988d291d1e2953d4b57cc9e88c146785d14.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1588520452.git.bruce.ashfield@gmail.com>

Hi Bruce,

On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Hi all,
> 
> Here are the -stable updates I've collected since m3 of dunfell. I
> ran things through the autobuilder, and no new kernel issues were
> picked up.
> 
> The -dev bump is good for master, while all of the 5.4-stable bumps
> are good for both master and dunfell.

I pulled these into master-next and saw reproducibility issues. I
wondered why your test build didn't show it, turns out it also did:

https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024

2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException: 

AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk

master-next was:

https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900

and friends.

Cheers,

Richard


  parent reply	other threads:[~2020-05-04  8:31 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2020-05-03 15:44 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.28 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 2/5] linux-yocto/5.4: update to v5.4.32 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 3/5] linux-yocto/5.4: update to v5.4.34 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 4/5] linux-yocto/5.4: update to v5.4.38 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 5/5] linux-yocto-dev: bump to v5.7-rc Bruce Ashfield
2020-05-04  8:30 ` Richard Purdie [this message]
2020-05-04 12:56   ` [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
     [not found]   ` <160BD489BF65999D.29536@lists.openembedded.org>
2020-05-04 13:06     ` [OE-core] " Bruce Ashfield
2020-05-04 13:24       ` Richard Purdie
2020-05-04 13:34         ` Bruce Ashfield
2020-05-07 18:14           ` Steve Sakoman
2020-05-07 19:18             ` Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2024-08-11 18:04 bruce.ashfield
2024-08-12  9:47 ` Richard Purdie
2024-08-12 12:47   ` Bruce Ashfield
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29  1:29 Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-05-01  1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30   ` Bruce Ashfield
2015-05-02  8:13     ` Martin Jansa
2015-05-03  2:50       ` Bruce Ashfield
2015-05-06 14:42         ` Martin Jansa
2015-05-06 14:58           ` Bruce Ashfield
2015-05-06 15:33             ` Martin Jansa
2015-05-06 15:44               ` Richard Purdie
2015-05-06 16:07                 ` Martin Jansa
2015-05-06 17:46                   ` Bruce Ashfield
2015-05-06 21:32                     ` Richard Purdie
2015-05-06 22:49                       ` Martin Jansa
2015-05-07 15:33                         ` Bruce Ashfield
2015-05-07  6:33               ` Khem Raj
2015-05-02  9:00     ` Richard Purdie
2015-05-03  2:53       ` Bruce Ashfield
2015-05-03  3:52       ` Bruce Ashfield
2015-05-03 10:48         ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04  4:36   ` Bruce Ashfield
2015-05-04 15:01   ` Bruce Ashfield
2015-03-24 18:57 Bruce Ashfield
2015-03-25  9:26 ` Richard Purdie
2015-03-25 12:13   ` Bruce Ashfield
2015-03-25 13:26     ` Bruce Ashfield
2015-03-25 13:52       ` Richard Purdie
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24  6:33 ` Saul Wold
2013-08-24 13:34   ` Bruce Ashfield
2013-08-24 13:45     ` Bruce Ashfield
2013-08-24 13:50       ` Saul Wold
2013-08-24 13:53         ` Bruce Ashfield
2013-08-24 14:47         ` Bruce Ashfield
2013-08-24 14:59         ` Bruce Ashfield
2013-08-24 16:05         ` Bruce Ashfield
2012-02-05  6:31 Bruce Ashfield
2012-02-08  4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold

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=70c6d988d291d1e2953d4b57cc9e88c146785d14.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.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