public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Builds are breaking in the sbuildchroot stage
Date: Fri, 7 Feb 2025 05:59:55 -0800 (PST)	[thread overview]
Message-ID: <f621f160-52b2-4d99-abc2-56de7b5ca36dn@googlegroups.com> (raw)
In-Reply-To: <2cc82e79c062d7b0a05a5e520fef4a060fc45d6a.camel@ilbers.de>


[-- Attachment #1.1: Type: text/plain, Size: 3907 bytes --]



On Thursday, February 6, 2025 at 2:49:42 PM UTC+5:30 Uladzimir Bely wrote:

On Wed, 2025-02-05 at 22:12 -0800, Srinuvasan Arjunan wrote: 
> Hello everyone, 
> 
>                In the latest ISAR next branch we observed the build 
> failure happening consistently with the following steps. 
> 
> 1. git clone http://github.com/ilbers/isar.git 
> 2. cd isar; git checkout next 
> 3.. isar-init-build-env ../build 
> 4. bitbake  mc:qemuarm-bookworm:isar-image-base 
> 
> Now we can able to see the below failures: 
> 
> Logs: 
> 
> NOTE: Executing Tasks 
> ERROR: mc:qemuarm-bookworm:sbuild-chroot-host-1.0-r0 
> do_rootfs_postprocess: 
> ExecutionError('/home/mahanadi/srinu_workspace/ISAR_UMOUNT_ISSUE_ANAL 
> YSIS/build/tmp/work/debian-bookworm-armhf/sbuild-chroot-host/1.0- 
> r0/temp/run.rootfs_do_umounts.143629', 32, None, None) 
> ERROR: Logfile of failure stored in: 
> /home/mahanadi/srinu_workspace/ISAR_UMOUNT_ISSUE_ANALYSIS/build/tmp/w 
> ork/debian-bookworm-armhf/sbuild-chroot-host/1.0- 
> r0/temp/log.do_rootfs_postprocess.143629 
> Log data follows: 
> | DEBUG: Executing python function do_rootfs_postprocess 
> | DEBUG: Executing shell function rootfs_do_mounts 
> | DEBUG: Shell function rootfs_do_mounts finished 
> | DEBUG: Executing shell function rootfs_do_qemu 
> | DEBUG: Shell function rootfs_do_qemu finished 
> | DEBUG: Executing shell function 
> rootfs_postprocess_clean_ldconfig_cache 
> | DEBUG: Shell function rootfs_postprocess_clean_ldconfig_cache 
> finished 
> | DEBUG: Executing shell function rootfs_postprocess_clean_tmp 
> | DEBUG: Shell function rootfs_postprocess_clean_tmp finished 
> | DEBUG: Executing shell function rootfs_do_umounts 
> | umount: 
> /home/mahanadi/srinu_workspace/ISAR_UMOUNT_ISSUE_ANALYSIS/build/tmp/w 
> ork/debian-bookworm-armhf/sbuild-chroot-host/1.0-r0/rootfs/dev/pts: 
> target is busy. 
> | WARNING: exit code 32 from a shell command. 
> | DEBUG: Python function do_rootfs_postprocess finished 
> ERROR: Task (mc:qemuarm- 
> bookworm:/home/mahanadi/srinu_workspace/ISAR_UMOUNT_ISSUE_ANALYSIS/is 
> ar/meta/recipes-devtools/sbuild-chroot/sbuild-chroot- 
> host.bb:do_rootfs_postprocess) failed with exit code '1' 
> 
> 
> Does anyone faces this kind of issue? 
> 
> Note: same machine building fine with kas-container 
> 
> Any help would be greatly appreciated  
> 
> Many thanks, 
> Srinu 
> 

Hello. 

I've tried exactly same steps in two scenarois: 
- being inside docker bookworm container 
- being inside freshly debootstrapped bookworm chroot (with /dev, 
/proc, /sys mounted, of course). 

Builds in them both didn't fail. 

I didn't try it directly on host since is not Debian-like system. 

As for me, the issue looks like something local related.


  Hi Uladzimir Bely,

  Thanks for the quick test.

  Here we observed this issue in the debian host machine, we directly ran 
the build in the host machine not the prepared bootstrap/container.
  Today we tried other debian host machine also, observed the same failures.

Many thanks,
Srinu



>   
> -- 
> You received this message because you are subscribed to the Google 
> Groups "isar-users" group. 
> To unsubscribe from this group and stop receiving emails from it, 
> send an email to isar-users+...@googlegroups.com. 
> To view this discussion visit 
> 
https://groups.google.com/d/msgid/isar-users/4d6486d5-0622-46d0-b207-37d281e56071n%40googlegroups.com 
> . 

-- 
Best regards, 
Uladzimir. 



-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/f621f160-52b2-4d99-abc2-56de7b5ca36dn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5635 bytes --]

      reply	other threads:[~2025-02-07 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  6:12 Srinuvasan Arjunan
2025-02-06  9:19 ` Uladzimir Bely
2025-02-07 13:59   ` Srinuvasan Arjunan [this message]

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=f621f160-52b2-4d99-abc2-56de7b5ca36dn@googlegroups.com \
    --to=srinuvasanasv@gmail.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