From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] buildchroot: Permanently mount '/dev', '/sys' and '/proc'
Date: Tue, 6 Feb 2018 10:38:07 +0100 [thread overview]
Message-ID: <4364b432-f199-d2f7-3d26-32b0cfc91c0b@siemens.com> (raw)
In-Reply-To: <b5d2e81d-7a3f-6908-f3a0-5bfb617e8f9c@siemens.com>
On 2018-02-05 19:06, Jan Kiszka wrote:
>>> And when I restart the build that I interrupt after buildchroot was long
>>> finished, that task is still rebuild - and that fails, maybe because of
>>> preexisting artifacts.
>>
>> That's the known problem, we have no do_clean task implemented. Re-run
>> on existing tree is not officially supported for now.
>
> That should be fixed, or our turn-around times for Isar development will
> explode!
This is really an urgent must-fix. I'm doing full rebuilds over and over
again now, just to test small changes down the pipeline.
Do you already have an idea how to prevent the buildchroot rebuild? I
suppose it's caused by the new prepare task, right? Can we achieve that
without invalidating the buildchroot setup?
Jan
next prev parent reply other threads:[~2018-02-06 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 16:43 [PATCH 0/2] mounts for buildchroot Alexander Smirnov
2018-02-05 16:43 ` [PATCH 1/2] buildchroot: Do not call 'apt-get update' Alexander Smirnov
2018-02-05 16:51 ` Jan Kiszka
2018-02-05 17:06 ` Alexander Smirnov
2018-02-05 17:25 ` Jan Kiszka
2018-02-06 9:12 ` Alexander Smirnov
2018-02-06 9:13 ` Alexander Smirnov
2018-02-06 9:38 ` Jan Kiszka
2018-02-05 16:43 ` [PATCH 2/2] buildchroot: Permanently mount '/dev', '/sys' and '/proc' Alexander Smirnov
2018-02-05 16:53 ` Jan Kiszka
2018-02-05 17:16 ` Alexander Smirnov
2018-02-05 17:30 ` Jan Kiszka
2018-02-05 17:32 ` Jan Kiszka
2018-02-05 17:50 ` Jan Kiszka
2018-02-05 18:03 ` Jan Kiszka
2018-02-05 18:03 ` Alexander Smirnov
2018-02-05 18:06 ` Jan Kiszka
2018-02-06 9:38 ` Jan Kiszka [this message]
2018-02-06 9:43 ` Alexander Smirnov
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=4364b432-f199-d2f7-3d26-32b0cfc91c0b@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.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