Analysis of Robot reports from OSM Jenkins

Date and time of the report: 2025-02-11 08:20:23.138896

Analysed period: 2025-01-21 to 2025-02-11.

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 FIFTEEN				Release FOURTEEN				Release SIXTEEN
	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.316956	21.316956	0.000000	0.0	6.300012	6.300012	0.0	0.0	20.500046	20.500046	0.0	0.0	21.463275	21.463275	0.0
Basic 05-Instantiation Parameters In Cloud Init	0.000000	21.316956	21.316956	0.000000	0.0	6.300012	6.300012	0.0	0.0	20.500046	20.500046	0.0	0.0	21.463275	21.463275	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.500046	20.500046	0.0	0.0	0.000000	0.000000	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.500046	20.500046	0.0	0.0	0.000000	0.000000	0.0
Basic 08-Disable Port Security Network Level	0.000000	21.316956	21.316956	0.000000	0.0	6.300012	6.300012	0.0	0.0	20.500046	20.500046	0.0	0.0	21.463275	21.463275	0.0
...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...	...
Slice 02-Shared Network Slicing	1.000312	20.316644	21.316956	0.046926	0.0	6.300012	6.300012	0.0	0.0	20.500046	20.500046	0.0	0.0	21.463275	21.463275	0.0
Sol003 01-Vnf-Lifecycle-Management	0.000000	21.316956	21.316956	0.000000	0.0	6.300012	6.300012	0.0	0.0	20.500046	20.500046	0.0	0.0	21.463275	21.463275	0.0
Sol003 02-Dualstack Ip Vnfm	0.000000	21.316956	21.316956	0.000000	0.0	6.300012	6.300012	0.0	0.0	0.000000	0.000000	0.0	0.0	21.463275	21.463275	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

67 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	3267	2025-02-10 07:39:23	12366662	UNSTABLE	FAIL	465.0	7.0
1	osm-stage_3-merge/v16.0	149	2025-02-11 04:13:42	0	FAILURE	UNAVAILABLE	NaN	NaN
2	osm-stage_3-merge/v15.0	406	2025-02-10 11:05:39	12376188	UNSTABLE	FAIL	448.0	7.0
3	osm-stage_3-merge/v14.0	562	2025-02-10 23:08:15	18316260	UNSTABLE	FAIL	610.0	9.0

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

Click to see the details of build 149 of osm-stage_3-merge/v16.0

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

Click to see the details of build 562 of osm-stage_3-merge/v14.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
165	Sa 01-Vnf With Vim Metrics	FAIL	2025-02-10 09:32:16	2025-02-10 09:47:36	6	1	Get VNF VIM-based Metrics	Wait Until Keyword Succeeds
166	Sa 02-Vnf With Vim Metrics And Autoscaling	FAIL	2025-02-10 09:47:36	2025-02-10 10:21:10	11	4	Get VNF VIM-based Metric Before Auto-scaling	Wait Until Keyword Succeeds
167	Sa 07-Alarms From Sa-Related Vnfs	FAIL	2025-02-10 10:21:10	2025-02-10 10:42:08	14	2	Get Alarm Metric	Wait Until Keyword Succeeds

