I recently expanded the testing matrix of my macro package. I have some GitHub actions that run on every push to main
. I started testing Linux builds and I am seeing some strange failures. They seem to be on some narrow but consistent set of configuration variables.
Here is my testing matrix for macOS:
xcode-version:
- "15.4"
- "16.0"
- "16.1"
- "16.2"
- "16.3"
swift-syntax-version:
- "510.0.0"
- "510.0.1"
- "510.0.2"
- "510.0.3"
- "600.0.0"
- "600.0.1"
- "601.0.0"
- "601.0.1"
configuration:
- debug
- release
Here is my testing matrix for Linux:
swift-version:
- "5.10.1"
- "6.0.0"
- "6.0.1"
- "6.0.2"
- "6.0.3"
- "6.1.0"
swift-syntax-version:
- "510.0.0"
- "510.0.1"
- "510.0.2"
- "510.0.3"
- "600.0.0"
- "600.0.1"
- "601.0.0"
- "601.0.1"
configuration:
- debug
- release
I then run the builds and test across those products.
All of my macOS build run pass.
All of my macOS test runs pass.
All of my Linux build runs pass.
The following Linux test runs are failing:
- Swift 6.0.0 / swift-syntax 510.0.0 / debug
- Swift 6.0.1 / swift-syntax 510.0.0 / debug
- Swift 6.0.2 / swift-syntax 510.0.0 / debug
- Swift 6.0.3 / swift-syntax 510.0.0 / debug
It's only this range of Swift toolchains… only this specific version of swift-syntax
… only debug
builds… and only when I run tests.
I have no idea what could be causing this… but I've run these all multiple times and I keep seeing the same failures. Whatever it is… it seems to be consistent.
Here is an example of what the output looks like:
Any ideas? Can anyone else reproduce a failure on that specific configuration on their macro package from Linux?