cpp-ros2 tests & serialization tests always fail, because of using 'sudo'

[Jakio815]

I see that the cpp-ros2 tests & serialization tests always fail.
Both tests have this error code.
Error: The process '/usr/bin/sudo' failed with exit code 100

Is this a problem for everyone or only me?
This is the link.

and below is the error.

Run ros-tooling/setup-ros@v0.4
Invoking "sudo bash -c echo 'Etc/UTC' > /etc/timezone"
Invoking "sudo apt-get update"
Invoking "sudo DEBIAN_FRONTEND=noninteractive RTI_NC_LICENSE_ACCEPTED=yes apt-get install --no-install-recommends --quiet --yes curl gnupg2 locales lsb-release"
Invoking "sudo locale-gen en_US en_US.UTF-[8](https://github.com/lf-lang/lingua-franca/actions/runs/3514276074/jobs/5888154298#step:5:9)"
Invoking "sudo bash -c echo 'Etc/UTC' > /etc/timezone"
Invoking "sudo ln -sf /usr/share/zoneinfo/Etc/UTC /etc/localtime"
Invoking "sudo DEBIAN_FRONTEND=noninteractive RTI_NC_LICENSE_ACCEPTED=yes apt-get install --no-install-recommends --quiet --yes tzdata"
Invoking "sudo apt-key add /home/runner/work/lingua-franca/lingua-franca/ros.key"
Invoking "bash -c source /etc/lsb-release ; echo -n "$DISTRIB_CODENAME""
Invoking "sudo bash -c echo "deb http://packages.ros.org/ros2/ubuntu jammy main" > /etc/apt/sources.list.d/ros2-latest.list"
Invoking "sudo apt-get update"
Invoking "sudo apt-get upgrade -y"
Invoking "bash -c source /etc/lsb-release ; echo -n "$DISTRIB_CODENAME""
Invoking "sudo DEBIAN_FRONTEND=noninteractive RTI_NC_LICENSE_ACCEPTED=yes apt-get install --no-install-recommends --quiet --yes libssl-dev python3-dev build-essential clang cmake git lcov python3-catkin-pkg-modules python3-pip python3-vcstool wget libasio-dev libtinyxml2-dev python3-rosdep"
Invoking "sudo pip3 install --upgrade pip==20.*"
Invoking "sudo pip3 install --upgrade pip"
Invoking "sudo pip3 install --upgrade argcomplete colcon-bash==0.4.2 colcon-cd==0.1.1 colcon-cmake==0.2.26 colcon-common-extensions==0.2.1 colcon-core==0.6.1 colcon-coveragepy-result==0.0.8 colcon-defaults==0.2.5 colcon-lcov-result==0.5.0 colcon-library-path==0.2.1 colcon-metadata==0.2.5 colcon-mixin==0.2.0 colcon-notification==0.2.13 colcon-output==0.2.12 colcon-package-information==0.3.3 colcon-package-selection==0.2.[10](https://github.com/lf-lang/lingua-franca/actions/runs/3514276074/jobs/5888154298#step:5:12) colcon-parallel-executor==0.2.4 colcon-pkg-config==0.1.0 colcon-powershell==0.3.6 colcon-python-setup-py==0.2.7 colcon-recursive-crawl==0.2.1 colcon-ros==0.3.21 colcon-test-result==0.3.8 coverage cryptography empy flake8<3.8 flake8-blind-except flake8-builtins flake8-class-newline flake8-comprehensions flake8-deprecated flake8-docstrings flake8-import-order flake8-quotes ifcfg importlib-metadata==2.* importlib-resources lark-parser mock mypy nose numpy pep8 pydocstyle pyopenssl pyparsing pytest pytest-cov pytest-mock pytest-repeat pytest-rerunfailures pytest-runner setuptools<60.0 wheel"
Invoking "sudo bash -c rm /etc/ros/rosdep/sources.list.d/20-default.list || true"
Invoking "sudo rosdep init"
Invoking "sudo DEBIAN_FRONTEND=noninteractive RTI_NC_LICENSE_ACCEPTED=yes apt-get install --no-install-recommends --quiet --yes ros-galactic-desktop"
Error: The process '/usr/bin/sudo' failed with exit code 100

[lhstrh]

Looks like this was fixed in 036dbc3.

[cmnrd]

Just for the sake of documentation: The issue was not the use of sudo, but an error produced by the command run with sudo. The CI log makes a great job at masking the actual error... but one has to unfold the commands by clicking on the small triangle to see the full error.

[Jakio815]

Invoking "sudo DEBIAN_FRONTEND=noninteractive RTI_NC_LICENSE_ACCEPTED=yes apt-get install --no-install-recommends --quiet --yes ros-galactic-desktop"
  /usr/bin/sudo DEBIAN_FRONTEND=noninteractive RTI_NC_LICENSE_ACCEPTED=yes apt-get install --no-install-recommends --quiet --yes ros-galactic-desktop
  Reading package lists...
  Building dependency tree...
  Reading state information...
  E: Unable to locate package ros-galactic-desktop

I see that you're right. I'll check it more precisely next time. Thanks! @cmnrd

[cmnrd]

No worries, it wasn't a criticism ;) More a reminder (also for myself) for next time as this puzzled me for a while.