Analysis of Robot reports from OSM Jenkins¶

Date and time of the report: 2024-03-26 08:20:23.353778

Analysed period: 2024-03-05 to 2024-03-26.

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:

Successful builds/failed builds in a row: grp_build_result.
Successful test reports vs. test reports with fails in a row: grp_test_result.
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¶

Empty dataframe. Skipping.

Empty dataframe. Skipping.

3.2 Overall success of Jenkins builds and Robot tests¶

3.3 Sequences of pass/fails per test suites¶

Empty dataframe. Skipping.

Empty dataframe. Skipping.

3.4 Failing days per test suite¶

Empty dataframe. Skipping.

Empty dataframe. Skipping.

Out[58]:

job	Master branch				Release FIFTEEN				Release FOURTEEN				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	0.0	18.976574	18.976574	0.0	0.0	12.128831	12.128831	0.0	0.0	12.623588	12.623588	0.0	0.0	11.543021	11.543021	0.0
Basic 05-Instantiation Parameters In Cloud Init	0.0	18.976574	18.976574	0.0	0.0	12.128831	12.128831	0.0	0.0	12.623588	12.623588	0.0	0.0	11.543021	11.543021	0.0
Basic 06-Vnf With Charm	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0	0.0	12.623588	12.623588	0.0	0.0	11.543021	11.543021	0.0
Basic 07-Secure Key Management	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0	0.0	12.623588	12.623588	0.0	0.0	11.543021	11.543021	0.0
Basic 08-Disable Port Security Network Level	0.0	18.976574	18.976574	0.0	0.0	12.128831	12.128831	0.0	0.0	12.623588	12.623588	0.0	0.0	11.543021	11.543021	0.0
...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...
Slice 02-Shared Network Slicing	0.0	18.976574	18.976574	0.0	0.0	12.128831	12.128831	0.0	0.0	12.623588	12.623588	0.0	0.0	11.543021	11.543021	0.0
Sol003 01-Vnf-Lifecycle-Management	0.0	18.976574	18.976574	0.0	0.0	12.128831	12.128831	0.0	0.0	12.623588	12.623588	0.0	0.0	11.543021	11.543021	0.0
Sol003 02-Dualstack Ip Vnfm	0.0	18.976574	18.976574	0.0	0.0	12.128831	12.128831	0.0	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0
basic 23-delete vnf package SOL004 SOL007	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0
k8s 10-k8s proxy charms SOL004 SOL007	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0	0.0	0.000000	0.000000	0.0

66 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	2935	2024-03-26 02:06:13	10934806	SUCCESS	FAIL	449.0	2.0
1	osm-stage_3-merge/v15.0	99	2024-03-26 05:08:34	0	FAILURE	UNAVAILABLE	NaN	NaN
2	osm-stage_3-merge/v14.0	277	2024-03-25 23:08:12	2574113	FAILURE	UNAVAILABLE	NaN	NaN
3	osm-stage_3-merge/v13.0	446	2024-01-31 21:07:31	15541814	SUCCESS	PASS	558.0	0.0
4	osm-stage_3-merge/v12.0	695	2024-03-26 01:04:13	1377324	FAILURE	UNAVAILABLE	NaN	NaN
5	osm-stage_3-merge/v10.0	1053	2024-02-01 04:08:33	2336073	FAILURE	UNAVAILABLE	NaN	NaN

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

Click to see the details of build 99 of osm-stage_3-merge/v15.0

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

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

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

Click to see the details of build 1053 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
155	Heal 02-Scale Vdu Healing	FAIL	2024-03-26 03:34:49	2024-03-26 03:39:42	15	1	Check VNF After Healing	Execute Remote Command Check Rc Return Output
156	Heal 03-Multiple Healing	FAIL	2024-03-26 03:39:42	2024-03-26 03:45:09	15	1	Check VNFs After Healing	Check If Remote File Exists

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

	name	status	starttime	endtime	pass	fail	failed_test_name	failed_keyword

osm-stage_3-merge/v14.0: (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):¶