-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
lib: nrf_modem_lib: Use debug logs of expected errnos on backend write #19820
base: main
Are you sure you want to change the base?
lib: nrf_modem_lib: Use debug logs of expected errnos on backend write #19820
Conversation
I don't think we need a changelog entry for changing this log level, @divipillai? |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: fa125401484c7c046ac66e2477733d5529074d67 more detailssdk-nrf:
Github labels
List of changed files detected by CI (1)
Outputs:ToolchainVersion: 11349092be Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
b8a9edf
to
5439000
Compare
Agree, as from the description seems like an intermittent issue. |
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
LOG_ERR("trace_backend.write failed with err: %d", ret); | ||
} else { | ||
LOG_DBG("trace_backend.write returned with %d", ret); | ||
LOG_DBG("Is the backend properly connected?"); |
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.
Is there a way to pose this as a statement rather than a question? Perhaps outline possible scenarios or solutions and make it more explicit and actionable.
For example:
Please make sure that the backend is properly connected.
or something like that.
This fits more with the rest of the logs in NCS.
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.
Thanks, updated.
We use -ENOSPC and -ENOSPC to signal from the backend that there is no space in backend or it is not properly connected. This can occur from time to time and is not always an error. Though, it can be noisy in log output. This commit replaces the error logs with debug level and adds a hint that the backend should be properly connected. Signed-off-by: Eivind Jølsgard <[email protected]>
5439000
to
fa12540
Compare
We use -ENOSPC and -ENOSPC to signal from the backend that there is no space in backend or it is not properly connected. This can occur from time to time and is not always an error. Though, it can be noisy in log output. This commit replaces the error logs with debug level and adds a hint that the backend should be properly connected.