Analysis of Robot reports from OSM Jenkins¶

Date and time of the report: 2026-02-22 08:45:16.712361

Analysed period: 2026-02-01 to 2026-02-22.

1. Retrieval of all currrent data for aggregate analytics¶

Database update:

Retrieving new jobs...
Getting new builds from: osm-stage_3-merge/master, osm-stage_3-merge/v19.0, osm-stage_3-merge/v18.0, osm-stage_3-merge/v17.0, osm-stage_3-merge/v16.0, osm-stage_3-merge/v14.0
DONE
Retrieving from database...	
DONE

2. Aggregated analysis of stability¶

2.1 Restricts data to time window for analysis¶

2.2 Finding sequences of successful builds and Robot reports¶

Two values retrieved from the build are key to determine the state of the jubs and test suites at a given moment:

  • build_result is the outcome of the build, reported by Jenkins. It can be: SUCCESS, FAILURE, UNSTABLE or ABORTED.
  • test_result is the summary of the concerned Robot tests. It can be: FAIL, UNAVAILABLE or PASS.

Based on these two states, 3 types of temporal sequences of success/failure are identified per builds and test suites:

  1. Successful builds/failed builds in a row: grp_build_result.
  2. Successful test reports vs. test reports with fails in a row: grp_test_result.
  3. Clean builds and tests vs. failures (of any kind) in a row: grp_success_fail.

For the identification of these sequences, the following mapping applies:

Type of sequence Relevant state OK sequence contains NOK sequence contains Ignore
grp_build_result build_result SUCCESS or UNSTABLE FAILURE ABORTED
grp_test_result test_result PASS FAIL UNAVAILABLE
grp_success_fail test_result PASS FAIL or UNAVAILABLE N/A

The different groupings of segments are detected and a label is added to each sample...

DONE

Then, the duration of each of the sequences of success/failure is determined and a specific dataframe is built summarizing such sequences, to ease their representation and analysis...

DONE

2.3 Finding sequences of pass/fails per test suite¶

DONE

3. Reports¶

3.1 Aggregated success rate per test step¶

No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image

3.2 Overall success of Jenkins builds and Robot tests¶

No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image

3.3 Sequences of pass/fails per test suites¶

No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
Empty dataframe. Skipping.

3.4 Failing days per test suite¶

No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
No description has been provided for this image
Out[58]:
job Master branch Release EIGHTEEN Release FOURTEEN ... Release NINETEEN Release SEVENTEEN Release SIXTEEN
days_failing days_passing days_run error_rate days_failing days_passing days_run error_rate days_failing days_passing ... days_run error_rate days_failing days_passing days_run error_rate days_failing days_passing days_run error_rate
suites
Basic 01-Crud Operations On Vim Targets 0.000000 21.362017 21.362017 0.0 0.00000 16.44123 16.44123 0.0 0.0 0.0 ... 21.01366 0.0 0.000000 15.623892 15.623892 0.0 0.000000 14.254436 14.254436 0.000000
Basic 05-Instantiation Parameters In Cloud Init 0.000000 21.362017 21.362017 0.0 0.00000 16.44123 16.44123 0.0 0.0 0.0 ... 19.77520 0.0 0.000000 15.623892 15.623892 0.0 0.000000 14.254436 14.254436 0.000000
Basic 06-Vnf With Charm 0.000000 0.000000 0.000000 0.0 0.00000 0.00000 0.00000 0.0 0.0 0.0 ... 0.00000 0.0 0.000000 0.000000 0.000000 0.0 0.000000 0.000000 0.000000 0.000000
Basic 07-Secure Key Management 0.000000 0.000000 0.000000 0.0 0.00000 0.00000 0.00000 0.0 0.0 0.0 ... 0.00000 0.0 0.000000 0.000000 0.000000 0.0 0.000000 0.000000 0.000000 0.000000
Basic 08-Disable Port Security Network Level 0.000000 21.362017 21.362017 0.0 0.00000 16.44123 16.44123 0.0 0.0 0.0 ... 19.77520 0.0 0.000000 15.623892 15.623892 0.0 0.000000 14.254436 14.254436 0.000000
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Sa 08-Vnf With Vnf Indicators Snmp 21.362017 0.000000 21.362017 1.0 16.44123 0.00000 16.44123 1.0 0.0 0.0 ... 19.77520 1.0 15.623892 0.000000 15.623892 1.0 14.254436 0.000000 14.254436 1.000000
Slice 01-Network Slicing 0.000000 21.362017 21.362017 0.0 0.00000 16.44123 16.44123 0.0 0.0 0.0 ... 19.77520 0.0 0.000000 15.623892 15.623892 0.0 0.000000 14.254436 14.254436 0.000000
Slice 02-Shared Network Slicing 0.000000 21.362017 21.362017 0.0 0.00000 16.44123 16.44123 0.0 0.0 0.0 ... 19.77520 0.0 0.000000 15.623892 15.623892 0.0 1.000035 13.254401 14.254436 0.070156
Sol003 01-Vnf-Lifecycle-Management 0.000000 21.362017 21.362017 0.0 0.00000 16.44123 16.44123 0.0 0.0 0.0 ... 19.77520 0.0 0.000000 15.623892 15.623892 0.0 0.000000 14.254436 14.254436 0.000000
Sol003 02-Dualstack Ip Vnfm 0.000000 21.362017 21.362017 0.0 0.00000 16.44123 16.44123 0.0 0.0 0.0 ... 19.77520 0.0 0.000000 15.623892 15.623892 0.0 0.000000 14.254436 14.254436 0.000000

