From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6680483261914808320 X-Received: by 2002:a5d:5282:: with SMTP id c2mr14401296wrv.88.1556180840202; Thu, 25 Apr 2019 01:27:20 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:2292:: with SMTP id 18ls2649765wmf.3.canary-gmail; Thu, 25 Apr 2019 01:27:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqzQvEyyPKx1v52ReY0v0Drhu79kVVpNTG1ugXuRotBSoTRlV5gfEpE4dlibi+rHm/if1rCr X-Received: by 2002:a7b:cc96:: with SMTP id p22mr2623709wma.17.1556180839719; Thu, 25 Apr 2019 01:27:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556180839; cv=none; d=google.com; s=arc-20160816; b=woCdLWmnChp+Ra7uo/LTUkqkbttWbxD+N8yW7Fjinnv94IVR8yAARV8O0niel82CHo kPapualaQapdC0CIhwYki5+1GCHVA2TFagOUlkfLiXlWkRoF/+WNXs9OLjTbbPTUSDj2 JY2ZeZsieav2NhkNA2xf5b/9nuThz2uWAVjm/CspPgRUHdR7374OVSK40StwUzpm0LIU WQ1M3w+zDb0tkXBbJCUaQFK7PAbr23oER6gRFNoOuDGvqrUGYQQPiq2KYmo8yw3I8wYZ jV7BKUTu6CM/Mp3kdv122DJgMjR1jyq1zT5YzQbBza5JuqV+s4WE6ToAoSUlunbofoLm O8ug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=YZ9MJdTkEjp4GBA39hvFV7so6kq6dn2AgXrMDJi8szI=; b=w69I49s2jKNY8JOtSzHfGFdB3cSMyI0U7G3vnnZa21XpPTuTS5qFYofYQJSNLlIWfJ 7lQE+Znc2CRW3gEzuyrka0gkMKDM1VdakvVBAWOJliQLe3zrcy0flFmRtwbsUu+j8OI9 PIGK6o+KMOk9Y2XFvCsiu2J2aowDO5cIlmpIY8iwJQPGlVyu20Kq1mEaw5UWujGLM2nC I/4ldfYlYuCv3f2bsXNlMzTOGUM5i0XKkYlJk050U69sj1PzEggtMEY93Owvx67m1t7L vJ4O0BIji2iE7l2cE9ND4MnOKR0sxKOGQJrgGi8I53U/aVR5Zq6pLkgXJnVCBqAu/efy GRQw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id y130si170422wmd.2.2019.04.25.01.27.19 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Apr 2019 01:27:19 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x3P8RH8A028523 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 25 Apr 2019 10:27:17 +0200 Received: from [139.25.69.232] (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x3P8RH3i009136; Thu, 25 Apr 2019 10:27:17 +0200 Subject: Re: [PATCH v3 0/8] Cleanup rootfs creation To: "Maxim Yu. Osipov" , isar-users@googlegroups.com Cc: Claudius Heine References: <20190424092734.14167-1-claudius.heine.ext@siemens.com> <33359f72-d7d0-0d41-051d-da9885bd7354@ilbers.de> <0523bc46-f96e-d4d0-1828-fc99079c938b@siemens.com> <561243bd-3aa7-5f8a-83c5-4137660354fb@siemens.com> <1aa42268-5f7e-355b-e980-eebe9df4a526@ilbers.de> From: Claudius Heine Message-ID: Date: Thu, 25 Apr 2019 10:27:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <1aa42268-5f7e-355b-e980-eebe9df4a526@ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: vBrIwD3jgB6L On 25/04/2019 10.07, Maxim Yu. Osipov wrote: > 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. Well I did build the multiconfig+target where the issue occured IIRC. > >>> >>>> 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? I don't care. I would like to have my CI configured in a way that allows my patches to tested for upstream inclusion. If that is in a "fast", "slow" or "totally unnoteworthy" velocity does not matter for that. CI is an acceptability test and I want the strictest one. If I was mistaken that "fast" is less strict than "slow", then switch to "fast". If I now need to pass "fast" and "slow" for my patch to be acceptable, then I would suggest introducing a "abysmal slow" CI run that combines "slow" and "fast". Claudius > > Maxim. > >> Claudius >> >>> >>> Maxim. >>> >>>> Claudius >>>> >>>>> >>>>> Maxim. >>>>> >>>>> On 4/24/19 11:27 AM, claudius.heine.ext@siemens.com wrote: >>>>>> From: Claudius Heine >>>>>> >>>>>> 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(-) >>>>>> >>>>> >>>>> >>>> >>> >>> >> > > -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de