Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

k6 cloud --quiet exits immediately after the test run starts #1371

Closed
na-- opened this issue Mar 23, 2020 · 1 comment · Fixed by #1702
Closed

k6 cloud --quiet exits immediately after the test run starts #1371

na-- opened this issue Mar 23, 2020 · 1 comment · Fixed by #1702
Assignees
Labels
Milestone

Comments

@na--
Copy link
Member

na-- commented Mar 23, 2020

This check: https://github.com/loadimpact/k6/blob/4c7c4bf135a8b68a77549484d2a627fee4128570/cmd/cloud.go#L191-L193

causes --quiet to exit the k6 cloud process prematurely. This may sometimes be useful, but we have another option that is specifically meant for that, k6 cloud --exit-on-running, so we should fix this.

@na-- na-- added the bug label Mar 23, 2020
@na-- na-- added this to the v0.29.0 milestone Oct 30, 2020
@qcastel
Copy link

qcastel commented Oct 30, 2020

To give a bit more context on why I was trying to use this option and hit that bug:

When you run K6 cloud from a CI, the progression bar is spamming the CI log. As we are limited on the number of logs we can do in CI, I was interested to avoid having those progressing logs.

Screenshot 2020-10-30 at 11 22 54

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants