-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Windows error logs directed to stderr #39139
Windows error logs directed to stderr #39139
Conversation
For consistency, this should also be done on macOS and Linux if not done already. |
I'm not sure to understand the rationale, what difference does it make on Windows? Doesn't it print stdout and stderr to the same |
yeah, it'll print everything on the console unless redirecting stdout or stderr to another stream like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good feature, but we need to harmonize this behavior with Linux and macOS (if not done already).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes it consistent with Unix systems:
godot/drivers/unix/os_unix.cpp
Lines 562 to 579 in df62d9f
switch (p_type) { | |
case ERR_WARNING: | |
logf_error("%sWARNING:%s %s\n", yellow_bold, yellow, err_details); | |
logf_error("%s at: %s (%s:%i)%s\n", gray, p_function, p_file, p_line, reset); | |
break; | |
case ERR_SCRIPT: | |
logf_error("%sSCRIPT ERROR:%s %s\n", magenta_bold, magenta, err_details); | |
logf_error("%s at: %s (%s:%i)%s\n", gray, p_function, p_file, p_line, reset); | |
break; | |
case ERR_SHADER: | |
logf_error("%sSHADER ERROR:%s %s\n", cyan_bold, cyan, err_details); | |
logf_error("%s at: %s (%s:%i)%s\n", gray, p_function, p_file, p_line, reset); | |
break; | |
case ERR_ERROR: | |
default: | |
logf_error("%sERROR:%s %s\n", red_bold, red, err_details); | |
logf_error("%s at: %s (%s:%i)%s\n", gray, p_function, p_file, p_line, reset); | |
break; |
Thanks! |
Cherry-picked for 3.4. |
it makes more harder to run tests with those error logs