-
Notifications
You must be signed in to change notification settings - Fork 1
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
CRAYSAT-1953: Functional tests for sat nid2xname
#673
Conversation
20835c9
to
7994c61
Compare
Output test on rocket
Output test on drax
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @annapoorna-s-alt looks great though I gave it a test on Gamora and its failed on two of the tests converting xnames to nids, the issue seems to be that there are a bunch of prepended zeroes on the nid name. Here is the output from the testing https://gist.github.com/ethanholen-hpe/80081aed9bca7829cffc74a0c364be41
Not sure if this is an issue with the state of gamora or with the test but let me know if you need any help tracking this down.
Thanks @ethanholen-hpe for checking on Gamora too. There were actually few nodes for which the NIDs from cray command is just a single digit. But actually we need to prepend the zeroes on the nid name to make at least 6 digits. I checked on the system too- https://area.hpc.amslabs.hpecorp.net/cgi-bin/hardware.cgi?system=gamora Adding here an ex for single digit NID:
I addressed it and tested on Gamora too. Please verify
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great tested on both gamora and mug 👍🏻
a151625
to
3932ba3
Compare
Summary and Scope
Add automated test cases for
sat nid2xname
andsat xname2nid
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
List the environments in which these changes were tested.
Tested on:
Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?
Risks and Mitigations
Low risk since we added only automated test cases to verify functionality of
sat nid2xname
andsat xname2nid
Pull Request Checklist