Issue running in history mode - base files do not get replaced #600
Comments
|
My understanding is that history creates a "baseline," and each run of latest is compared against this baseline. It's not a rolling diff, but a "identify when it broke, and again when it recovered." To do a rolling diff (showing what changed since the last run), you'd want to replace your history images with the prior run's snapshots before running latest again. I believe running either copy_old_shots or copy_base_images (not sure which) before your next run of latest will generate what you want. The code is at https://github.com/BBC-News/wraith/blob/master/lib/wraith/folder.rb if you want to see the inner workings. |
|
Try this: (required for history mode, otherwise optional) The directory that your base screenshots will be stored in.history_dir: 'history/shots_base' (required) The directory that your latest screenshots will be stored indirectory: 'history/shots' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am having difficulty running wraith in history mode correctly as the base files do not seem to be getting replaced with the latest files.
1 - I set up wraith
2 - I update the history yaml file
3 - I set up the image folders
4 - I ran wraith history to create base images
5 - I ran wraith latest to create new images and compared
Up to step 5 everything looks correct.
6 - I then run wraith latest again, what I observe is it clears out my latest images and the base images remain as they are. So what this means is on the latest run its still creating new files and comparing then with the existing base files rather than updating them so my results are exactly the same each time.
Please can someone tell me if this is an issue or whether I am doing something wrong in the config etc?
Reporting a problem? Please describe the issue above, and complete the following checklist so that we can help you more quickly.
Issue checklist:
I have validated my config file against YAML Validator to make sure it is valid YAML.
I have run the
wraith infocommand and pasted the output below:verbose: trueto my config) and pasted the output below:The text was updated successfully, but these errors were encountered: