At the end of cross-compilation, the build and install directory are chowned to the invoking user (build step is run as root in the container). However, if the build fails, this step isn't run
Expected Behavior
After the build is done, I can easily modify or remove build and install outputs.
Actual Behavior
If the build fails, the ownership of the files is not changed. This shows up as an error failing to remove the /tmp outputs in the run_e2e_test.sh script, if the build fails.
To Reproduce
Add a C++ syntax error to dummy_pkg_ros
Run run_e2e_test.sh
System (please complete the following information)
OS: Ubuntu Bionic
ROS 2 Distro: Dashing
Additional context
This should be solvable with an exit hook in the build_workspace.sh script
Description
At the end of cross-compilation, the
buildandinstalldirectory arechowned to the invoking user (build step is run as root in the container). However, if the build fails, this step isn't runExpected Behavior
After the build is done, I can easily modify or remove
buildandinstalloutputs.Actual Behavior
If the build fails, the ownership of the files is not changed. This shows up as an error failing to remove the /tmp outputs in the
run_e2e_test.shscript, if the build fails.To Reproduce
dummy_pkg_rosrun_e2e_test.shSystem (please complete the following information)
Additional context
This should be solvable with an exit hook in the
build_workspace.shscript