[
https://issues.apache.org/jira/browse/YUNIKORN-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YUNIKORN-1833:
-----------------------------------
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Â
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).
was:
After YUNIKORN-1801 and YUNIKORN-1802, we generate way too many events and they
can't be conveniently verified in {{{}partition_test.go{}}}.
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).
> Rationalize event verification in partition_test.go
> ---------------------------------------------------
>
> Key: YUNIKORN-1833
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1833
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> 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Â
> 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).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
