I can easily reproduce this failure on a slow VM (cpu cap of 10% of my host cpu) and I see where it fails, but after spending a few hours debugging it I got nowhere close to an explanation or a fix. May be a race. It's definately not a click scope fault, the problem is either in scope-harness or shell plugin itself. Since I cannot focus on this problem right now, perhaps as a temporary workaround it's best to disable this test for now.
I can easily reproduce this failure on a slow VM (cpu cap of 10% of my host cpu) and I see where it fails, but after spending a few hours debugging it I got nowhere close to an explanation or a fix. May be a race. It's definately not a click scope fault, the problem is either in scope-harness or shell plugin itself. Since I cannot focus on this problem right now, perhaps as a temporary workaround it's best to disable this test for now.