public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v4 0/6] Python refactoring
Date: Mon, 11 Mar 2019 13:22:36 +0100	[thread overview]
Message-ID: <ea3da10efa03a37a4302a70d31629459b181e02d.camel@siemens.com> (raw)
In-Reply-To: <92b2d5da-3e0e-1721-4023-4b76395055d4@ilbers.de>

On Mon, 2019-03-11 at 11:10 +0100, Maxim Yu. Osipov wrote:
> Hi Claudius,
> 
> On 3/4/19 5:21 PM, Claudius Heine wrote:
> > Hi,
> > 
> > On 04/03/2019 14.07, [ext] claudius.heine.ext@siemens.com wrote:
> > > From: Claudius Heine <ch@denx.de>
> > > 
> > > Hi,
> > > 
> > > I just took Haralds patchset + Maxims rebase and fixed it up.
> > > 
> > > There was just a tiny change necessary, I added that in an
> > > additional 
> > > patch.
> > > It builds on my machine (qemuamd64) and I am currently testing it
> > > on 
> > > isar-ci.
> > 
> > Ok I run this patchset two times on the isar-ci now. The exact
> > same 
> > commit id failed the first time after ~10 minutes [1] and will go
> > green 
> > the second time [2] (Not completely finished yet, but it looks good
> > so 
> > far after 1h50m.)
> > 
> > We really should fix the nondeterminism in the CI.
> 
>  From the first glance the error caused build failure was
> 
> E: Couldn't download packages: locales
> 
> How are you going to fix such "non-determinism"?

Such problems are not an issue in OE so they should not be an issue in
Isar.

Claudius


  reply	other threads:[~2019-03-11 12:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 13:07 claudius.heine.ext
2019-03-04 13:07 ` [PATCH v4 1/6] Remove all uses of subprocess.call(shell=True) claudius.heine.ext
2019-03-04 13:07 ` [PATCH v4 2/6] isar-bootstrap-helper: get_deb_host_arch: fix decoding claudius.heine.ext
2019-03-04 13:07 ` [PATCH v4 3/6] Use modern python formatting claudius.heine.ext
2019-03-04 13:07 ` [PATCH v4 4/6] image: Remove recursion in get_image_name claudius.heine.ext
2019-03-04 13:08 ` [PATCH v4 5/6] wic: Refactor fakeroot script claudius.heine.ext
2019-03-04 13:08 ` [PATCH v4 6/6] Fix python style claudius.heine.ext
2019-03-04 16:21 ` [PATCH v4 0/6] Python refactoring Claudius Heine
2019-03-11 10:10   ` Maxim Yu. Osipov
2019-03-11 12:22     ` Claudius Heine [this message]
2019-03-12 14:56 ` Claudius Heine
2019-03-12 15:26   ` Jan Kiszka
2019-03-12 15:34     ` Claudius Heine
2019-03-12 16:03       ` Jan Kiszka
2019-03-12 16:17         ` Claudius Heine
2019-03-12 22:36 ` Maxim Yu. Osipov

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=ea3da10efa03a37a4302a70d31629459b181e02d.camel@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /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