[202511] ignore SCD kernel warning about I2C communication ack errors (#21959)#22532
Merged
vmittal-msft merged 1 commit intosonic-net:202511from Feb 23, 2026
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: xuliping <xuliping@microsoft.com>
lipxu
force-pushed
the
20260223_public202511_kernelErr
branch
from
4830140 to
a620580
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
12 tasks
vmittal-msft
approved these changes
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the motivation for this PR?
In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors.
How did you do it?
It's a warning message, should not be failed in loganalyzer, ignore these messages.
How did you verify/test it?
https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation