Flaky test: `Job for ssh.service failed because the control process exited with error code.`
- Dominant language
- Go
- Stars
- 21.9k
- Forks
- 957
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 53
Description
```
LIMA| Executing /mnt/lima-cidata/boot/11-colorterm-environment.sh
+ [ ! -e /etc/ssh/sshd_config ]
+ grep -q COLORTERM /etc/ssh/sshd_config
+ sed -i s/^AcceptEnv LANG LC_\*$/AcceptEnv COLORTERM LANG LC_*/ /etc/ssh/sshd_config
+ [ -f /sbin/openrc-run ]
+ command -v systemctl
+ systemctl -q is-active ssh
+ systemctl reload ssh
Job for ssh.service failed because the control process exited with error code.
See "systemctl status ssh.service" and "journalctl -xeu ssh.service" for details.
LIMA| WARNING: Failed to execute /mnt/lima-cidata/boot/11-colorterm-environment.sh
```
https://github.com/lima-vm/lima/actions/runs/5043312199/jobs/9049310878
Contributor guide
Research direction
Start with /mnt/lima-cidata/boot/11-colorterm-environment.sh and inspect the failed GitHub Actions job linked in the issue, focusing on the ssh.service reload and the displayed systemctl error. Determine the cause of the intermittent failure and verify that the affected action no longer reports this boot-script failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100