Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Added testcase which checks for SMT state when new cpu's added dynamically #2730

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added testcase which checks for SMT state when new cpu's added dynamically #2730

wants to merge 1 commit into from

Conversation

shirishaganta1
Copy link
Contributor

Added a check to make sure the smtstate is correct after dynamically adding a new CPU.

@shirishaganta1
Added testcase which checks for SMT state when new cpu's added dynami…
91acb84 
…cally

Added a check to make sure the smtstate is correct after
dynamically adding a new CPU.

Signed-off-by: Shirisha Ganta <shirisha@linux.ibm.com>
@shirishaganta1
Copy link
Contributor Author

JOB ID : 381e00bb01b92a322aab7a98dc8f5eb624087bce
JOB LOG : /home/avocado-fvt-wrapper/results/job-2023-11-06T10.09-381e00b/job.log
(1/1) test.py:dlpar_smtcheck.test: STARTED
(1/1) test.py:dlpar_smtcheck.test: FAIL: newly added CPU is not running at the correct SMT level 1 (5.70 s)
RESULTS : PASS 0 | ERROR 0 | FAIL 1 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB HTML : /home/avocado-fvt-wrapper/results/job-2023-11-06T10.09-381e00b/results.html
JOB TIME : 27.43 s

Test summary:
test.py:dlpar_smtcheck.test: FAIL
full.log

@PraveenPenguin
Copy link
Member

@shirishaganta1 can you please consider ras/smtest.py to add this test case

@abdhaleegit
Copy link
Collaborator

@shirishaganta1 as we discuss in the last community guidelines sessions we already have smt and cpu dlpar test .. we can still run this combination using cfg instead of adding a new test

@PraveenPenguin
Copy link
Member

@shirishaganta1 any update here

@shirishaganta1
Copy link
Contributor Author

@shirishaganta1 any update here

Will look into it and update

@Naresh-ibm
Copy link
Collaborator

@shirishaganta1 any update?

@shirishaganta1
Copy link
Contributor Author

@shirishaganta1 as we discuss in the last community guidelines sessions we already have smt and cpu dlpar test .. we can still run this combination using cfg instead of adding a new test

The above smt/cpu testcase are not validating the smt/cpustate values as per the set config
This test case involves changing the SMT configuration, performing a DLPAR operation, and then validating whether the SMT settings remain consistent before and after the DLPAR operation.

@PraveenPenguin
Copy link
Member

@shirishaganta1 as we discuss in the last community guidelines sessions we already have smt and cpu dlpar test .. we can still run this combination using cfg instead of adding a new test

The above smt/cpu testcase are not validating the smt/cpustate values as per the set config This test case involves changing the SMT configuration, performing a DLPAR operation, and then validating whether the SMT settings remain consistent before and after the DLPAR operation.

@shirishaganta1 can you please move this as scenario in ras/smtest.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@shirishaganta1 @PraveenPenguin @abdhaleegit @Naresh-ibm