ZeroLog
Private preview
EN DE

Security

22 November: a steadier release check for security scans

Behind the scenes: one of our release checks for security scans failed at random when the test machine was busy, and held back updates this morning. It now measures the right thing. Nothing changes for you.

User impact: Background

Nobody directly: this fixes one of our release checks for security scans, not the scans themselves. Updates are held back less often. No action needed.

What the check is for. When you start a security scan, ZeroLog answers right away and does the slower work, such as signing in to the site under test, in the background. One of our release checks makes sure it stays that way: starting a scan must not wait for anything slow.

What went wrong. The check used a stopwatch that also counted the very first request after the test server had started. When many checks ran at the same time, that first request alone could take longer than the limit, so the check failed although nothing was wrong. Two releases were held back this morning.

What changed. The check now warms up the server first and then measures only the start of the scan: how much computing time it uses, and separately that it does not wait for a sign-in. A real slowdown still stops a release; a busy test machine no longer does.

No action is needed.

Back to Newsroom