ocurrent / ocurrent/docker-base-images
Windows base image builders failing with `Job failed: Disconnected: Switch turned off`
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 32
- Forks
- 22
- Avg merge
- 6h 48m
- Merged PRs (30d)
- 2
Description
E.g., in https://images.ci.ocaml.org/job/2024-07-30/015349-win-version-45143d and https://images.ci.ocaml.org/job/2024-07-29/151428-win-version-e4a100
2024-07-30 01:53.49: New job: Windows version
2024-07-30 01:53.49: Waiting for resource in pool OCluster
2024-07-30 01:53.49: Waiting for worker…
2024-07-30 01:53.49: Got resource from pool OCluster
Building on ltsc2019-3
Sending build context to Docker daemon 2.048kB
Step 1/2 : FROM mcr.microsoft.com/windows:ltsc2019
ltsc2019: Pulling from windows
Digest: sha256:d73b1d59869965123148077be9cb06df4e706aea55bbc0dc5e28f0ce35b52676
Status: Image is up to date for mcr.microsoft.com/windows:ltsc2019
---> 6df6740e93d4
Step 2/2 : RUN for /f "tokens=4 delims=[] " %a in ('ver') do echo 1722304429& echo OuTPuT& echo %a& echo OuTPuT
---> Running in 46b679f1c40e
C:\>echo 1722304429 & echo OuTPuT & echo 10.0.17763.6054 & echo OuTPuT
1722304429
OuTPuT
10.0.17763.6054
OuTPuT
Removing intermediate container 46b679f1c40e
---> 84e1e835ca75
Successfully built 84e1e835ca75
Job succeeded
2024-07-30 01:58.50: Job failed: Disconnected: Switch turned off
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the two linked Windows job logs and compare the successful Docker build with the later “Disconnected: Switch turned off” failure. Trace the builder or worker configuration responsible for the OCluster job and identify where the disconnect is reported. Done means Windows base image jobs complete without this post-build failure and the relevant regression is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100