From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v3 0/8] Cleanup rootfs creation
Date: Thu, 25 Apr 2019 11:07:58 +0300 [thread overview]
Message-ID: <1aa42268-5f7e-355b-e980-eebe9df4a526@ilbers.de> (raw)
In-Reply-To: <561243bd-3aa7-5f8a-83c5-4137660354fb@siemens.com>
Hi Claudius,
On 4/25/19 10:01 AM, Claudius Heine wrote:
> Hi Maxim,
>
> On 25/04/2019 09.55, Maxim Yu. Osipov wrote:
>> Hi Claudius,
>>
>> On 4/25/19 8:40 AM, Claudius Heine wrote:
>>> Hi Maxim,
>>>
>>> On 25/04/2019 08.03, Maxim Yu. Osipov wrote:
>>>>
>>>> Tried this series with fast ci build ("scripts/ci_build.sh -q -f"-
>>>> similar problems as before.
>>>> http://isar-build.org:8080/job/isar_mosipov_develop/98/console
>>>>
>>>> I observe the same errors on my host.
>>>
>>> So what do we do then when the CI is not reproducible?
>>>
>>> I am at a loss at how to investigate an error that does not happen
>>> when I build on isar-build or on my local host and only when you
>>> build it on isar-build or at your host.
>>
>> Do you mean that this problem is not reproduced when you run "fast" CI
>> build (ci_build.sh -q -f) on your PC?
>
> I don't do ci_builds locally, because that is the job of the CI. I just
> build one target that might be affected of the specific change.
That's the reason why you can't reproduce the problem.
>>
>>> Any suggestions?
>>
>> Yes, sure. We will create an additional project for you on
>> isar-build.org to launch "fast" CI build.
>
> So you suggest that I should now test every patch I send two times, once
> for each different CI configuration manually?
There is another option. I may reconfigure your current project to fast
build. Should I do that?
Maxim.
> Claudius
>
>>
>> Maxim.
>>
>>> Claudius
>>>
>>>>
>>>> Maxim.
>>>>
>>>> On 4/24/19 11:27 AM, claudius.heine.ext@siemens.com wrote:
>>>>> From: Claudius Heine <ch@denx.de>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I could not reproduce the raspberrypi issue Maxim found in his CI
>>>>> build:
>>>>> http://isar-build.org:8080/job/isar_mosipov_develop/91/consoleText
>>>>>
>>>>> This is my build log:
>>>>> http://isar-build.org:8080/job/isar_claudius_ilbers-ci/54/consoleText
>>>>>
>>>>> Only the module loading fails, which Maxim stated he will look into.
>>>>>
>>>>> This patchset uses still the 'old' style for refactoring/cleanup
>>>>> patchsets,
>>>>> until I automated the official patch submission process as
>>>>> documented by the
>>>>> CONTRIBUTERS policy.
>>>>>
>>>>> You can find the whole patchset in under this url:
>>>>>
>>>>> https://github.com/cmhe/isar/tree/ch/cleanup
>>>>>
>>>>> regards,
>>>>> Claudius
>>>>>
>>>>> changes from v2:
>>>>> - replaced 'ROOTFS_ARCH' with 'HOST_ARCH' in sdkchroot.bb to avoid
>>>>> populate_sdk issue
>>>>>
>>>>> changes from v1:
>>>>> - fixed typo in commit message
>>>>>
>>>>> Claudius Heine (8):
>>>>> isar-boostrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to
>>>>> base.bbclass
>>>>> move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to
>>>>> isar-bootstrap
>>>>> buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH
>>>>> isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR
>>>>> bitbake.conf: remove unneeded and differently used variables
>>>>> image.bbclass: make IMAGE_ROOTFS overwritable
>>>>> bitbake.conf: set default QEMU_ARCH variables
>>>>> buildchroot/configscript: make creation of builder uid/gid
>>>>> idempotent
>>>>>
>>>>> meta/classes/base.bbclass | 9 +++++++++
>>>>> meta/classes/buildchroot.bbclass | 2 +-
>>>>> meta/classes/image-sdk-extension.bbclass | 2 +-
>>>>> meta/classes/image.bbclass | 2 +-
>>>>> meta/classes/isar-bootstrap-helper.bbclass | 14
>>>>> --------------
>>>>> meta/conf/bitbake.conf | 13
>>>>> ++++++++-----
>>>>> .../isar-bootstrap/isar-bootstrap-host.bb | 11 +++--------
>>>>> .../isar-bootstrap/isar-bootstrap-target.bb | 6 +-----
>>>>> .../recipes-core/isar-bootstrap/isar-bootstrap.inc | 1 +
>>>>> .../buildchroot/buildchroot-host.bb | 1 +
>>>>> meta/recipes-devtools/buildchroot/buildchroot.inc | 3 +--
>>>>> .../buildchroot/files/configscript.sh | 4 ++--
>>>>> meta/recipes-devtools/sdkchroot/sdkchroot.bb | 3 +--
>>>>> 13 files changed, 30 insertions(+), 41 deletions(-)
>>>>>
>>>>
>>>>
>>>
>>
>>
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2019-04-25 8:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 9:27 claudius.heine.ext
2019-04-24 9:27 ` [PATCH v3 1/8] isar-boostrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-25 11:25 ` Claudius Heine
2019-04-24 9:27 ` [PATCH v3 2/8] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-24 9:27 ` [PATCH v3 3/8] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-24 9:27 ` [PATCH v3 4/8] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-24 9:27 ` [PATCH v3 5/8] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-24 9:27 ` [PATCH v3 6/8] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-24 9:27 ` [PATCH v3 7/8] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-24 9:27 ` [PATCH v3 8/8] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext
2019-04-25 6:03 ` [PATCH v3 0/8] Cleanup rootfs creation Maxim Yu. Osipov
2019-04-25 6:40 ` Claudius Heine
2019-04-25 7:55 ` Maxim Yu. Osipov
2019-04-25 8:01 ` Claudius Heine
2019-04-25 8:07 ` Maxim Yu. Osipov [this message]
2019-04-25 8:27 ` Claudius Heine
2019-04-25 8:39 ` Maxim Yu. Osipov
2019-04-25 9:11 ` Claudius Heine
2019-04-25 9:33 ` Maxim Yu. Osipov
2019-04-25 9:51 ` Baurzhan Ismagulov
2019-04-25 10:32 ` Baurzhan Ismagulov
2019-04-25 11:18 ` Claudius Heine
2019-04-25 11:22 ` Claudius Heine
2019-04-25 8:52 ` Jan Kiszka
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=1aa42268-5f7e-355b-e980-eebe9df4a526@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--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