You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/test_debugging/test_debugging_tutorial.rst
+12-18Lines changed: 12 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,33 +12,27 @@ If you haven't already done so, make sure you've completed the steps in `Getting
12
12
CI Failures
13
13
-----------
14
14
15
-
Our CI runs in Travis and uses scripts found in the `moveit_ci repo <https://github.com/ros-planning/moveit_ci.git>`. These tests build and run various tests in various environments. Often something that works locally won't work in CI in a different environment. To troubleshoot a failure from CI it is useful to use docker to run in the same environment.
15
+
Our CI runs on Github Actions and uses scripts found in `industrial_ci <https://github.com/ros-industrial/industrial_ci.git>`_. These tests build and run various tests in various environments. Often something that works locally won't work in CI in a different environment. To troubleshoot a failure from CI it is useful to use docker to run in the same environment.
16
16
17
-
For troubleshooting a specific travis test it is helpful to look at the .travis.yml config file and test output to understand what environment variables are being set in your test.
17
+
For troubleshooting a specific test it is helpful to inspect the GHA logs to understand what environment variables are being set in your test.
18
18
19
19
Launch Docker Environment
20
20
-------------------------
21
21
22
-
To start docker container for kinetic:
22
+
To start docker container::
23
23
24
-
docker pull moveit/moveit:kinetic-ci
25
-
docker run -it moveit/moveit:kinetic-ci /bin/bash
26
-
27
-
To start docker container for melodic:
28
-
29
-
docker pull moveit/moveit:melodic-ci
30
-
docker run -it moveit/moveit:melodic-ci /bin/bash
24
+
docker run -it moveit/moveit:noetic-ci /bin/bash
31
25
32
26
Setup Environment
33
27
-----------------
34
28
35
-
The first thing you should do is update debians and install tools you'll need for debugging. The update is important because that is what we do in CI.
29
+
The first thing you should do is update debians and install tools you'll need for debugging. The update is important because that is what we do in CI::
36
30
37
31
apt-get update
38
32
apt-get dist-upgrade
39
33
apt-get install -y python-catkin-tools ssh git gdb valgrind vim
40
34
41
-
Next create the folder structure for your ROS environment:
35
+
Next create the folder structure for your ROS environment::
42
36
43
37
CATKIN_WS=/root/ros_ws
44
38
mkdir -p ${CATKIN_WS}/src
@@ -47,7 +41,7 @@ Next create the folder structure for your ROS environment:
47
41
Checkout Code
48
42
-------------
49
43
50
-
In this step we use git and wstool to get the code we will be testing. You'll replace the remote and branch with yours if you are debugging a PR. Note that on the wstool update step we'll need to skip replacing moveit if we are testing a specific branch from a PR.
44
+
In this step we use git and wstool to get the code we will be testing. You'll replace the remote and branch with yours if you are debugging a PR. Note that on the wstool update step we'll need to skip replacing moveit if we are testing a specific branch from a PR::
51
45
52
46
cd ${CATKIN_WS}/src
53
47
wstool init .
@@ -58,15 +52,15 @@ In this step we use git and wstool to get the code we will be testing. You'll r
You can also use rostest to run a specific test. The text argument sends output to the console instead of an xml output file. To do this you'll have to source the devel workspace.
88
+
You can also use rostest to run a specific test. The text argument sends output to the console instead of an xml output file. To do this you'll have to source the devel workspace::
0 commit comments