mirror of
https://github.com/zeek/zeek.git
synced 2025-10-06 16:48:19 +00:00
3d87400f1d
The sequence of - adding a new file - deleting an existing one - waiting for Zeek to notice the addition - re-adding the pre-existing file was prone to a race: it could happen that Zeek's directory observation would see the new file in one round, and by the time the next round happens the removal and re-addition had already happened, thus missing the change and failing the test. This avoids the race by placing the removal of the existing file before the addition of the new one, ensuring that when Zeek notices the addition (and pushes the test to the next round), it has also seen the removal, so the re-addition cannot get lost. |
||
|---|---|---|
| .. | ||
| active-http.test | ||
| addrs.test | ||
| conn-ids.test | ||
| decompose_uri.zeek | ||
| dir.test | ||
| directions-and-hosts.test | ||
| email.zeek | ||
| exec.test | ||
| files.test | ||
| hash_hrw.zeek | ||
| json.test | ||
| numbers.test | ||
| paths.test | ||
| pattern.test | ||
| queue.test | ||
| site.test | ||
| strings.test | ||
| thresholds.test | ||
| urls.test | ||