| Bug #34894 | falcon_record_cache_memory_leak2.test time outs on Pushbuild Windows | ||
|---|---|---|---|
| Submitted: | 27 Feb 2008 16:43 | Modified: | 25 Sep 2008 19:48 |
| Reporter: | Hakan Küçükyılmaz | Email Updates: | |
| Status: | Can't repeat | ||
| Category: | Server: Falcon | Severity: | S3 (Non-critical) |
| Version: | 6.0 | OS: | Microsoft Windows |
| Assigned to: | Christopher Powers | Target Version: | |
| Tags: | test failure, pushbuild | ||
| Triage: | D4 (Minor) / R3 (Medium) / E3 (Medium) | ||
[27 Feb 2008 16:43]
Hakan Küçükyılmaz
[27 Feb 2008 21:02]
Kevin Lewis
Vlad, There is a question here as to why pushbuild is timing out. Is the virtual machine overloaded? Or is there something in Falcon that hits a 50 second timeout a few times or maybe even a hang. Since this happens on Windows pushbuild only, I am assigning to you to try to reproduce any problem within Falcon. If the problem is definitely the test environment, maybe you can suggest a workaround.
[25 Sep 2008 19:48]
Christopher Powers
falcon_record_cache_memory_leak2 passes on all Windows pushbuild servers.