osm-stage_3-merge/v16.0: (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
266	Sa 01-Vnf With Vim Metrics	FAIL	2025-02-10 13:00:50	2025-02-10 13:16:42	6	1	Get VNF VIM-based Metrics	Wait Until Keyword Succeeds
267	Sa 02-Vnf With Vim Metrics And Autoscaling	FAIL	2025-02-10 13:16:42	2025-02-10 13:50:11	11	4	Get VNF VIM-based Metric Before Auto-scaling	Wait Until Keyword Succeeds
268	Sa 07-Alarms From Sa-Related Vnfs	FAIL	2025-02-10 13:50:11	2025-02-10 14:11:37	14	2	Get Alarm Metric	Wait Until Keyword Succeeds

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

	name	status	starttime	endtime	pass	fail	failed_test_name	failed_keyword
182	Basic 14-Vnf Relations	FAIL	2025-02-10 23:59:56	2025-02-11 00:02:57	5	1	Instantiate Charm Network Service	Create Network Service
211	Heal 04-Autohealing	FAIL	2025-02-11 01:51:49	2025-02-11 02:00:43	13	1	Check VNF After Healing	Should Not Be Equal
224	Sa 01-Vnf With Vim Metrics	FAIL	2025-02-11 02:43:26	2025-02-11 02:59:18	6	1	Get VNF VIM-based Metrics	Wait Until Keyword Succeeds
225	Sa 02-Vnf With Vim Metrics And Autoscaling	FAIL	2025-02-11 02:59:18	2025-02-11 03:32:48	11	4	Get VNF VIM-based Metric Before Auto-scaling	Wait Until Keyword Succeeds
226	Sa 07-Alarms From Sa-Related Vnfs	FAIL	2025-02-11 03:32:48	2025-02-11 03:53:41	14	2	Get Alarm Metric	Wait Until Keyword Succeeds

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
10	Sa 01-Vnf With Vim Metrics	Get VNF VIM-based Metrics	Wait Until Keyword Succeeds	FAIL	2025-02-10 09:32:58	2025-02-10 09:46:59
40	Sa 02-Vnf With Vim Metrics And Autoscaling	Get VNF VIM-based Metric Before Auto-scaling	Wait Until Keyword Succeeds	FAIL	2025-02-10 09:48:25	2025-02-10 10:02:26
45	Sa 02-Vnf With Vim Metrics And Autoscaling	Wait VIM-based Metric To Exceed Threshold	Wait Until Keyword Succeeds	FAIL	2025-02-10 10:02:28	2025-02-10 10:16:29
48	Sa 02-Vnf With Vim Metrics And Autoscaling	Check VIM-based Metric Exceeds Threshold After...	Check VIM-based Metric Exceeds Threshold	FAIL	2025-02-10 10:18:29	2025-02-10 10:18:29
79	Sa 07-Alarms From Sa-Related Vnfs	Get Alarm Metric	Wait Until Keyword Succeeds	FAIL	2025-02-10 10:23:19	2025-02-10 10:37:20
80	Sa 07-Alarms From Sa-Related Vnfs	Check Alarms Were Received	Wait Until Keyword Succeeds	FAIL	2025-02-10 10:37:20	2025-02-10 10:40:50

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

	suite_name	test_name	keyword_name	status	starttime	endtime

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

	suite_name	test_name	keyword_name	status	starttime	endtime
243	Sa 01-Vnf With Vim Metrics	Get VNF VIM-based Metrics	Wait Until Keyword Succeeds	FAIL	2025-02-10 13:02:04	2025-02-10 13:16:05
273	Sa 02-Vnf With Vim Metrics And Autoscaling	Get VNF VIM-based Metric Before Auto-scaling	Wait Until Keyword Succeeds	FAIL	2025-02-10 13:17:29	2025-02-10 13:31:30
278	Sa 02-Vnf With Vim Metrics And Autoscaling	Wait VIM-based Metric To Exceed Threshold	Wait Until Keyword Succeeds	FAIL	2025-02-10 13:31:32	2025-02-10 13:45:32
281	Sa 02-Vnf With Vim Metrics And Autoscaling	Check VIM-based Metric Exceeds Threshold After...	Check VIM-based Metric Exceeds Threshold	FAIL	2025-02-10 13:47:32	2025-02-10 13:47:32
312	Sa 07-Alarms From Sa-Related Vnfs	Get Alarm Metric	Wait Until Keyword Succeeds	FAIL	2025-02-10 13:52:53	2025-02-10 14:06:53
313	Sa 07-Alarms From Sa-Related Vnfs	Check Alarms Were Received	Wait Until Keyword Succeeds	FAIL	2025-02-10 14:06:53	2025-02-10 14:10:24

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

	suite_name	test_name	keyword_name	status	starttime	endtime
89	Basic 14-Vnf Relations	Instantiate Charm Network Service	Create Network Service	FAIL	2025-02-11 00:00:02	2025-02-11 00:02:18
130	Heal 04-Autohealing	Check VNF After Healing	Should Not Be Equal	FAIL	2025-02-11 02:00:03	2025-02-11 02:00:03
149	Sa 01-Vnf With Vim Metrics	Get VNF VIM-based Metrics	Wait Until Keyword Succeeds	FAIL	2025-02-11 02:44:41	2025-02-11 02:58:41
182	Sa 02-Vnf With Vim Metrics And Autoscaling	Get VNF VIM-based Metric Before Auto-scaling	Wait Until Keyword Succeeds	FAIL	2025-02-11 03:00:07	2025-02-11 03:14:07
189	Sa 02-Vnf With Vim Metrics And Autoscaling	Wait VIM-based Metric To Exceed Threshold	Wait Until Keyword Succeeds	FAIL	2025-02-11 03:14:09	2025-02-11 03:28:10
192	Sa 02-Vnf With Vim Metrics And Autoscaling	Check VIM-based Metric Exceeds Threshold After...	Check VIM-based Metric Exceeds Threshold	FAIL	2025-02-11 03:30:10	2025-02-11 03:30:10
197	Sa 02-Vnf With Vim Metrics And Autoscaling	Get VDUs After Auto-scaling	Run Keyword If	FAIL	2025-02-11 03:32:10	2025-02-11 03:32:10
224	Sa 07-Alarms From Sa-Related Vnfs	Get Alarm Metric	Wait Until Keyword Succeeds	FAIL	2025-02-11 03:34:56	2025-02-11 03:48:56
226	Sa 07-Alarms From Sa-Related Vnfs	Check Alarms Were Received	Wait Until Keyword Succeeds	FAIL	2025-02-11 03:48:56	2025-02-11 03:52:27

---

---

---

Powered by osm-analytics