Analysis of Robot reports from OSM Jenkins

Date and time of the report: 2023-06-06 08:20:37.642094

Analysed period: 2023-05-16 to 2023-06-06.

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

job	Master branch				Release TEN				Release THIRTEEN				Release TWELVE
	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	5.387025	11.833018	17.220044	0.312835	0.000000	21.135298	21.135298	0.000000	0.000000	20.344384	20.344384	0.000000	0.000000	21.263088	21.263088	0.000000
Basic 05-Instantiation Parameters In Cloud Init	0.000000	17.220044	17.220044	0.000000	5.000000	16.135298	21.135298	0.236571	0.000000	20.344384	20.344384	0.000000	0.000000	21.263088	21.263088	0.000000
Basic 06-Vnf With Charm	0.000000	17.220044	17.220044	0.000000	5.999954	15.135345	21.135298	0.283883	0.000000	20.344384	20.344384	0.000000	1.044988	20.218099	21.263088	0.049146
Basic 07-Secure Key Management	0.000000	17.220044	17.220044	0.000000	5.000000	16.135298	21.135298	0.236571	0.000000	20.344384	20.344384	0.000000	1.044988	20.218099	21.263088	0.049146
Basic 08-Disable Port Security Network Level	5.387025	11.833018	17.220044	0.312835	0.000000	21.135298	21.135298	0.000000	0.000000	20.344384	20.344384	0.000000	1.044988	20.218099	21.263088	0.049146
...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...
Slice 01-Network Slicing	0.000000	17.220044	17.220044	0.000000	0.000000	21.135298	21.135298	0.000000	3.000046	17.344338	20.344384	0.147463	1.000000	20.263088	21.263088	0.047030
Slice 02-Shared Network Slicing	4.387037	12.833007	17.220044	0.254763	0.000000	21.135298	21.135298	0.000000	3.000046	17.344338	20.344384	0.147463	3.044977	18.218111	21.263088	0.143205
Sol003 01-Vnf-Lifecycle-Management	0.000000	17.220044	17.220044	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	20.344384	20.344384	0.000000	0.000000	21.263088	21.263088	0.000000
basic 23-delete vnf package SOL004 SOL007	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000
k8s 10-k8s proxy charms SOL004 SOL007	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000	0.000000

63 rows × 16 columns

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	2611	2023-06-06 01:06:24	2292358	FAILURE	UNAVAILABLE	NaN	NaN
1	osm-stage_3-merge/v13.0	223	2023-06-05 22:07:24	2095461	FAILURE	UNAVAILABLE	NaN	NaN
2	osm-stage_3-merge/v12.0	417	2023-06-06 00:04:24	2034858	FAILURE	UNAVAILABLE	NaN	NaN
3	osm-stage_3-merge/v10.0	833	2023-06-06 03:08:24	2155282	FAILURE	UNAVAILABLE	NaN	NaN

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

Click to see the details of build 223 of osm-stage_3-merge/v13.0

Click to see the details of build 417 of osm-stage_3-merge/v12.0

Click to see the details of build 833 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

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

	name	status	starttime	endtime	pass	fail	failed_test_name	failed_keyword

osm-stage_3-merge/v12.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

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

	suite_name	test_name	keyword_name	status	starttime	endtime

osm-stage_3-merge/v12.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

---

---