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.

>  
> --
> 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.