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

Revert to err logging instead of LOGS_DEFAULT macro #22720

Merged

Conversation

ivberg
Copy link
Contributor

@ivberg ivberg commented Nov 5, 2024

Revert to err logging instead of LOGS_DEFAULT macro due to issue seen during testing. "onnxruntime::logging::LoggingManager::DefaultLogger Attempt to use DefaultLogger but none has been registered."

Description

Revert part of PR suggestion to prevent crash for scenario seen in #22699. Previously we had tested w/o this macro

Motivation and Context

Previous PR #22699 it was suggested to use LOGS_DEFAULT() but that does not work during early init. Safer to use std::cerr instead like the original PR had it.

… during testing. "onnxruntime::logging::LoggingManager::DefaultLogger Attempt to use DefaultLogger but none has been registered."
@ivberg ivberg requested a review from skottmckay November 5, 2024 00:45
@ivberg ivberg merged commit db72096 into main Nov 5, 2024
89 of 91 checks passed
@ivberg ivberg deleted the user/ivberg/FixETW_Running_Under_LowIntegrityLevel_Process_2 branch November 5, 2024 17:51
ishwar-raut1 pushed a commit to ishwar-raut1/onnxruntime that referenced this pull request Nov 19, 2024
Revert to err logging instead of LOGS_DEFAULT macro due to issue seen
during testing. "onnxruntime::logging::LoggingManager::DefaultLogger
Attempt to use DefaultLogger but none has been registered."

### Description
Revert part of PR suggestion to prevent crash for scenario seen in
microsoft#22699. Previously we had tested w/o this macro

### Motivation and Context
Previous PR microsoft#22699 it was suggested to use LOGS_DEFAULT() but that does
not work during early init. Safer to use std::cerr instead like the
original PR had it.
ankitm3k pushed a commit to intel/onnxruntime that referenced this pull request Dec 11, 2024
Revert to err logging instead of LOGS_DEFAULT macro due to issue seen
during testing. "onnxruntime::logging::LoggingManager::DefaultLogger
Attempt to use DefaultLogger but none has been registered."

### Description
Revert part of PR suggestion to prevent crash for scenario seen in
microsoft#22699. Previously we had tested w/o this macro

### Motivation and Context
Previous PR microsoft#22699 it was suggested to use LOGS_DEFAULT() but that does
not work during early init. Safer to use std::cerr instead like the
original PR had it.
ankitm3k pushed a commit to intel/onnxruntime that referenced this pull request Dec 11, 2024
Revert to err logging instead of LOGS_DEFAULT macro due to issue seen
during testing. "onnxruntime::logging::LoggingManager::DefaultLogger
Attempt to use DefaultLogger but none has been registered."

### Description
Revert part of PR suggestion to prevent crash for scenario seen in
microsoft#22699. Previously we had tested w/o this macro

### Motivation and Context
Previous PR microsoft#22699 it was suggested to use LOGS_DEFAULT() but that does
not work during early init. Safer to use std::cerr instead like the
original PR had it.
ankitm3k pushed a commit to intel/onnxruntime that referenced this pull request Dec 11, 2024
Revert to err logging instead of LOGS_DEFAULT macro due to issue seen
during testing. "onnxruntime::logging::LoggingManager::DefaultLogger
Attempt to use DefaultLogger but none has been registered."

### Description
Revert part of PR suggestion to prevent crash for scenario seen in
microsoft#22699. Previously we had tested w/o this macro

### Motivation and Context
Previous PR microsoft#22699 it was suggested to use LOGS_DEFAULT() but that does
not work during early init. Safer to use std::cerr instead like the
original PR had it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants