-
Notifications
You must be signed in to change notification settings - Fork 300
Rebase hash #2162
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
Merged
Merged
Rebase hash #2162
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
cdd14bd
Use SHA1 of image file for check_graphic
marqh 8b7818b
Initial json repo of image hashes.
bjlittle e2801ac
graphic_hash logic
marqh 152ce4e
test image resolution
marqh 04e487d
Indented image json store.
bjlittle 1ef41b1
error reporting
marqh b884ad6
Deal with multiple image hashes.
bjlittle 3abe8e5
clean up check_graphic code
marqh fb183e2
new sha1 sums for mpl1.3
marqh 4d4398b
ValueError on no entry in json
marqh a36466d
check_graphic tidying
marqh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
@marqh You've changed the logic here from the original, which I kinda disagree with.
As it now stands any developer who adds a new graphics test, has to manually craft the changes to the
imagerepo.jsonand manage the hash renaming of thepng... this doesn't scale very well.I'll propose an alternative approach on your
rebase_hashbranch as a PR that (I believe) improves this work-flow. We can discuss that further there ... so hang tight for that.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.
@marqh Okay, I'm working on that
rebase_hashbranch PR ... in-bound soon, thanksThere 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 understand your concerns and I am keen to see a work flow for updating lots of images
however, in your previous implementation, the effect was that tests with no checksum to check would pass, for developers and for travis.
This is a more serious problem. I simplified the logic to allow me to fix this problem, which I deemed critical.
If you are working with respect to this branch, please make sure that an implementation does not allow tests to pass where there is no entry in the imagerepo or where the image checksum comparison fails.
any tooling to help updating must (imho) deal with these as test failures, then help the developer fix them, not enable them to pass
I hope that point of view is clear and coherent
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.
@marqh I completely understand your concerns, and I think that there is a suitable compromise to be had here to meet all our needs.
I don't think it would be wise of me to mix this into this PR - let's do that in a separate PR 👍