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 v5 0/5] UBI support
Date: Wed, 13 Feb 2019 09:36:11 +0100 [thread overview]
Message-ID: <66b91f1f-3378-1295-2f17-287118aebd64@ilbers.de> (raw)
In-Reply-To: <dc2a1e68-6ddc-95d3-33ab-dde5a05746ae@siemens.com>
Hi Claudius,
You can easily access the build directory with all build artifacts of
the last build (the build artifacts of previous builds are wiped out
except logs): Just go to
http://isar-build.org:8080/job/isar_mosipov_next/ws/build.
FYI: The last (#141) build (with your patches (Click on Changes)) failed:
See:
http://isar-build.org:8080/job/isar_mosipov_next/141/console
The previous (#140) (actually is the same as 'next') is OK:
http://isar-build.org:8080/job/isar_mosipov_next/140/console
Just to doublecheck: have you tried on your local PC
'./scripts/ci_build.sh -q'?
Regards,
Maxim.
On 2/12/19 5:36 PM, Claudius Heine wrote:
> On 12/02/2019 16.51, [ext] Claudius Heine wrote:
>> Hi Maxim,
>>
>> On 12/02/2019 15.06, Maxim Yu. Osipov wrote:
>>> Hi again, Claudius,
>>>
>>> I've applied "[PATCH v2 1/1] meta: added do_transform_template task
>>> as templating system and switch" before UBI support v5 series
>>> and CI failed:
>>>
>>> See for details
>>>
>>> http://isar-build.org:8080/job/isar_mosipov_next/139/console
>>
>> I only see errors that complain about code that is not affected by the
>> template and ubi patchset. It complains about the
>> 'buildchroot-target', which does not use the ubi classes or the
>> template functions.
>>
>> I will investigate further, but currently I don't think that the bug
>> is in those patchesets that lead to this issue. Currently I cannot
>> reproduce this issue on my host.
>
> I tried reproducing it on the siemens internal ci server without
> success. So if that issue persists on your CI then I would need access
> to that server to debug that issue or maybe the dump of the bitbake
> environment for the buildchroot-target task + the state of the tmp
> directory.
>
> Regards,
> Claudius
>
--
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-02-13 8:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 9:09 claudius.heine.ext
2019-02-11 9:09 ` [PATCH v5 1/5] meta/image.bbclass: add image_do_mounts for image specific mounts claudius.heine.ext
2019-02-11 10:49 ` chombourger
2019-02-11 11:33 ` Claudius Heine
2019-02-11 9:09 ` [PATCH v5 2/5] meta/classes: added ubifs-img class claudius.heine.ext
2019-02-11 9:09 ` [PATCH v5 3/5] meta/classes: added ubi-img class claudius.heine.ext
2019-02-11 9:09 ` [PATCH v5 4/5] meta/classes: added fit-img class for creation of fit images claudius.heine.ext
2019-02-11 9:09 ` [PATCH v5 5/5] meta-isar: added nand-ubi-demo example to demonstrate UBI use claudius.heine.ext
2019-02-11 9:45 ` [PATCH v5 0/5] UBI support Henning Schild
2019-02-12 11:24 ` Maxim Yu. Osipov
2019-02-12 13:16 ` Claudius Heine
2019-02-12 13:35 ` Claudius Heine
2019-02-12 13:36 ` Maxim Yu. Osipov
2019-02-12 14:06 ` Maxim Yu. Osipov
2019-02-12 14:09 ` Claudius Heine
2019-02-12 14:36 ` Baurzhan Ismagulov
2019-02-12 14:56 ` Claudius Heine
2019-02-12 15:51 ` Claudius Heine
2019-02-12 16:36 ` Claudius Heine
2019-02-13 8:36 ` Maxim Yu. Osipov [this message]
2019-02-13 9:53 ` Claudius Heine
2019-02-15 14:47 ` 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=66b91f1f-3378-1295-2f17-287118aebd64@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