Pipeline fails (invoked due to demo tag creation)
Creating the demo tags for ARMAR-6 has triggered the build pipelines of all projects. In Robot API, it failed after an attempt to install apt packages:
❗ Error: Running 'apt-get install --no-install-recommends -y libalglib-dev
libarmadillo-dev libatlas-base-dev libblas-dev libbson-dev libgsl-dev
liblapack-dev libmongoc-dev libomp-dev libomp5 libqt5bluetooth5
libsuitesparse-dev qtconnectivity5-dev' failed with return code 100
(see https://git.h2t.iar.kit.edu/sw/armarx/robot-api/-/jobs/58530/raw)
However, two other runs of the pipeline that were based on the same commit/version passed:
- passed: https://git.h2t.iar.kit.edu/sw/armarx/robot-api/-/pipelines/17126
- passed: https://git.h2t.iar.kit.edu/sw/armarx/robot-api/-/pipelines/17181
- failed: https://git.h2t.iar.kit.edu/sw/armarx/robot-api/-/pipelines/17182 (reason as listed above).
Error 100 often seems to be related to docker files, see https://stackoverflow.com/questions/38002543/apt-get-update-returned-a-non-zero-code-100. For example, they mention clock issues, disk cleanup, RUN statements in a dockerfile or upgrading to a supported Ubuntu version.
@peller, @dreher, do you have an idea how this non-deterministic behavior of the pipeline can be explained and what is to be done?