Analysis of Robot reports from OSM Jenkins¶

Date and time of the report: 2026-02-05 08:45:06.134415

Analysed period: 2026-01-15 to 2026-02-05.

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/v18.0, osm-stage_3-merge/v17.0, osm-stage_3-merge/v16.0, osm-stage_3-merge/v14.0

Traceback (most recent call last):
  File "/opt/conda/lib/python3.13/site-packages/jenkins/__init__.py", line 596, in jenkins_request
    return self._response_handler(
           ~~~~~~~~~~~~~~~~~~~~~~^
        self._request(req, stream))
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/lib/python3.13/site-packages/jenkins/__init__.py", line 549, in _response_handler
    response.raise_for_status()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/opt/conda/lib/python3.13/site-packages/requests/models.py", line 1024, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://osm.etsi.org/jenkins/job/osm-stage_3-merge/job/master/api/json?depth=0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/conda/lib/python3.13/site-packages/jenkins/__init__.py", line 478, in get_job_info
    response = self.jenkins_open(requests.Request(
        'GET', self._build_url(JOB_INFO, locals())
    ))
  File "/opt/conda/lib/python3.13/site-packages/jenkins/__init__.py", line 570, in jenkins_open
    return self.jenkins_request(req, add_crumb, resolve_auth).text
           ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/lib/python3.13/site-packages/jenkins/__init__.py", line 610, in jenkins_request
    raise NotFoundException('Requested item could not be found')
jenkins.NotFoundException: Requested item could not be found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/osm-analytics/Jenkins/./00-script-jenkins_and_robot_etl.py", line 98, in <module>
    ingest_update_all_jenkins_job(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        jenkins_server=server,
        ^^^^^^^^^^^^^^^^^^^^^^
    ...<8 lines>...
        table_robot_reports_extended=table_robot_reports_extended
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/osm-analytics/Jenkins/jenkins_robot_etl.py", line 32, in ingest_update_all_jenkins_job
    df_builds_of_job = get_all_job_builds(jenkins_server, job_name)
  File "/osm-analytics/Jenkins/jenkins_lib.py", line 79, in get_all_job_builds
    my_job = server.get_job_info(job_name, 0, True)
  File "/opt/conda/lib/python3.13/site-packages/jenkins/__init__.py", line 489, in get_job_info
    raise JenkinsException('job[%s] does not exist' % name)
jenkins.JenkinsException: job[osm-stage_3-merge/master] does not exist

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

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

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 
Empty dataframe. Skipping.
Empty dataframe. Skipping.
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
Out[58]:
job Master branch Release EIGHTEEN Release FOURTEEN 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.361791 21.361791 0.0 0.000000 18.440969 18.440969 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Basic 05-Instantiation Parameters In Cloud Init 0.000000 21.361791 21.361791 0.0 0.000000 18.440969 18.440969 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Basic 06-Vnf With Charm 0.000000 0.000000 0.000000 0.0 0.000000 0.000000 0.000000 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Basic 07-Secure Key Management 0.000000 0.000000 0.000000 0.0 0.000000 0.000000 0.000000 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Basic 08-Disable Port Security Network Level 0.000000 21.361791 21.361791 0.0 0.000000 18.440969 18.440969 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Sa 08-Vnf With Vnf Indicators Snmp 21.361791 0.000000 21.361791 1.0 18.440969 0.000000 18.440969 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Slice 01-Network Slicing 0.000000 21.361791 21.361791 0.0 0.000000 18.440969 18.440969 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Slice 02-Shared Network Slicing 0.000000 21.361791 21.361791 0.0 0.000000 18.440969 18.440969 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Sol003 01-Vnf-Lifecycle-Management 0.000000 21.361791 21.361791 0.0 0.000000 18.440969 18.440969 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Sol003 02-Dualstack Ip Vnfm 0.000000 21.361791 21.361791 0.0 0.000000 18.440969 18.440969 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

62 rows × 20 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 9127 osm-stage_3-merge/master 3642 2026-02-03 00:06:13 13247393 SUCCESS FAIL 481.0 4.0
1 9132 osm-stage_3-merge/v18.0 171 2026-02-03 22:12:14 0 FAILURE UNAVAILABLE NaN NaN
2 9133 osm-stage_3-merge/v17.0 394 2026-02-03 17:49:13 0 FAILURE UNAVAILABLE NaN NaN
3 9130 osm-stage_3-merge/v16.0 503 2026-02-03 02:41:14 1356215 FAILURE UNAVAILABLE NaN NaN
4 9134 osm-stage_3-merge/v14.0 921 2026-02-03 19:08:14 1180713 FAILURE UNAVAILABLE NaN NaN

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

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

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

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

Click to see the details of build 921 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
116 258111 Epa 04-Epa Underlay Sriov FAIL 2026-02-03 01:30:03 2026-02-03 01:33:12 7 2 Ping from Vnf1 to Vnf2 Execute Remote Command Check Rc Return Output
136 258131 Sa 08-Vnf With Vnf Indicators Snmp FAIL 2026-02-03 03:18:04 2026-02-03 03:28:59 5 2 Instantiate Network Service Create Network Service

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
101 6738252 Epa 04-Epa Underlay Sriov Ping from Vnf1 to Vnf2 Execute Remote Command Check Rc Return Output FAIL 2026-02-03 01:31:51 2026-02-03 01:32:07
104 6738255 Epa 04-Epa Underlay Sriov Ping from Vnf2 to Vnf1 Execute Remote Command Check Rc Return Output FAIL 2026-02-03 01:32:07 2026-02-03 01:32:15
111 6738906 Sa 08-Vnf With Vnf Indicators Snmp Instantiate Network Service Create Network Service FAIL 2026-02-03 03:18:07 2026-02-03 03:19:19
116 6738911 Sa 08-Vnf With Vnf Indicators Snmp Get VNF SNMP Metrics Wait Until Keyword Succeeds FAIL 2026-02-03 03:19:19 2026-02-03 03:28:20

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