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

[BUG]: TestPipeline.EngineFactories fails on arm64 #525

Open
2 tasks done
dagardner-nv opened this issue Dec 20, 2024 · 0 comments
Open
2 tasks done

[BUG]: TestPipeline.EngineFactories fails on arm64 #525

dagardner-nv opened this issue Dec 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@dagardner-nv
Copy link
Contributor

Version

25.02

Which installation method(s) does this occur on?

Docker

Describe the bug.

Observed in CI:

2024-12-20T18:30:16.0896967Z [ RUN      ] TestPipeline.EngineFactories
2024-12-20T18:30:16.0898474Z E20241220 18:30:14.152635 281473592543296 service.cpp:40] Must call Service::call_in_destructor to ensure service is cleaned up before being destroyed
2024-12-20T18:30:16.0900601Z unknown file: Failure
2024-12-20T18:30:16.0901830Z C++ exception with description "cpu_set must be a subset of the initial topology to create a fiber pool" thrown in the test body.
2024-12-20T18:30:16.0902949Z 
2024-12-20T18:30:16.0903255Z [  FAILED  ] TestPipeline.EngineFactories (92 ms)

Minimum reproducible example

Enable TestPipeline.EngineFactories

Relevant log output

Full env printout

Other/Misc.

No response

Code of Conduct

  • I agree to follow MRC's Code of Conduct
  • I have searched the open bugs and have found no duplicates for this bug report
@dagardner-nv dagardner-nv added the bug Something isn't working label Dec 20, 2024
dagardner-nv added a commit to dagardner-nv/MRC that referenced this issue Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

1 participant