-
Notifications
You must be signed in to change notification settings - Fork 80
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
Add unit test showing high CPU utilization when attempting to get /120 subnet #137
Conversation
cfff801
to
acf52be
Compare
@@ -0,0 +1,5 @@ | |||
--- | |||
minor_changes: |
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.
minor_changes: | |
doc_changes: |
Unable to freeze job graph: Job network-ee-unit-tests depends on network-ee-build-container-image which was not run. |
89cf854
to
f016252
Compare
Unable to freeze job graph: Job network-ee-unit-tests depends on network-ee-build-container-image which was not run. |
recheck |
Build failed.
|
This at the very least needs a rebase, but the changelog update is also correct- no code is changing here outside of tests, so this is at best a |
Closing as above changes has already been added from a different PR |
SUMMARY
Two bugs are exposed by the unit tests, one in
netaddr
and one inansible.utils
. The"2600:1f1c:1b3:8f00::/56" | ipsubnet(120, 0)
unit test causes theipsubnet
filter to attempt to create 18446744073709551616 subnets, this never returns.ISSUE TYPE
COMPONENT NAME
ipsubnet filter
ADDITIONAL INFORMATION