Skip to content

Conversation

@ulysses4ever
Copy link
Collaborator

I wanna see if this is still needed.

The failure looks like this:

Run git config --global protocol.file.allow always
error: could not lock config file C:/msys64/home/runneradmin/.gitconfig: No such file or directory
Error: Process completed with exit code 255.

e.g. https://github.com/haskell/cabal/actions/runs/16415578333/job/46397611829


Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@ulysses4ever
Copy link
Collaborator Author

after all validate tests were smooshed into one github action step, I am positively unable to read the logs. Is anyone able to point me to the actual error message?

@geekosaur
Copy link
Collaborator

I'm confused, when did this change you mentioned happen? The only one I remember added folding output sections.

@ulysses4ever
Copy link
Collaborator Author

that one, yes

@ulysses4ever
Copy link
Collaborator Author

I don't understand where the failure is but logically, this workaround seems to be effective still. Closing…

@geekosaur
Copy link
Collaborator

Perhaps we should only skip it on Windows?

@ulysses4ever
Copy link
Collaborator Author

Good point! I don't currently have time to try it 😕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants