Open stitch opened 2 years ago
This happens due to timeouts during the scan on our side. Todo: point towards what exception scenarios have to be improved.
This happens due to timeouts during the scan on our side. Todo: point towards what exception scenarios have to be improved.
This is rather vague. Could you elaborate a bit on what you were thinking here?
This can be due to timeouts that are too short or the other party has a load balancer or something that causes these measurements to be unstable.
hp.com 32% dev: https://dev.internet.nl/site/hp.com/5558/ 22% dev: https://dev.internet.nl/site/hp.com/5613/ 29% prod: https://internet.nl/site/hp.com/1513014/ 32% prod: https://internet.nl/site/hp.com/1513266/
audi.nl: 60% dev: https://internet.nl/mail/audi.nl/679221/ 65% dev: https://internet.nl/mail/audi.nl/679234/ 65% prod: https://dev.internet.nl/mail/audi.nl/7981/ 60% prod: https://dev.internet.nl/mail/audi.nl/7982/
Probably solved by raising the time out and also having more log info on the tests that differ. Logging has to be sprinkled throughout the code. Timings can be adjusted in settings.