Where did CONDA go?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with the linked workflow at .github/workflows/ci_workflows.yml line 107 and compare the failing run with the earlier successful run linked in the issue. The report says $CONDA no longer points to miniconda and shows /bin/conda: No such file or directory; determine where the runner environment or workflow behavior changed. Done means identifying why the path is missing and confirming the expected conda command works.
Written by the indexing model from the issue text.
Description
Describe the bug
$CONDA is supposed to point to miniconda in GHA. But it stopped working. Where did it go?
/bin/conda: No such file or directory
To Reproduce
https://github.com/ejeschke/ginga/actions/runs/42638175618/job/129231810312
from
Expected behavior
https://github.com/ejeschke/ginga/actions/runs/40318986346/job/121558748696
Runner Version and Platform
Version of your runner?
OS of the machine running the runner? OSX/Windows/Linux/...
What's not working?
Please include error messages and screenshots.
Job Log Output
If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.
Runner and Worker's Diagnostic Logs
If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.
- Dominant language
- C#
- Stars
- 6.4k
- Forks
- 1.5k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 36
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from actions/runner
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
actions/runner#4820 · 3 comments ·
Maintainers usually reply within 1 day
-
Workflow schema omits documented code-quality and copilot-requests permissionsPossibly taken @localzet claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Runner crashes at InitializeSecretMasker on machines with Thai (th-TH) culture — culture-sensitive LastIndexOf in PowerShellPreAmpersandEscapePossibly taken @CloudNinjaDev claimed this 47 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Broker retry logs an ERR stack trace and a phantom backoff on every job completion (listener's own cancellation treated as a request failure)Possibly taken @nitrobass24 claimed this 87 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 71/100
Maintainers usually reply within 1 day
-
bug debugger flaky small
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[BUG] MyAnonaMouse search turns a curly apostrophe into a space, so titles with ’ are never foundOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
About screenOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
GDMTT/JiraTaskBar#45 · 2 comments ·
Maintainers usually reply within 1 day