2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 <2024> 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 <2024> 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | CI-Scripts and RTEMS Cached files on GHA |
From: | "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov> |
To: | EPICS core-talk <core-talk at aps.anl.gov> |
Date: | Thu, 28 Mar 2024 22:24:44 +0000 |
Earlier today I had to clear the cached copies of the dependencies for the 3 RTEMS builds of pvAccessCPP. Looking at
this run, despite apparently successfully restoring the cached copies: Received 174353040 of 174353040 (100.0%), 169.5 MBs/sec
17Cache
Size: ~166 MB (174353040 B) 18/usr/bin/tar
-z -xf /home/runner/work/_temp/0a59dd1a-0e60-48ac-aa81-7b50d65052c4/cache.tgz -P -C /home/runner/work/pvAccessCPP/pvAccessCPP
19Cache
restored successfully 20Cache
restored from key: 7.0/ubuntu-20.04/gcc/default/5/RTEMS-pc686-qemu/ the
main builds were failing with this error: make[2]: Leaving directory '/home/runner/work/pvAccessCPP/pvAccessCPP/configure/O.linux-x86_64'
45
perl -CSD /home/runner/.cache/base-7.0/bin/linux-x86_64/convertRelease.pl checkRelease
46
make -C O.RTEMS-pc686-qemu -f ../Makefile TOP=../.. \ 47
T_A=RTEMS-pc686-qemu install 48
/home/runner/.cache/base-7.0/configure/os/CONFIG.Common.RTEMS:37: /opt/rtems/5/i386-rtems5/pc686/Makefile.inc: No such file or directory
49
make[2]: *** No rule to make target '/opt/rtems/5/i386-rtems5/pc686/Makefile.inc'. Stop.
50
make[1]: *** [/home/runner/.cache/base-7.0/configure/RULES_ARCHS:58: install.RTEMS-pc686-qemu] Error 2
51
make: *** [/home/runner/.cache/base-7.0/configure/RULES_DIRS:85: configure.install] Error 2
52
Error: Process completed with exit code 2. I am also seeing these "Annotations" about the run from GHA which I suspect may be related:
On deleting the cached data the dependencies are rebuilt and the main build succeeds (see run #70), but it fails again on subsequent builds (#71). I just cleared the caches again and re-ran the failed builds which I hope will succeed. Can anyone explain what needs to be done to fix this properly? Thanks, - Andrew -- Complexity comes for free, Simplicity you have to work for. |