Chris Timperley

We should enforce this rule as part of our CI to avoid cases such as this: https://github.com/robust-rosin/robust/blob/master/motoman/91072e8/91072e8.bug

Fix "bug.subsystem" property in bug reports

2

In RQ2.2 for the paper, we report the subsystems affected by the failure for each bug. That information is currently captured by the bug.subsystem property in the bug reports. We...

Some of the `geometry2` bug descriptions are named `description.bug` (e.g., `geometry2/42267be/description.bug`). We should change `description.bug` to be `42267be.bug` to match the rest of the repository.

Build separate Docker image for buggy and fixed versions (fixes #263 and fixes #159)

1

**Warning:** Do not merge before merging #264. ## Approach * uses a multi-stage build to construct a separate image for the buggy and fixed versions in a single pass.

Added image for mavros e05c71a

2

Status: ``` Step 41/43 : RUN echo "[ROBUST] attempting to build PUT..." && echo "[ROBUST] is a build failure expected? ${IS_BUILD_FAILURE}." && ./build.sh || [ "${IS_BUILD_FAILURE}" = "yes" ] --->...

Added image for mavros 400949c

4

Fails to download source for PUT: ``` ---> d37c86810e22 Step 31/43 : RUN wstool init -j8 ${ROS_WSPACE}/src ${ROS_WSPACE}/deps.rosinstall ---> Running in efd1835eb091 Using initial elements from: /ros_ws/deps.rosinstall Writing /ros_ws/src/.rosinstall [angles]...

Inspired by ROS, perhaps?