Skip to content

Conversation

@prashanthswami
Copy link
Contributor

There are a few steps in our parsing logic where we skip lines that don't match the expectations of the /proc/cpuinfo node. Reduce the log level of these lines to 'debug', as these are not generally errors and are noisy on systems that have unique cpuinfo key-value pairs.

When parsing logic encounters a higher-than-expected processor number, increase the level to warning, to indicate that an error may have occurred in the parsing step.

This does not fully address #19 but resolves the underlying noise reported.

@prashanthswami
Copy link
Contributor Author

Review: @malfet

Copy link
Collaborator

@fbarchard fbarchard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks... these messages are not very interesting, so reducing it is a good idea

@prashanthswami prashanthswami force-pushed the adjust-log-level branch 3 times, most recently from cd7de52 to 9104dce Compare January 6, 2024 02:27
There are a few steps in our parsing logic where we skip lines that
don't match the expectations of the /proc/cpuinfo node. Reduce the log
level of these lines to 'debug', as these are not generally errors and
are noisy on systems that have unique cpuinfo key-value pairs.

When parsing logic encounters a higher-than-expected processor number,
increase the level to warning, to indicate that an error may have
occurred in the parsing step.
Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the updates, LGTM

@malfet malfet merged commit 0502736 into pytorch:main Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants