-
Notifications
You must be signed in to change notification settings - Fork 19
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
Fixed JsonCompare() function and switched to using it for json_test #217
Fixed JsonCompare() function and switched to using it for json_test #217
Conversation
There was an error running your pipeline, see logs for details. |
0986913
to
51859a3
Compare
I added a negative test and debug logging to see how that might look in case someone wants to debug WHY JsonCompare() found two json's to not be equal
The output is a bit "backwards" by noting the inner-most problem and then the elements outside of that in sequence to furthest out last. |
ab85141
to
994be5a
Compare
There was an error running your pipeline, see logs for details. |
994be5a
to
a0226b1
Compare
There was an error running your pipeline, see logs for details. |
a0226b1
to
06610c8
Compare
There was an error running your pipeline, see logs for details. |
06610c8
to
2129690
Compare
There was an error running your pipeline, see logs for details. |
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.
Very nice fixes and improvements! Thanks!
2129690
to
89a8944
Compare
There was an error running your pipeline, see logs for details. |
89a8944
to
5ceb31c
Compare
There was an error running your pipeline, see logs for details. |
@cf-bottom jenkins, please |
Sure, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/10628/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-10628/ |
Also added DEBUG logging for details on why JsonCompare() found two json elements to not be equal. Ticket: ENT-11450 Changelog: none
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.
I'd do two things differently, but it's definitely good to go as is.
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.
LGTM, but take a look at Jenkins test failures before merging.
dc30808
5ceb31c
to
dc30808
Compare
There was an error running your pipeline, see logs for details. |
@cf-bottom jenkins |
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.
ACK
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/10629/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-10629/ |
One was a 52 exit code during cfbs test which is likely "known" and should already be addressed so maybe the fix for https://northerntech.atlassian.net/browse/ENT-11526 (apache graceful restart) didn't quite fix it. The other is maybe new, I have logged a ticket: https://northerntech.atlassian.net/browse/ENT-11565 |
PR to pull this change (and any others up to this merge) into core cfengine/core#5483 |
Ticket: ENT-11450
Changelog: none