ci: run lscpu at end of build #11814
Merged
Conversation
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
|
Please set the appropriate release note label. |
|
test-focus K8sDemos |
|
test-runtime |
pchaigno
reviewed
Jun 2, 2020
We have been running into cpu frequency issues in our ci, this change will allow us to check whether the build was affected by the problem. Signed-off-by: Maciej Kwiek <maciej@isovalent.com>
|
test-focus K8sDemos |
pchaigno
approved these changes
Jun 2, 2020
joestringer
reviewed
Jun 2, 2020
| @@ -133,6 +133,7 @@ pipeline { | |||
| } | |||
| post { | |||
| always { | |||
| sh 'lscpu' | |||
There was a problem hiding this comment.
I note that some lines use double-quote and others use single-quote, but seems like both are respected.
joestringer
approved these changes
Jun 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We have been running into cpu frequency issues in our ci, this change
will allow us to check whether the build was affected by the problem.