You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 13, 2023. It is now read-only.
c.Skip("Temporarily disabled on RS5 17743+ builds due to platform bug")
547
-
548
-
// This is being tracked internally. @jhowardmsft. Summary of failure
549
-
// from an email in early July 2018 below:
550
-
//
551
-
// Platform regression. In cmd.exe by the look of it. I can repro
552
-
// it outside of CI. It fails the same on 17681, 17676 and even as
553
-
// far back as 17663, over a month old. From investigating, I can see
554
-
// what's happening in the container, but not the reason. The test
555
-
// starts a long-running container based on the Windows busybox image.
556
-
// It then adds another process (docker exec) to that container to
557
-
// sleep. It loops waiting for two instances of busybox.exe running,
558
-
// and cmd.exe to quit. What's actually happening is that the second
559
-
// exec hangs indefinitely, and from docker top, I can see
560
-
// "OpenWith.exe" running.
561
-
562
-
//Manual repro would be
563
-
//# Start the first long-running container
564
-
//docker run --rm -d --name test busybox sleep 300
565
-
566
-
//# In another window, docker top test. There should be a single instance of busybox.exe running
567
-
//# In a third window, docker exec test cmd /c start sleep 10 NOTE THIS HANGS UNTIL 5 MIN TIMEOUT
568
-
//# In the second window, run docker top test. Note that OpenWith.exe is running, one cmd.exe and only one busybox. I would expect no "OpenWith" and two busybox.exe's.
0 commit comments