Analysis of Robot reports from OSM Jenkins¶

Date and time of the report: 2024-07-19 08:20:25.740065

Analysed period: 2024-06-28 to 2024-07-19.

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.000000	21.561331	21.561331	0.000000	0.0	21.479144	21.479144	0.0	0.0	20.684907	20.684907	0.0	0.0	21.604398	21.604398	0.0
Basic 05-Instantiation Parameters In Cloud Init	0.000000	21.561331	21.561331	0.000000	0.0	21.479144	21.479144	0.0	0.0	20.684907	20.684907	0.0	0.0	21.604398	21.604398	0.0
Basic 06-Vnf With Charm	0.000000	0.000000	0.000000	0.000000	0.0	0.000000	0.000000	0.0	0.0	20.684907	20.684907	0.0	0.0	21.604398	21.604398	0.0
Basic 07-Secure Key Management	0.000000	0.000000	0.000000	0.000000	0.0	0.000000	0.000000	0.0	0.0	20.684907	20.684907	0.0	0.0	21.604398	21.604398	0.0
Basic 08-Disable Port Security Network Level	0.000000	21.561331	21.561331	0.000000	0.0	21.479144	21.479144	0.0	0.0	20.684907	20.684907	0.0	0.0	21.604398	21.604398	0.0
...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...
Slice 02-Shared Network Slicing	2.000012	19.561319	21.561331	0.092759	0.0	21.479144	21.479144	0.0	0.0	20.684907	20.684907	0.0	0.0	21.604398	21.604398	0.0
Sol003 01-Vnf-Lifecycle-Management	0.000000	21.561331	21.561331	0.000000	0.0	21.479144	21.479144	0.0	0.0	20.684907	20.684907	0.0	0.0	21.604398	21.604398	0.0
Sol003 02-Dualstack Ip Vnfm	0.000000	21.561331	21.561331	0.000000	0.0	21.479144	21.479144	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.000000	0.000000	0.000000	0.000000	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.000000	0.000000	0.000000	0.000000	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	3054	2024-07-19 01:06:36	9724236	SUCCESS	PASS	456.0	0.0
1	osm-stage_3-merge/v15.0	243	2024-07-19 02:34:41	9804288	SUCCESS	PASS	455.0	0.0
2	osm-stage_3-merge/v14.0	393	2024-07-18 22:08:39	16198522	SUCCESS	FAIL	601.0	2.0
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	809	2024-07-19 00:04:36	14842648	SUCCESS	PASS	530.0	0.0
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 3054 of osm-stage_3-merge/master

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

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

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
253	Epa 04-Epa Underlay Sriov	FAIL	2024-07-19 00:12:54	2024-07-19 00:15:31	7	2	Ping from Vnf1 to Vnf2	Execute Remote Command Check Rc Return Output

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):¶