Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2179059

Summary:	[ERFE] Add more OVS tests to the 0day robot and report upstream trough patchwork
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	Eelco Chaudron <echaudro>
Component:	openvswitch	Assignee:	Michael Santana <msantana>
openvswitch sub component:	daemons and tools	QA Contact:	qding
Status:	CLOSED COMPLETED	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	ctrautma, fleitner, jhsiao
Version:	FDP 23.K
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-12 16:09:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eelco Chaudron 2023-03-16 14:33:17 UTC

The goal for this BZ is to run more tests as part of the 0day robot and report the results through patchwork. The goal is to have these tests run in a virtual environment isolated from the host/internal Red Hat network.

To start with we would need the following tests to be run:

- make check-kernel
- make check-offloads
- make check-system-userspace
- make check-dpdk  [WITHOUT PHYSICAL PORTS]
- make check-afxdp

The (failure) details of these runs should be stored in a GitHub for analysis due to the lack of storage space/limited email lengths.


We also need a way to expose the FreeBSD runs that are currently executed by the robot to patchwork. For example https://github.com/ovsrobot/ovs/runs/11935632494

On top of the above, we also need to do windows builds/tests using the Cirrus CI, and report this to patchwork.

Finally, we would also like to run "make clang-analyze" and report any newly introduced issues. I think we could probably do this by exporting the trace to sarif format and using the diff tools. More details can be found here:https://github.com/microsoft/sarif-tutorials

Comment 2 Eelco Chaudron 2023-03-16 14:44:33 UTC

Added a Vagrant example which will set up a fedora VM with all the tools needed. In addition, there is a script that will run the tests. It does not include the custom RPMS but instructions on how to create them are included (or ping me offline and I can get them to you).

The main reason for adding this is to just get an idea of what tools/setup is needed to run all the datapath tests.

Assigned BZ to Flavio for re-assignment.

Comment 3 Eelco Chaudron 2023-12-07 12:58:25 UTC

All the make check-* and make clang-analyse will be integrated into GitHub actions. The following FDP issue, https://issues.redhat.com/browse/FDP-197.

Which then leaves the following items:

```
We also need a way to expose the FreeBSD runs that are currently executed by the robot to patchwork. For example https://github.com/ovsrobot/ovs/runs/11935632494

On top of the above, we also need to do windows builds/tests using the Cirrus CI, and report this to patchwork.
```

Comment 5 Eelco Chaudron 2024-03-12 16:09:07 UTC

I've done this, so will close it.