62 rows × 24 columns

4. Information about the latest builds of relevant jobs¶

Latest build of each job¶

auto_id job build timestamp duration build_result test_result pass_count fail_count
0 9243 osm-stage_3-merge/master 3661 2026-02-22 00:06:11 44912 FAILURE UNAVAILABLE NaN NaN
1 9244 osm-stage_3-merge/v19.0 23 2026-02-21 14:11:07 118333 FAILURE UNAVAILABLE NaN NaN
2 9245 osm-stage_3-merge/v18.0 189 2026-02-21 22:12:10 741310 FAILURE UNAVAILABLE NaN NaN
3 9246 osm-stage_3-merge/v17.0 412 2026-02-21 17:49:09 30725 FAILURE UNAVAILABLE NaN NaN
4 9247 osm-stage_3-merge/v16.0 521 2026-02-22 02:41:07 27710 FAILURE UNAVAILABLE NaN NaN
5 9248 osm-stage_3-merge/v14.0 939 2026-02-21 19:08:09 28698 FAILURE UNAVAILABLE NaN NaN

Click to see the details of build 3661 of osm-stage_3-merge/master

Click to see the details of build 23 of osm-stage_3-merge/v19.0

Click to see the details of build 189 of osm-stage_3-merge/v18.0

Click to see the details of build 412 of osm-stage_3-merge/v17.0

Click to see the details of build 521 of osm-stage_3-merge/v16.0

Click to see the details of build 939 of osm-stage_3-merge/v14.0

Failed test suites per job (if any):¶

osm-stage_3-merge/master: (full report)

auto_id name status starttime endtime pass fail failed_test_name failed_keyword

osm-stage_3-merge/v19.0: (full report)

auto_id name status starttime endtime pass fail failed_test_name failed_keyword

osm-stage_3-merge/v18.0: (full report)

auto_id name status starttime endtime pass fail failed_test_name failed_keyword

osm-stage_3-merge/v17.0: (full report)

auto_id name status starttime endtime pass fail failed_test_name failed_keyword

osm-stage_3-merge/v16.0: (full report)

auto_id name status starttime endtime pass fail failed_test_name failed_keyword

osm-stage_3-merge/v14.0: (full report)

auto_id name status starttime endtime pass fail failed_test_name failed_keyword

Details of failed tests into failing test suites (if any):¶

osm-stage_3-merge/master: (full report)

auto_id suite_name test_name keyword_name status starttime endtime

osm-stage_3-merge/v19.0: (full report)

auto_id suite_name test_name keyword_name status starttime endtime

osm-stage_3-merge/v18.0: (full report)

auto_id suite_name test_name keyword_name status starttime endtime

osm-stage_3-merge/v17.0: (full report)

auto_id suite_name test_name keyword_name status starttime endtime

osm-stage_3-merge/v16.0: (full report)

auto_id suite_name test_name keyword_name status starttime endtime

osm-stage_3-merge/v14.0: (full report)

auto_id suite_name test_name keyword_name status starttime endtime



Powered by osm-analytics