Analysis of Robot reports from OSM Jenkins

Date and time of the report: 2022-02-05 08:20:29.677145

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

1. Retrieval of all currrent data for aggregate analytics

Database update:

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

3.2 Overall success of Jenkins builds and Robot tests

3.3 Sequences of pass/fails per test suites

3.4 Failing days per test suite

4. Information about the latest builds of relevant jobs

Latest build of each job

	job	build	timestamp	duration	build_result	test_result	pass_count	fail_count
0	osm-stage_3-merge/master	1974	2022-02-05 02:06:14	10031064	SUCCESS	FAIL	413.0	4.0
1	osm-stage_3-merge/v11.0	122	2022-02-05 00:00:18	0	FAILURE	UNAVAILABLE	NaN	NaN
2	osm-stage_3-merge/v10.0	292	2022-02-05 04:08:13	4202	FAILURE	UNAVAILABLE	NaN	NaN

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

Click to see the details of build 122 of osm-stage_3-merge/v11.0

Click to see the details of build 292 of osm-stage_3-merge/v10.0

Failed test suites per job (if any):

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

	name	status	starttime	endtime	pass	fail	failed_test_name	failed_keyword
54	Epa 04-Epa Underlay Sriov	FAIL	2022-02-05 03:39:42	2022-02-05 03:41:14	5	4	Instantiate Network Service	Create Network Service

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

	name	status	starttime	endtime	pass	fail	failed_test_name	failed_keyword

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

	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)

	suite_name	test_name	keyword_name	status	starttime	endtime
3	Epa 04-Epa Underlay Sriov	Instantiate Network Service	Create Network Service	FAIL	2022-02-05 03:39:46	2022-02-05 03:40:30
5	Epa 04-Epa Underlay Sriov	Get Management Ip Addresses	Variable Should Exist	FAIL	2022-02-05 03:40:30	2022-02-05 03:40:30
12	Epa 04-Epa Underlay Sriov	Ping from Vnf1 to Vnf2	Variable Should Exist	FAIL	2022-02-05 03:40:30	2022-02-05 03:40:30
16	Epa 04-Epa Underlay Sriov	Ping from Vnf2 to Vnf1	Variable Should Exist	FAIL	2022-02-05 03:40:30	2022-02-05 03:40:30

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

	suite_name	test_name	keyword_name	status	starttime	endtime

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

	suite_name	test_name	keyword_name	status	starttime	endtime

---

---