[action] [PR:16757] fix: pfc timer accuracy timestamp regex#53
Merged
auspham merged 1 commit intoAzure:202405from Feb 3, 2025
Merged
[action] [PR:16757] fix: pfc timer accuracy timestamp regex#53auspham merged 1 commit intoAzure:202405from
auspham merged 1 commit intoAzure:202405from
Conversation
<!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: Fixes # (issue) 31202914 From #16446 we are changing to use regex to capture the timestamp for pfc timer accuracy. However, the regex does not cover the scenario where date digit is 1. For example: `2025 Jan 5 00:53:14.103188 ` ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 ### Approach #### What is the motivation for this PR? Comparing between: - `2025 Jan 26 17:36:31.27789` - `2025 Feb 2 15:17:24.055182` We can see that we might need up to 2 spaces after month and the number of day digits can vary between 1 to 2. #### How did you do it? Adjust the regex so it matches for both format #### How did you verify/test it?  #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
Collaborator
Author
|
Original PR: sonic-net/sonic-mgmt#16757 |
Collaborator
Author
|
/azp run |
11 tasks
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
2 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.
Description of PR
Summary:
Fixes # (issue) 31202914
From #16446 we are changing to use regex to capture the timestamp for pfc timer accuracy. However, the regex does not cover the scenario where date digit is 1. For example:
2025 Jan 5 00:53:14.103188Type of change
Back port request
Approach
What is the motivation for this PR?
Comparing between:
2025 Jan 26 17:36:31.277892025 Feb 2 15:17:24.055182We can see that we might need up to 2 spaces after month and the number of day digits can vary between 1 to 2.
How did you do it?
Adjust the regex so it matches for both format
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation