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

Nightly Jobs (Scheduled Jobs) are failing #8966

Closed
kgpai opened this issue Mar 5, 2024 · 4 comments
Closed

Nightly Jobs (Scheduled Jobs) are failing #8966

kgpai opened this issue Mar 5, 2024 · 4 comments
Labels

Comments

@kgpai
Copy link
Contributor

kgpai commented Mar 5, 2024

Problem description

The nightly jobs (https://github.com/facebookincubator/velox/actions/workflows/scheduled.yml) are currently failing because they cannot load libboost

error while loading shared libraries: libboost_context.so.1.84.0: cannot open shared object file: No such file or directory

System information

See : https://github.com/facebookincubator/velox/actions/runs/8150420469/job/22277980506#step:5:22

./spark_expression_fuzzer_test: error while loading shared libraries: libboost_context.so.1.84.0: cannot open shared object file: No such file or directory
Error: Process completed with exit code 127.

CMake log

No response

@kgpai kgpai added build triage Newly created issue that needs attention. labels Mar 5, 2024
@kgpai
Copy link
Contributor Author

kgpai commented Mar 5, 2024

cc: @czentgr @majetideepak

@kgpai kgpai removed the triage Newly created issue that needs attention. label Mar 5, 2024
@czentgr
Copy link
Collaborator

czentgr commented Mar 6, 2024

The setup script does not actually build the dependencies that may be required - this is expected because if the script is sourced it skips any build step.
So when the image was built to be used with the runner it likely has the shared library dependency (aka at built time it used the system install as opposed to the bundled version). And that dependency won't be installed by the script in the runner environment.
So I guess we will have to ensure that boost is statically linked.

Previously, boost on Ubuntu always came from the system package manager. But the new version is not present, hence it comes from the setup script.

How is fmt and folly handled? I looked at the yml but it wasn't clear how they are sourced.

Attempt at a fix: #8970

@majetideepak
Copy link
Collaborator

I described the fix here #8943

@mbasmanova
Copy link
Contributor

I believe this is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants