🤖 New build scheduled with the buildbot fleet by @tiran for commit 2a3424d7b8ef485a0df2589f54073e7e0f009ce3 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

Looks like Windows still wants those symbols exported.

https://github.com/python/cpython/runs/4332435157?check_suite_focus=true#step:4:724

@brettcannon Is there libffi-8.dll in $(ExternalsDir)libffi-3.4.2 runner directory when a GitHub action fails (as declared in libffi.props)? I cannot say "the library is present because other imports are resolved" since ffi_type_* look like the only ffi exports. At least there is no other declaration with FFI_EXTERN in headers before generation.

@brettcannon Is there libffi-8.dll in $(ExternalsDir)libffi-3.4.2 runner directory when a GitHub action fails (as declared in libffi.props)?

No idea.

Steve explained the issue on BPO. Windows cannot statically reference values from a DLL.

🤖 New build scheduled with the buildbot fleet by @tiran for commit 6787c5c 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

ARM64 buildbot is failing with LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt, https://buildbot.python.org/all/#/builders/739/builds/265

🤖 New build scheduled with the buildbot fleet by @tiran for commit 6787c5c 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.