r-hub / actions

GitHub Actions for R-hub
MIT License
21 stars 5 forks source link

`macos-arm64` fails with `symbol not found in flat namespace '_ps__list_apps'` #28

Closed pawelru closed 1 week ago

pawelru commented 1 week ago

Observed for r-release-macos-arm64 and r-oldrel-macos-arm64 Step: Run r-hub/actions/setup-deps@v1

Dependency resolution
  Error in dyn.load(dll_file) : 
    unable to load shared object '/private/var/folders/g6/rgtlsw6n123b0gt5483s5_cm0000gn/T/RtmpafSxCY/file1ee56fa0ad26/ps/libs//ps.so':
    dlopen(/private/var/folders/g6/rgtlsw6n123b0gt5483s5_cm0000gn/T/RtmpafSxCY/file1ee56fa0ad26/ps/libs//ps.so, 0x0006): symbol not found in flat namespace '_ps__list_apps'
  Calls: <Anonymous> ... load_private_packages -> load_private_package -> dyn.load
  Execution halted

This is a common failure across multiple (if not all) of pkgs that uses rhub workflows. Few examples: [1], [2], [3]

Re-run didn't help.

That must be a recent change. The same workflow (on the same R package codebase) succeeded last week.

Appreciate your help on this.

gaborcsardi commented 1 week ago

Seems like a bug in the devel pak build.

gaborcsardi commented 1 week ago

I'll move this over to pak. EDIT: actually, never mind, I cannot. Will fix in a minute.

gaborcsardi commented 1 week ago

This was a bug in the pak nightly builds, which were not prepared for Objective-C files when cross compiling for arm64 macOS on x86_64 macOS. Fixed here: https://github.com/r-lib/pak/commit/fe4d2c6da65d534780cf73371819814cfeb81b57

I also removed the cross compiling, no need for that now that GHA has native arm64 macs: https://github.com/r-lib/pak/commit/659fbf1f12094d2dd2e228930f78282b6a3bc647 https://github.com/r-lib/pak/commit/e7d20861baebd54c2412530a12e781c1e99066d3

I started a new build, I'll comment here when the new versions are deployed: https://github.com/r-lib/pak/actions/runs/11890375962/job/33128891191

gaborcsardi commented 1 week ago

The new binaries are deployed, so this should be fixed now. Thanks for the report!

pawelru commented 1 week ago

I re-run the failed workflows and I confirm - all is looking good now! Thank you for the prompt action!

gaborcsardi commented 1 week ago

For the record, this is going to get better soon: