Skip to content
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

Scan stability - Retry on failure or On fail, record last known good? #22

Open
cybershambles opened this issue May 6, 2015 · 0 comments

Comments

@cybershambles
Copy link

"name": "Crikey", "url": "www.crikey.com.au", "wayback": ["X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "X", "B", "X", "B", "X", "X", "X", "X", "X", "X", "B", "X", "X", "B", "B", "B", "X", "B", "X", "B", "B"],

Because we're running a lot of scans - I've noticed lots of X's in the daily scans.

  1. Retry the failures until the scan is successful
    or
  2. If the last known score was B, but it's failed today... keep the last known as B until the next successful test which might lower the score.

Having all of these X's will cause false negatives, stopping the change updates from being notified in our twitter.

The graph on our site is looking messy because the graph keeps dropping and returning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant