Opened at 2018-03-29T20:50:46Z
Last modified at 2021-03-30T18:40:19Z
#2914 new defect
test_magic_folder timeout on windows
Reported by: | warner | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | soon |
Component: | code | Version: | 1.12.1 |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
Our Appveyor CI system shows test_magic_folder.RealTest.test_batched_process hitting a timeout error ("test still running after 120 seconds") on windows, on maybe one out of every 5 builds.
I've reconfigured .appveyor.yml to include the trial test.log as an artifact, so we can see if it's throwing an error, or if it's just taking too long and sometimes exceeds the limit. Then we can either be lazy and increase the timeout, or actually make it run faster, or if it's an intermittent deadlock then fix it for real.
Change History (4)
comment:1 Changed at 2018-03-29T21:05:19Z by warner
comment:2 Changed at 2018-03-30T02:25:04Z by warner
I got some logs: when it passes on appveyor, it only takes about 400ms, just like on linux. I'll wait until we get a failing build to see what's happening there.
comment:3 Changed at 2020-06-30T14:45:13Z by exarkun
- Milestone changed from 1.13.0 to 1.15.0
Moving open issues out of closed milestones.
comment:4 Changed at 2021-03-30T18:40:19Z by meejah
- Milestone changed from 1.15.0 to soon
Ticket retargeted after milestone closed
This test takes 0.441 seconds on our linux buildbot ("xenial"), and the longest magic-folder test takes 2.3 seconds (test_magic_folder.RealTestAliceBob.test_alice_bob), so I'm guessing this is an intermittent deadlock, rather than a very slow test that would complete if we just increased the timeout somewhat. I'm not sure why we've only seen it on appveyor, though; it suggests that there's something windows-specific about the bug.