[YUNIKORN-1833] Rationalize event verification in partition_test.go

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: core - scheduler
• Labels: pull-request-available
• Assignee: Peter Bacsko
• Reporter: Peter Bacsko
• Created: 23/Jun/23 08:11
• Updated: 20/Nov/23 16:42
• Resolved: 29/Jun/23 15:15

Description

After YUNIKORN-1801 and YUNIKORN-1802, we generate way too many events and they can't be conveniently verified in partition_test.go. Things will get worse after YUNIKORN-1803.

Let's move them to a different unit test or maybe remove the checks entirely and provide coverage somewhere else (partition_test.go is a slightly bigger, integration-like test anyway, we can't validate everything in these scenarios).

Issue Links

• links to: GitHub Pull Request #583