-
Notifications
You must be signed in to change notification settings - Fork 2
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
Buildfarmer log 2024/05/20 - 2024/05/27 #53
Comments
May 20Build regressions
Test regressions
|
🔴 ci.ros2.org build regressions (May 20th)Out of space left on agent
|
Nightly_win_deb sros2 failure investigation 🕵️♀️First failure: https://ci.ros2.org/view/nightly/job/nightly_win_deb/3095/ Error
Possible cause: ros2/sros2@fb22661 |
Coverage nightly for Jazzy and Rolling build regression 🕵️♀️Affected builds Seems like an issue when porting the coverage reports to the jenkins controller.
|
The issues logged have been present for years, quite likely, based on recent reports. Although those errors affect the visualization of the source files in coverage reports, they don't actually break the build. Th last time this was being investigated, the exit status of colcon-test was non-zero and that was the "actual" hard failure. |
Yeah, we need to land ros2/ci#771, which will switch this from a red build to a yellow one. |
Thanks, we will wait for that to land then. Sorry for the noise, it's been a while since I've done buildfarm work 😆 |
May 21Build regressions
Test regressions
|
🔴 Build regressions (May 21st)ROSOut of space left on agent
|
🟡 Test regression
|
@claraberendsen I've prepared a fix for the aforementioned CI regression. |
May 22Build regressions
Test regressions
|
Doc rosindex | Build regression | Keeping track 👀Reference build: https://build.ros.org/job/doc_rosindex/2003/console (started failing again since build 1998) Log output:
It's being solved in: ros-infrastructure/ros_buildfarm#1047 |
Ros2 nightlies
|
job_name | last_fail | first_fail | build_count | failure_count | failure_percentage |
---|---|---|---|---|---|
nightly_linux_debug | 2024-05-22 | 2024-05-09 | 15 | 7 | 46.67 |
nightly_linux_repeated | 2024-05-19 | 2024-05-08 | 16 | 2 | 12.5 |
nightly_win_deb | 2024-05-15 | 2024-05-07 | 9 | 5 | 55.56 |
Flakiness report (projectroot.test_tutorial_parameter_events__rmw_connextdds):
job_name | last_fail | first_fail | build_count | failure_count | failure_percentage |
---|---|---|---|---|---|
nightly_win_rep | 2024-05-22 | 2024-05-07 | 13 | 13 | 100.0 |
nightly_win_rel | 2024-05-22 | 2024-05-22 | 14 | 1 | 7.14 |
nightly_linux-rhel_repeated | 2024-05-21 | 2024-05-12 | 16 | 3 | 18.75 |
nightly_win_deb | 2024-05-12 | 2024-05-09 | 9 | 2 | 22.22 |
I don't see any specific change that points to a reason why it started failing more in normal jobs, and not only repeated ones (package history).
projectroot.test_tutorial_parameter_events_async__rmw_connextdds
- In linux debug started happening since March 31 build 3012
- In linux repeated started happening since April 23 build 3433
- In windows debug started happening since March 29 build 3047
projectroot.test_tutorial_parameter_events__rmw_connextdds:
- In windows repeated this tests started happening since parallel testing (reference build) in Feb 25 and has been happening almost consistently since.
- In windows release happened today only
- In windows debug started happening since Feb 29 build 3018 (just after parallel testing)
- In rhel repeated it started happening since March 8 build 1859
May 23Build regressions
Test regressions
|
Ros linux nightlies | Build regression | Keeping track 👀Some linux nightlies failed due to a "No Space Left" error in linux-2xlarge-f8f1b088 machine:
I'm cleaning up the space in the agent |
May 24Build regressions
Test regressions
|
Jazzy Release | Warnings | Investigating 🕵️Reference build:https://build.ros2.org/view/Jci/job/Jci__nightly-release_ubuntu_noble_amd64/15/ Warnings
@clalancette these warnings are in different packages. Where should I report this? |
May 25Build regressions
Test regressions
|
May 26Build regressions
Test regressions
|
Previous log #51
The text was updated successfully, but these errors were encountered: