-
Notifications
You must be signed in to change notification settings - Fork 719
CI: use macos-13 instead of macos-latest #3366
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
Conversation
our workflows assume macos-latest is intel. but now it's arm64. use macos-13, which is documented to be intel, instead. reference: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners XXX what to do for test-tools/wamr-ide/VSCode-Extension/src/utilities/lldbUtilities.ts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Let's merge this PR first to address the CI issue, and check whether we should modify this file later. |
Apply patches which were fixed in branch main to branch `release/1.3.x`: - aot debug: Fix a few NULL dereferences on errors (#3273) - aot debug: Fix a NULL dereference (#3274) - aot debug: Process lldb_function_to_function_dbi only for C (#3278) - Revert "lldb_function_to_function_dbi: A hack to avoid crashing on C++ methods (#3190)" (#3281) - Fix warnings/issues reported in Windows and by CodeQL/Coverity (#3275) - thread mgr: Free aux stack only when it was allocated (#3282) - interp: Restore context from prev_frame after tail calling a native f unction (#3283) - Sync simd opcode definitions spec (#3290) - Add more checks in wasm loader (#3300) - Fix posix_fadvise error handling (#3323) - Fix readdir for posix (#3339) - wasm loader: Fix checks for opcode ref.func and opcode else (#3340) - Enhance wasm loader checks for opcode br_table (#3352) - CI: Use macos-13 instead of macos-latest (#3366)
Our workflows assume macos-latest is intel, but now it's arm64. Use macos-13, which is documented to be intel, instead. reference: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners
Our workflows assume macos-latest is intel, but now it's arm64. Use macos-13, which is documented to be intel, instead. reference: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners Signed-off-by: victoryang00 <[email protected]>
Our workflows assume macos-latest is intel, but now it's arm64. Use macos-13, which is documented to be intel, instead. reference: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners
Our workflows assume macos-latest is intel, but now it's arm64. Use macos-13, which is documented to be intel, instead. reference: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners Signed-off-by: victoryang00 <[email protected]>
our workflows assume macos-latest is intel. but now it's arm64. use macos-13, which is documented to be intel, instead.
reference:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners
XXX what to do for test-tools/wamr-ide/VSCode-Extension/src/utilities/lldbUtilities.ts?