Skip to content

Conversation

@ychin
Copy link
Member

@ychin ychin commented Oct 31, 2025

The test_artifacts action (which we use to upload artifacts when a test has failed) relies on parsing the CI matrix values to generate a unique artifact name. However, in #1559 we switched to using a reusable workflow instead, which no longer uses a matrix inside the composable workflow. We could simply make a matrix with only one item in it to satisfy the test_artifact action but that seems a bit overkill. Instead, just modify it so we manually pass in the preferred artifact name instead which also gives us more flexibility in the naming. It does mean future upstream merges may cause conflicts.

The test_artifacts action (which we use to upload artifacts when a test
has failed) relies on parsing the CI matrix values to generate a unique
artifact name. However, in macvim-dev#1559 we switched to using a reusable
workflow instead, which no longer uses a matrix inside the composable
workflow. We could simply make a matrix with only one item in it to
satisfy the test_artifact action but that seems a bit overkill. Instead,
just modify it so we manually pass in the preferred artifact name
instead which also gives us more flexibility in the naming. It does mean
future upstream merges may cause conflicts.
@ychin ychin added this to the Release 183 milestone Oct 31, 2025
@ychin ychin added Infrastructure Non-app infrastructure issues, e.g. CI Non User Facing Non-user facing change. These issues do no need to show up in release notes. labels Oct 31, 2025
@github-actions github-actions bot added the CI Vim upstream label for CI issues label Oct 31, 2025
@ychin ychin enabled auto-merge October 31, 2025 00:00
@ychin ychin merged commit 9c0d779 into macvim-dev:master Oct 31, 2025
5 checks passed
@ychin ychin deleted the fix-failed-test-artifact-uploads branch October 31, 2025 00:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Vim upstream label for CI issues Infrastructure Non-app infrastructure issues, e.g. CI Non User Facing Non-user facing change. These issues do no need to show up in release notes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant