text: Title: Export CI images to S3
  Body: Create a TravisCI `after_failure` script that uploads actual images and diffs to S3 so we can diagnose TravisCI failures. 
  
  ### Proposal/Issue
  
  It seems like every time we push a commit to GitHub the TravisCI tests fail, even if they were working locally. Right now we're messing with the tolerances but with no real insight into what the key differences are in the CI environment vs locally. To better help us address these issues we should push the failed test images and their diffs to S3 for further inspection. 
  
  Issues to consider:
  
  1. Limit the number of uploads to S3: only upload failed test actual and diff images 
  2. Organize by test/commit - multiple travis tests might be running at the same time 
  3. Log where the images were uploaded and stored 
  4. Long run clean up of these images over time 
  
  ### Addendum 
  
  Also, export AppVeyor images using artifacts. 