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.

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

Added fix to run every if/else statements in case of failure. #2902

Merged

Conversation

Krishan-Saraswat
Copy link
Contributor

Lparstat test have multiple if/else statements to check for different options, if one fails then test execution stops, added fix to execute every statement and check failure at the end.


We can see multiple Fail conditions getting executed.

[root@ltcrain8oj-lp7 ras]# avocado run --max-parallel-tasks=1 ras_ppcutils.py:test_lparstat
JOB ID : 690e2d43f40fde6cc7cb8216971d1a21e1dfcd77
JOB LOG : /root/avocado-fvt-wrapper/results/job-2024-10-03T22.44-690e2d4/job.log
(1/1) ras_ppcutils.py:RASToolsPpcutils.test_lparstat: STARTED
(1/1) ras_ppcutils.py:RASToolsPpcutils.test_lparstat: FAIL: ['Normalised busy plus idle value does not match with Frequency percentage', 'number of physical processors consumed are not displaying correct'] (11.28 s)
RESULTS : PASS 0 | ERROR 0 | FAIL 1 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB HTML : /root/avocado-fvt-wrapper/results/job-2024-10-03T22.44-690e2d4/results.html
JOB TIME : 26.63 s

Test summary:
1-ras_ppcutils.py:RASToolsPpcutils.test_lparstat: FAIL

Lparstat test have multiple if/else statements to check for
different options, if one fails then test execution stops,
added fix to execute every statement and check failure at the end.

Signed-off-by: Krishan Gopal Saraswat <[email protected]>
Copy link
Member

@PraveenPenguin PraveenPenguin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PraveenPenguin PraveenPenguin merged commit 1519656 into avocado-framework-tests:master Oct 7, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants