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

Follow-up Wasm CI integration #193

Merged

Conversation

kateinoigakukun
Copy link
Contributor

@kateinoigakukun kateinoigakukun commented Aug 28, 2024

We are moving to Swift SDK-style installation on the development branch, and swift test with static stdlib is broken in obsoleting toolchain-style installation now.

Verified it works here ✅ https://github.com/kateinoigakukun/swift-case-paths/actions/runs/10591664518/job/29349506477

@kateinoigakukun kateinoigakukun mentioned this pull request Aug 28, 2024
@kateinoigakukun kateinoigakukun marked this pull request as ready for review August 28, 2024 06:57
Copy link
Member

@mbrandonw mbrandonw left a comment

Choose a reason for hiding this comment

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

This is awesome, thanks so much @kateinoigakukun! We'll try to get Wasm CI on all of our repos that it's possible.

@mbrandonw mbrandonw merged commit 857ba4e into pointfreeco:add-wasm-ci Aug 29, 2024
3 checks passed
mbrandonw added a commit that referenced this pull request Aug 29, 2024
* Add Wasm CI.

* fix for wasi

* fix

* wip

* use dev snapshot

* include static swift stdlib

* wip

* fix wasi

* wasi fixes

* fix

* wip

* wip

* wip

* try env var

* wip

* wip

* wip

* wip

* Follow-up Wasm CI integration (#193)

* Skip several deprecated tests on WebAssembly

* Use the official compiler and Swift SDK for WebAssembly

* Grant access to the current directory to the XCTest harness

---------

Co-authored-by: Yuta Saito <kateinoigakukun@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants