Repository navigation
Web Cmdlets test intermittently fail with WebListener timeout #6001
Description
Activity
I have seen this before a few times, but I can never reproduce it when I try. The only way I see we can get to the bottom if it is to add super verbose failure messages and then reviewing the output when it does fail.
Maybe CI very slow and we should wait more? What is timeout for the start?
15 seconds
We could increase the timeout and get anything useful to
$initStatus.Also we check a real time with Get-Date. But if VM sleeps long time the real time loses a value. I think it is more reliably count 100ms intervals in the cycle.
But if VM sleeps long time the real time loses a value.
what?
as for $initstatus..
$Job | Stop-Job -PassThru | Receive-Jobshould b dumping anything that would be in it in the catch block.But if VM sleeps long time the real time loses a value.
what?We get
$timeOut = (get-date).AddSeconds($initTimeoutSeconds). Then VM sleeps 30 seconds. Then it run and we check(get-date) -lt $timeOut)- we already expire although we worked only 100 ms!Then VM sleep 30 seconds.
what?
I mean, CI farm can be very busy and VM can be put in a pause.
so something like
$sleepMilliseconds = 100 $sleepCount = $initTimeoutSeconds * 1000 / $sleepMilliseconds do { Start-Sleep -Milliseconds $sleepMilliseconds $initStatus = $Job.ChildJobs[0].Output | Out-String $isRunning = $initStatus -match $initCompleteMessage $sleepCount-- } while (-not $isRunning -and $sleepCount -gt 0)
Reacted by IlyaYes. If CI VM really slow-slow this help.
I've seen this a few times.
Steps to reproduce
Run Windows CI Tests
Expected behavior
No failures
Actual behavior
https://ci.appveyor.com/project/PowerShell/powershell/build/6.0.0-7706#L2212
Environment data