-
-
Notifications
You must be signed in to change notification settings - Fork 33k
Closed
Labels
3.13bugs and security fixesbugs and security fixes3.14bugs and security fixesbugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-replRelated to the interactive shellRelated to the interactive shelltype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Bug report
Bug description:
We noticed a failure of our Vim test suite on the Github Windows runners, when it was updated from python3.12 to python3.13.
Vim basically does run in a terminal exit(123)
and expects the return code to be 123, however, since python3.13 the return code seems to be 1.
Note this works find on the linux jobs, just on Windows this does not work correctly. Also note, python3 -c 'exit(123)' seems to work correctly, only when using an interactive session it doesn't seem to work right.
related:
- Github Windows runner update breaks the test suite. vim/vim#16546 (see in particular this comment)
- Updated Github Windows 2022 runners break Vims test suite actions/runner-images#11512
exit(123)
CPython versions tested on:
3.13
Operating systems tested on:
Windows
Linked PRs
Metadata
Metadata
Assignees
Labels
3.13bugs and security fixesbugs and security fixes3.14bugs and security fixesbugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-replRelated to the interactive shellRelated to the interactive shelltype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error