Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Upload failed MacVim tests artifacts, misc improvements #1522

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

ychin
Copy link
Member

@ychin ychin commented Jan 7, 2025

Add MacVim test failure results to the list of failed artifacts to upload. The xcresult folder can be opened in Xcode for inspection to help understand what went wrong. Also, fix the ordering so failed Vim GUI test artifacts can be uploaded as well.

When configuring Vim, be explicit to not build with sodium/gettext for the non-publish builds. This makes sure that even if the CI environment somehow has them installed by default, we won't use them by mistake. Those installed packages would be built for a different OS target anyway and throw out warnings (the ones we bundle with MacVim are custom built to target the proper OS versions).

@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 Jan 7, 2025
@ychin ychin added this to the Release 181 milestone Jan 7, 2025
@ychin ychin requested a review from Copilot January 7, 2025 01:30

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

@github-actions github-actions bot added the CI Vim upstream label for CI issues label Jan 7, 2025
Add new step to upload MacVim test results when we have failed tests.
The xcresult folder can be opened in Xcode for inspection to help
understand what went wrong. Also, fix the ordering so failed Vim GUI
test artifacts can be uploaded as well.

When configuring Vim, be explicit to not build with sodium/gettext for
the non-publish builds. This makes sure that even if the CI environment
somehow has them installed by default, we won't use them by mistake.
Those installed packages would be built for a different OS target anyway
and throw out warnings (the ones we bundle with MacVim are custom built
to target the proper OS versions).
@ychin ychin force-pushed the ci-upload-failed-macvim-tests branch 2 times, most recently from 2f510ac to 5b30e66 Compare January 7, 2025 03:23
@ychin ychin merged commit ea84370 into macvim-dev:master Jan 7, 2025
4 of 8 checks passed
@ychin ychin deleted the ci-upload-failed-macvim-tests branch January 7, 2025 03:24
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