Analysis of Robot reports from OSM Jenkins

Date and time of the report: 2022-02-12 08:20:23.771741

Analysed period: 2022-01-22 to 2022-02-12.

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	1982	2022-02-12 02:06:20	11199483	SUCCESS	FAIL	416.0	1.0
1	osm-stage_3-merge/v11.0	135	2022-02-12 00:00:19	11390469	SUCCESS	FAIL	416.0	1.0
2	osm-stage_3-merge/v10.0	301	2022-02-12 04:08:20	1168123	FAILURE	UNAVAILABLE	NaN	NaN

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

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

Click to see the details of build 301 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
55	Fail 01-Insufficient Resources	FAIL	2022-02-12 03:56:13	2022-02-12 03:57:47	5	1	Cannot Instantiate Network Service	Should Contain

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

	name	status	starttime	endtime	pass	fail	failed_test_name	failed_keyword
98	Fail 01-Insufficient Resources	FAIL	2022-02-12 01:51:00	2022-02-12 01:52:34	5	1	Cannot Instantiate Network Service	Should Contain

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
13	Fail 01-Insufficient Resources	Cannot Instantiate Network Service	Should Contain	FAIL	2022-02-12 03:57:01	2022-02-12 03:57:01

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

	suite_name	test_name	keyword_name	status	starttime	endtime
34	Fail 01-Insufficient Resources	Cannot Instantiate Network Service	Should Contain	FAIL	2022-02-12 01:51:48	2022-02-12 01:51:48

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

	suite_name	test_name	keyword_name	status	starttime	endtime

---

---