You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2024/01/10 20:56:00 UTC
[jira] [Resolved] (YUNIKORN-2305) E2E test: Upload stdout logs to Github Action artifact
[ https://issues.apache.org/jira/browse/YUNIKORN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko resolved YUNIKORN-2305.
------------------------------------
Fix Version/s: 1.5.0
Resolution: Fixed
Merged to master, thanks [~Yu-Lin Chen] for the contribution.
> E2E test: Upload stdout logs to Github Action artifact
> ------------------------------------------------------
>
> Key: YUNIKORN-2305
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2305
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: test - e2e
> Reporter: Yu-Lin Chen
> Assignee: Yu-Lin Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> In current e2e test, there are 2 types of logging
> * [ginkgo.By|https://onsi.github.io/ginkgo/#documenting-complex-specs-by] : Document the specs and their steps.
> * [ginkgo.GinkgoWriter|https://onsi.github.io/ginkgo/#logging-output] : Dump cluster status to stdout when the test failed. (Current including scheduler REST result and scheduler pod logs.)
> Those kinds of information are mixed up in Github Actions logs, making it hard to read.
> We should use the [upload-artifact|https://github.com/actions/upload-artifact?tab=readme-ov-file] in Github Action to upload stdout to artifact.
> PS: This is a follow-up Jira based on the discussion in YUNIKORN-2293
--
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