[ 
https://issues.apache.org/jira/browse/YARN-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Bodo updated YARN-9119:
----------------------------
    Description: 
The execution of {{testLinuxGpuResourceDiscoverPluginConfig}} depends on a 
system property: {{RunLinuxGpuResourceDiscoverPluginConfigTest}}. This is most 
likely the test executor creates the required files during test runs (!), 
making the tests not executable locally.

----

- The logic of looking up nvidia binary should be separated from the 
{{GpuDiscoverer}}.
- The testcase should also be separated to 3 different testcases, as the 
comment says in the code.

  was:This testcase should be separated to 3 different testcases, as the 
comment says in the code.

        Summary: Extract nvidia-smi binary lookup logic from GpuDiscoverer  
(was: Clean up testcase 
TestGpuDiscoverer.testLinuxGpuResourceDiscoverPluginConfig)

> Extract nvidia-smi binary lookup logic from GpuDiscoverer
> ---------------------------------------------------------
>
>                 Key: YARN-9119
>                 URL: https://issues.apache.org/jira/browse/YARN-9119
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Szilard Nemeth
>            Assignee: Alex Bodo
>            Priority: Major
>              Labels: newbie, newbie++
>
> The execution of {{testLinuxGpuResourceDiscoverPluginConfig}} depends on a 
> system property: {{RunLinuxGpuResourceDiscoverPluginConfigTest}}. This is 
> most likely the test executor creates the required files during test runs 
> (!), making the tests not executable locally.
> ----
> - The logic of looking up nvidia binary should be separated from the 
> {{GpuDiscoverer}}.
> - The testcase should also be separated to 3 different testcases, as the 
> comment says in the code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to