Bug description
aligator-test-py-mpc build in Debug on Ubuntu 22.04 fail because it reach the default ctest 1500s timeout.
This test usually run in 80s on other platform.
Expected behavior
Test should run in 80s.
Reproduction steps
Steps to reproduce the behavior:
mkdir build
cd build
cmake .. \
-GNinja \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DCMAKE_BUILD_TYPE=Debug \
-DBUILD_WITH_PINOCCHIO_SUPPORT=ON \
-DBUILD_CROCODDYL_COMPAT=OFF \
-DBUILD_WITH_OPENMP_SUPPORT=ON \
-DBUILD_BENCHMARKS=OFF \
-DBUILD_EXAMPLES=ON \
-DGENERATE_PYTHON_STUBS=ON \
-DALIGATOR_TRACY_ENABLE=OFF \
-DBUILD_WITH_UBUNTU_22_COMPATIBILITY=${{ matrix.ubuntu_22_compatibility }}
ninja
ctest -R ".*py-mpc.*" -V
Docker image
If this is an installation issue, a Docker image to reproduce it
FROM ubuntu:22.04
ARG DEBIAN_FRONTEND=noninteractive
RUN apt-get update
RUN apt-get install -y \
lsb-release \
gnupg2 \
cmake \
git \
python3
RUN sh -c "echo \"deb [arch=amd64] http://robotpkg.openrobots.org/packages/debian/pub $(lsb_release -cs) robotpkg\" >> /etc/apt/sources.list "
RUN apt-key adv --fetch-keys http://robotpkg.openrobots.org/packages/debian/robotpkg.key
RUN apt-get update
ARG PYTHON3_VERSION=310
RUN apt-get install -y \
doxygen \
ninja-build \
ccache \
libomp-dev \
libomp5 \
libboost-all-dev \
libeigen3-dev \
libfmt-dev \
libmimalloc-dev \
python3-pytest \
python3-matplotlib \
python3-numpy \
robotpkg-example-robot-data \
robotpkg-py$PYTHON3_VERSION-example-robot-data \
robotpkg-py$PYTHON3_VERSION-eigenpy \
robotpkg-py$PYTHON3_VERSION-pinocchio
RUN apt-get clean && \
rm -rf /var/lib/apt/lists/*
RUN echo "export PATH=$PATH:/opt/openrobots/bin" >> ~/.bashrc
RUN echo "export PYTHONPATH=$PYTHONPATH:/opt/openrobots/lib/python3.10/site-packages" >> ~/.bashrc
RUN echo "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/openrobots/lib" >> ~/.bashrc
RUN echo "export CMAKE_PREFIX_PATH=/opt/openrobots/lib" >> ~/.bashrc
System
- OS: Ubuntu 22.04
- aligator version: main
Bug description
aligator-test-py-mpc build in Debug on Ubuntu 22.04 fail because it reach the default ctest 1500s timeout.
This test usually run in 80s on other platform.
Expected behavior
Test should run in 80s.
Reproduction steps
Steps to reproduce the behavior:
Docker image
If this is an installation issue, a Docker image to reproduce it
System