-
Notifications
You must be signed in to change notification settings - Fork 12
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
STP #867
Draft
wkz
wants to merge
10
commits into
main
Choose a base branch
from
stp
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
troglobit
approved these changes
Dec 17, 2024
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, really nice work on this! Only a minor comment from me.
Signed-off-by: Joachim Wiberg <[email protected]>
- Helper to get a set of nodes, using a formatted path - Helper to get a single node, using a formatted path
This convention is now well established, so it seems silly to have to repeat it in every test.
The somewhat clumsy construct of resolving a logical port name to its physical counterpart has been with us from Infamy's inception: _, physical_port = env.ltop.xlate(logical_node, logical_port) This is needlessly verbose. Since devices already have access to the mappings which applies to it, make them easy to access: target = env.attach("target") # Get physical port names via the subscript operator target["data0"]
Using `sys.argv[0]` does not quite achieve the effect we want, namely that any (test-case, $PYTHONHASHSEED) tuple should always default to the same transport. For example, the following two examples should always use the same transport: $ make PYTHONHASHSEED=1337 test-sh infamy0:test$ ./case/ietf_system/hostname/test.py $ make PYTHONHASHSEED=1337 test-sh infamy0:test$ cd ./case/ietf_system/hostname infamy0:hostname$ ./test.py But, since their argv[0]'s are different, they don't. Therefore use the _last two components_ of argv[0]'s full path instead. This should: - Spread the allocation over an entire suite run, since the penultimate component is usually the test name. - Keep the allocation stable when test code is modified (which is common during debugging of failing tests) - Avoid instabilities stemming from the local storage location (i.e., home directory names etc.)
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.
Description
Playing around with
mstpd
Checklist
Tick relevant boxes, this PR is-a or has-a: