ACS Latest Code Sync Failed During Build

[smangali-qc]

HI @chetan-rathore ,

we are observing ACS Latest Code Sync Failed During Build ,below are the logs.

/local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto$ ./build-scripts/build-systemready-dt-band-live-image.sh
++ pwd

• TOP_DIR=/local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto
• pushd /local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto/meta-woden
  /local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto/meta-woden /local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto
• kas shell kas/woden.yml --command 'bitbake llvm-native && bitbake rust-native && bitbake glibc && bitbake glibc-locale && bitbake qemu-system-native && bitbake cargo-native && bitbake linux-yocto && bitbake woden-image'
  2026-01-20 16:18:26 - INFO - kas 4.4 started
  2026-01-20 16:18:26 - INFO - Using /local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto/meta-woden/kas as root for repository meta-woden
  2026-01-20 16:18:26 - WARNING - Using deprecated refspec for repository "poky". You should migrate to commit/tag/branch.
  2026-01-20 16:18:26 - WARNING - Using deprecated refspec for repository "meta-arm". You should migrate to commit/tag/branch.
  2026-01-20 16:18:26 - WARNING - Using deprecated refspec for repository "meta-openembedded". You should migrate to commit/tag/branch.
  2026-01-20 16:18:26 - WARNING - Using deprecated refspec for repository "meta-clang". You should migrate to commit/tag/branch.
  2026-01-20 16:18:26 - WARNING - Using deprecated refspec for repository "meta-secure-core". You should migrate to commit/tag/branch.
  2026-01-20 16:18:26 - INFO - Repository poky already contains scarthgap as commit
  2026-01-20 16:18:26 - INFO - Repository meta-arm already contains scarthgap as commit
  2026-01-20 16:18:26 - INFO - Repository meta-openembedded already contains scarthgap as commit
  2026-01-20 16:18:26 - INFO - Repository meta-clang already contains scarthgap as commit
  2026-01-20 16:18:26 - INFO - Repository meta-secure-core already contains scarthgap as commit
  2026-01-20 16:18:26 - WARNING - Repo poky is dirty - no checkout
  2026-01-20 16:18:26 - WARNING - Repo meta-arm is dirty - no checkout
  2026-01-20 16:18:26 - INFO - Repository meta-openembedded checked out to scarthgap
  2026-01-20 16:18:26 - INFO - Repository meta-clang checked out to scarthgap
  2026-01-20 16:18:26 - INFO - Repository meta-secure-core checked out to scarthgap
  2026-01-20 16:18:26 - INFO - To start the default build, run: bitbake -c build woden-image
  ERROR: Unable to parse /local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto/meta-woden/poky/bitbake/lib/bb/parse/init.py
  Traceback (most recent call last):
  File "/local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto/meta-woden/poky/bitbake/lib/bb/parse/init.py", line 145, in resolve_file
  raise IOError(errno.ENOENT, "file %s not found" % fn)
  FileNotFoundError: [Errno 2] file /local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto/meta-woden/build/../kas/conf/layer.conf not found

2026-01-20 16:18:27 - ERROR - Shell returned non-zero exit status
2026-01-20 16:18:27 - ERROR - Command "/bin/tcsh -c 'bitbake llvm-native && bitbake rust-native && bitbake glibc && bitbake glibc-locale && bitbake qemu-system-native && bitbake cargo-native && bitbake linux-yocto && bitbake woden-image'" failed with error 1

• '[' 1 -eq 0 ']'
• popd
  /local/mnt/workspace/acs_ethtool_delay/arm-systemready/SystemReady-devicetree-band/Yocto

regards,
shiva kumar

[chetan-rathore]

Hi @smangali-qc,

There were some build issues which we also found in our CI and were fixed.

fix: #612 today
fix: #606 last week

Can you share the arm-systemready commit id on top of which issue is seen, I would not expect the current latest code resulting in build failure.
877200e

[chetan-rathore]

FYI, we build latest DT at our side and there was no build failure. In case if build failure is still seen at your end, please share build machine details.

[smangali-qc]

HI @chetan-rathore ,

please find the machine details:

/local/mnt/workspace$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy
xyz@XYZ:/local/mnt/workspace$
uname -a
uname -m
Linux xyz 5.15.0-130-generic #140-Ubuntu SMP Wed Dec 18 17:59:53 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
x86_64
xyz@XYZ:/local/mnt/workspace$
xyz@XYZ:/local/mnt/workspace$ gcc --version
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

xyz@XYZ:/local/mnt/workspace$ python3 --version
Python 3.10.12

regards,
shiva kumar.

[chetan-rathore]

Hi @smangali-qc,

We have build on similar machine config recently, with same ubuntu, gcc and python version.
There is no failure observed at our end.

Are you observing build failures on other machines ? Also on current machine, were previous DT builds were success ?