Skip to content

Conversation

@finagolfin
Copy link
Contributor

Should work well, considering I run this repo through my Android CI.

…id triples and NDKs and run the tests in the Android x86_64 emulator
tests:
name: Test
uses: swiftlang/github-workflows/.github/workflows/swift_package_test.yml@0.0.4
uses: swiftlang/github-workflows/.github/workflows/swift_package_test.yml@main
Copy link
Contributor

@rauhul rauhul Jan 11, 2026

Choose a reason for hiding this comment

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

can this wait until android support is in a tagged release?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, of course, but I simply wanted to start testing the new Android emulator check in the workflow itself. Can you approve the workflow on this pull now so we can try that?

Copy link
Contributor

Choose a reason for hiding this comment

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

Certainly :)

@finagolfin
Copy link
Contributor Author

Oh, I forgot this repo also depends on cross-compiled executables that have to be moved onto the test target environment alongside the test runner for all tests to pass, as I've been doing on my Android CI for years.

Copy link
Contributor

@rauhul rauhul left a comment

Choose a reason for hiding this comment

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

didn't mean to approve, just enable the checks to run

@finagolfin
Copy link
Contributor Author

No problem, no point in merging this till we have a solution for the additional executables.

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