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.

Sign up for GitHub

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

Jump to bottom

printLogsToConsole: 'never' not respected by enableExtendedCollector: true when includeSuccessfulHookLogs is also true #241

Closed
gbutt-tr opened this issue Apr 25, 2024 · 1 comment
Closed

printLogsToConsole: 'never' not respected by enableExtendedCollector: true when includeSuccessfulHookLogs is also true #241

gbutt-tr opened this issue Apr 25, 2024 · 1 comment
Labels
improvement

Comments

@gbutt-tr
Copy link

When printLogsToConsole is set to 'never', enableExtendedCollector is set to true, and includeSuccessfulHookLogs is set to true, then before-all logs are still printed to the console.

Disabling includeSuccessfulHookLogs seems to fix this without any loss of file log data.

It is possible that these logs get output due to a hostname change that happens in the before hook, which causes the cypress spec to restart.

"cypress-terminal-report": "^6.0.1"
"cypress": "^13.6.4"
archfz added a commit that referenced this issue May 1, 2024
@archfz
#241: Ensure print logs to console on never works always.
2a5d077
@archfz
Copy link
Owner

archfz commented May 1, 2024

Fixed in 6.0.2

@archfz archfz closed this as completed May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@archfz @gbutt-tr