You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@yunikorn.apache.org by "Manikandan R (Jira)" <ji...@apache.org> on 2023/01/17 11:41:00 UTC

[jira] [Updated] (YUNIKORN-1531) Log the yk logs, dump etc to stdout

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

Manikandan R updated YUNIKORN-1531:
-----------------------------------
    Description: Cappture all the necessary details like logs, cluster dump, node details etc either in stdout or some place to debug ginkgo test failures. This would be handy especially when test works locally and failures are occurring only on github runners or any different environments.  (was: Cappture all the necessary details like logs, dump etc either in stdout or some place to debug ginkgo test failures. This would be handy especially when test works locally and failures are occurring only on github runners or any different environments.)

> Log the yk logs, dump etc to stdout
> -----------------------------------
>
>                 Key: YUNIKORN-1531
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1531
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>            Reporter: Manikandan R
>            Priority: Major
>
> Cappture all the necessary details like logs, cluster dump, node details etc either in stdout or some place to debug ginkgo test failures. This would be handy especially when test works locally and failures are occurring only on github runners or any different environments.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org