public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] Add skeleton dir option
Date: Thu, 1 Aug 2019 09:02:48 +0200	[thread overview]
Message-ID: <2e001699-0cc9-d2b1-1682-eede6932731d@siemens.com> (raw)
In-Reply-To: <20190731124029.GZ14716@yssyq.m.ilbers.de>


> Reproducing is as easy as (untested):
> 
> . isar-init-build-env ../build
> bitbake -c cache_base_repo multiconfig:qemuarm-stretch:isar-image-base \
>      multiconfig:qemuarm64-stretch:isar-image-base \
>      multiconfig:qemuamd64-stretch:isar-image-base \
>      multiconfig:qemuarm-buster:isar-image-base
> echo 'ISAR_USE_CACHED_BASE_REPO = "1"' >>conf/local.conf
> sudo rm -rf tmp
> bitbake multiconfig:qemuarm-stretch:isar-image-base \
>      multiconfig:qemuarm64-stretch:isar-image-base \
>      multiconfig:qemuamd64-stretch:isar-image-base \
>      multiconfig:qemuarm-buster:isar-image-base
> 

I build it on my machine and the patch set applied to next worked. I 
don't think the /dev/pts error is from the patch set. It could be a 
follow up from this one:

OTE: Executing RunQueue Tasks
ERROR: mc:qemuarm64-stretch:isar-image-base-debian-stretch-qemuarm64 
do_rootfs_postprocess: Function failed: image_configure_accounts (log 
file is located at 
/home/ibr/w/work/j/isar/src/b-20190729-skel-applied/tmp/work/debian-stretch-arm64/isar-image-base-debian-stretch-qemuarm64/temp/log.do_rootfs_postprocess.25984) 
  ERROR: Logfile of failure stored in: 
/home/ibr/w/work/j/isar/src/b-20190729-skel-applied/tmp/work/debian-stretch-arm64/isar-image-base-debian-stretch-qemuarm64/temp/log.do_rootfs_postprocess.25984 


Can you sent log.do_rootfs_postprocess.25984 ?

Kind regards
Quirin



  parent reply	other threads:[~2019-08-01  7:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 12:36 Quirin Gylstorff
2019-07-19 12:38 ` [PATCH 1/3] image-account-extension: " Quirin Gylstorff
2019-07-19 12:38   ` [PATCH 2/3] meta-isar: Add example for user settings Quirin Gylstorff
2019-07-23  8:08     ` Henning Schild
2019-07-23 12:00       ` Quirin Gylstorff
2019-07-23 12:03         ` [PATCH 0/3] Add skeleton dir option Quirin Gylstorff
2019-07-23 12:06         ` Quirin Gylstorff
2019-07-23 12:06           ` [PATCH v2 1/3] image-account-extension: " Quirin Gylstorff
2019-07-23 12:06           ` [PATCH v2] ubifs-img: Correct function name Quirin Gylstorff
2019-07-23 12:06           ` [PATCH v2 2/3] meta-isar: Add example for user settings Quirin Gylstorff
2019-07-23 12:06           ` [PATCH v2 3/3] image-account-extension:Move configure_accounts to postprocess Quirin Gylstorff
2019-07-29 21:25           ` [PATCH 0/3] Add skeleton dir option Baurzhan Ismagulov
2019-07-31 11:44             ` Quirin Gylstorff
2019-07-31 12:40               ` Baurzhan Ismagulov
2019-07-31 14:49                 ` Henning Schild
2019-07-31 17:23                   ` Baurzhan Ismagulov
2019-08-01 16:10                   ` Baurzhan Ismagulov
2019-08-01  7:02                 ` Quirin Gylstorff [this message]
2019-08-01  9:50                   ` Baurzhan Ismagulov
2019-08-01 14:23                     ` Quirin Gylstorff
2019-07-19 12:38   ` [PATCH 3/3] image-account-extension:Move configure_accounts to postprocess Quirin Gylstorff

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=2e001699-0cc9-d2b1-1682-eede6932731d@siemens.com \
    --to=quirin.gylstorff@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