Build failed in Jenkins: packaging_windows #1834

0 views
Skip to first unread message

ROS 2 Buildfarm

unread,
Aug 7, 2020, 5:47:51 PM8/7/20
to ros2-bu...@googlegroups.com
See <https://ci.ros2.org/job/packaging_windows/1834/display/redirect>

Changes:


------------------------------------------
[...truncated 117.86 KB...]
git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at eac81b2 1.1.2
=== src\ros2/sros2 (git) ===
Cloning into '.'...
Note: switching to '0.9.2'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 8263f68 0.9.2
=== src\ros2/system_tests (git) ===
Cloning into '.'...
Note: switching to '0.9.1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 3080805 0.9.1
=== src\ros2/test_interface_files (git) ===
Cloning into '.'...
Note: switching to '0.8.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at c4d710e 0.8.0
=== src\ros2/tinyxml2_vendor (git) ===
Cloning into '.'...
Note: switching to '0.7.3'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at df8745e 0.7.3
=== src\ros2/tinyxml_vendor (git) ===
Cloning into '.'...
Note: switching to '0.8.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at b7a50bf 0.8.0
=== src\ros2/tlsf (git) ===
Cloning into '.'...
Note: switching to '0.5.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 1c4a13c 0.5.0
=== src\ros2/unique_identifier_msgs (git) ===
Cloning into '.'...
Note: switching to '2.1.2'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at c0a899e 2.1.2
=== src\ros2/urdf (git) ===
Cloning into '.'...
Note: switching to '2.4.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 533de85 2.4.0
=== src\ros2/urdfdom (git) ===
Cloning into '.'...
Note: switching to '2.3.2'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 694a6fe 2.3.2
=== src\ros2/yaml_cpp_vendor (git) ===
Cloning into '.'...
Note: switching to '7.0.2'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 0c249d5 7.0.2
[31m [1m<== [0m 'vcs import "src" --force --retry 5 --input 00-ros2.repos' exited with return code '1' [0m
Build step 'Execute Windows batch command' marked build as failure
[CMakeMSBuild] Skipping execution of recorder since overall result is 'FAILURE'
[Cobertura] Publishing Cobertura coverage report...

INFO: Starting to record.
INFO: Processing CTest-Version 3.x (default)
INFO: [CTest-Version 3.x (default)] - No test report file(s) were found with the pattern 'ws/build/*/Testing/*/Test.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'CTest-Version 3.x (default)'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'CTest-Version 3.x (default)'?"
INFO: Processing GoogleTest-1.8
INFO: [GoogleTest-1.8] - No test report file(s) were found with the pattern 'ws/build/*/test_results/**/*.gtest.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'GoogleTest-1.8'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'GoogleTest-1.8'?"
INFO: Processing JUnit
INFO: [JUnit] - No test report file(s) were found with the pattern 'ws/build/*/pytest.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'JUnit'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'JUnit'?"
INFO: Processing JUnit
INFO: [JUnit] - No test report file(s) were found with the pattern 'ws/build/*/test_results/**/*.xunit.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'JUnit'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'JUnit'?"
INFO: Processing CTest-Version 3.x (default)
INFO: [CTest-Version 3.x (default)] - No test report file(s) were found with the pattern 'work space/build space/*/Testing/*/Test.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'CTest-Version 3.x (default)'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'CTest-Version 3.x (default)'?"
INFO: Processing GoogleTest-1.8
INFO: [GoogleTest-1.8] - No test report file(s) were found with the pattern 'work space/build space/*/test_results/**/*.gtest.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'GoogleTest-1.8'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'GoogleTest-1.8'?"
INFO: Processing JUnit
INFO: [JUnit] - No test report file(s) were found with the pattern 'work space/build space/*/pytest.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'JUnit'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'JUnit'?"
INFO: Processing JUnit
INFO: [JUnit] - No test report file(s) were found with the pattern 'work space/build space/*/test_results/**/*.xunit.xml' relative to '<https://ci.ros2.org/job/packaging_windows/ws/'> for the testing framework 'JUnit'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'JUnit'?"
INFO: Skipping tests recording.
Skipped archiving because build is not successful

ROS 2 Buildfarm

unread,
Aug 7, 2020, 7:14:22 PM8/7/20
to ros2-bu...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages