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

test-macstadium-macos1015-x64-1 linker incompatibility? ld: unsupported tapi file type '!tapi-tbd' in YAML #1777

Open
andrew-m-leonard opened this issue Dec 22, 2020 · 8 comments

Comments

@andrew-m-leonard
Copy link
Contributor

Any testcase that tries to compile build-natives-unix, fails with the following on this node:

02:20:41       [exec] gcc -m64 -dynamiclib -o /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/system/openjdk-systemtest/openjdk.test.modularity/bin/tests/com.test.jlink/native/bin/osx_x86-64/libJniTest.dylib /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/system/openjdk-systemtest/openjdk.test.modularity/bin/tests/com.test.jlink/native/lib/osx_x86-64/JniTest.o
02:20:42       [exec] ld: unsupported tapi file type '!tapi-tbd' in YAML file '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/lib/libSystem.tbd' for architecture x86_64
02:20:42       [exec] clang: error: linker command failed with exit code 1 (use -v to see invocation)

https://ci.adoptopenjdk.net/view/Test_system/job/Test_openjdk11_j9_extended.system_x86-64_mac/431/console

Ref: adoptium/aqa-tests#2133

@andrew-m-leonard
Copy link
Contributor Author

Try compiling a hello world C program:

test-macstadium-macos1015-x64-1:andrew jenkins$ gcc HelloWorld.c 
ld: unsupported tapi file type '!tapi-tbd' in YAML file '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/lib/libSystem.tbd' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@andrew-m-leonard
Copy link
Contributor Author

I've removed the ci.role.test from this node until we can fix the setup
@smlambert

@sxa
Copy link
Member

sxa commented Dec 23, 2020

As per discussion yesterday this is yours @gdams :-)

@sxa
Copy link
Member

sxa commented Feb 21, 2022

Will likely need a reinstall of Xcode (can that be done via ansible?) as there seems some incompatibility between something on the machine. May be worth trying to compare with a known good machine at the same Xcode level if one of the others ones is in a suitable state.

@sxa sxa removed this from the 2022-03 (March) milestone May 24, 2022
@sxa sxa added this to the 2022-06 (June) milestone May 24, 2022
@sxa sxa modified the milestones: 2022-06 (June), 2022-07 (July) Jun 30, 2022
@sxa sxa added the systemdown label Jan 27, 2023
@sxa
Copy link
Member

sxa commented Jan 30, 2023

Since this is a systemdown I'm marking it as critical as it's currently a waste of a machine ...

@sxa sxa added the critical label Jan 30, 2023
@sxa
Copy link
Member

sxa commented Jun 6, 2023

@Haroon-Khel If this is potentially a reinstall of Xcode is it something that can be/will be/has been covered by your ansible playbook executions under #695 ?

@sxa sxa modified the milestones: 2023-04 (April), 2023-06 (June) Jun 6, 2023
@sxa sxa modified the milestones: 2023-06 (June), 2023-07 (July) Jul 7, 2023
@sxa
Copy link
Member

sxa commented Jul 12, 2023

Noting that it is likely we will replace this system with a machine from orka as part of #2536

@sxa
Copy link
Member

sxa commented Jul 12, 2023

As per discussion yesterday this is yours @gdams :-)

@gdams Should we just shut this system down in macstadium for now on the basis we'll likely create equivalents in orka and this machine has been chewing up costs while unusable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

5 participants