Repository navigation
iOS testbed does not correctly handle test arguments with spaces #141442
Copy link
Copy link
Closed
Labels
3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixes3.15bugs and security fixesbugs and security fixesOS-iostype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixes3.15bugs and security fixesbugs and security fixes
on Nov 12, 2025 This problem was introduced as part of #138018; that change introduced the use of the xctestplan, but it wasn't until I tried to run NumPy's test suite (which needs a
pytest -m 'not slow'configuration) that the problem became apparent.- added 4 commits that reference this issue
on Feb 3, 2026 - added 3 commits that reference this issue
on Jun 12, 2026
Metadata
Metadata
Assignees
Labels
3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixes3.15bugs and security fixesbugs and security fixesOS-iostype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Bug report
Bug description:
The iOS testbed can be given arguments to pass to the test suite - for example:
The arguments are then written into a test plan, and used to start the test suite.
The testbed runner correctly parses the command line arguments, and writes them into the test plan. However, even though Xcode's xctestplan format is a JSON document, and arguments are specified as an array, and
arg 3in the previous example is passed as a single quoted value in that array, Xcode itself does a raw concatenation of the array content. This means that any argument that contains a space is interpreted at runtime as multiple arguments.CPython versions tested on:
CPython main branch
Operating systems tested on:
Other
Linked PRs