Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI incorrectly runs build tool tests on output of test tool #316

Closed
rotu opened this issue Jul 10, 2019 · 9 comments
Closed

CI incorrectly runs build tool tests on output of test tool #316

rotu opened this issue Jul 10, 2019 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@rotu
Copy link
Contributor

rotu commented Jul 10, 2019

When a test writes output that mimics build output, like "[ERROR] []: Original error msg: custom exception raised in configure callback" (as seen in ros2/rclcpp#777), it falsely flags it as a MSBuild error. The text output of colcon test-result should never cause a CI failure.

This might be a bug in the deprecated Warnings plugin currently in use or might be a misconfiguration of CI rules.

@rotu rotu changed the title Incorrect CI warning reported for test output CI incorrectly runs build tool tests on output of test tool Jul 10, 2019
rotu added a commit to RoverRobotics-forks/ci that referenced this issue Dec 13, 2019
rotu added a commit to RoverRobotics-forks/ci that referenced this issue Jan 2, 2020
rotu added a commit to RoverRobotics-forks/ci that referenced this issue Feb 18, 2020
@dirk-thomas
Copy link
Member

When a test writes output that mimics build output

Since the Jenkins plugin parses the output to find known patterns I don't see how we could avoid this. Do you have a specific idea how that could be achieved? If not, I am inclined to close this as wontfix since it is outside our hands.

@dirk-thomas dirk-thomas added the question Further information is requested label Feb 26, 2020
@rotu
Copy link
Contributor Author

rotu commented Feb 26, 2020

@dirk-thomas Yes, both Warnings and Warnings-NG plugins can (should) be configured to analyze a file other than consoleText. By default, colcon emits build and test output to log files already.

@dirk-thomas dirk-thomas added enhancement New feature or request and removed question Further information is requested labels Feb 26, 2020
rotu added a commit to RoverRobotics-forks/ci that referenced this issue Feb 28, 2020
@j-rivero
Copy link
Contributor

reopening as per #359 (comment)

@j-rivero j-rivero reopened this Mar 10, 2020
@hidmic
Copy link

hidmic commented Apr 16, 2020

@j-rivero @rotu considering #404 is in, can this issue be closed?

@j-rivero
Copy link
Contributor

@j-rivero @rotu considering #404 is in, can this issue be closed?

I don't think that this can be closed since #404 is not limiting the scope of the warnings in any way. To fix this issue we should inject the logs from colcon into the warnings-ng plugin instead of parsing all the output. We still have some false positives due to information coming from random test context (see http://build.ros.org/job/Mpr__gazebo_ros_pkgs__ubuntu_bionic_amd64/36/gcc/#issuesContent)

@dirk-thomas
Copy link
Member

@j-rivero the referenced Melodic job is not using colcon but catkin_make_isolated which doesn't capture any log files.

@j-rivero
Copy link
Contributor

@j-rivero the referenced Melodic job is not using colcon but catkin_make_isolated which doesn't capture any log files.

Right, sorry, the fix for the ROS1 buildfarm could be obvious. The example for the ROS2 buildfarm should be: http://build.ros2.org/job/Edev__gazebo_ros_pkgs__ubuntu_bionic_amd64/12/gcc/

@dirk-thomas
Copy link
Member

Addressed by #477 and ros-infrastructure/ros_buildfarm#812.

@rotu
Copy link
Contributor Author

rotu commented Jun 17, 2020

Awesome job, @dirk-thomas! Thanks for making the CI so much more usable!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants