-
Notifications
You must be signed in to change notification settings - Fork 658
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 of lidar_apollo_segmentation_tvm
failing in CI
#5765
Comments
@lexavtanke @ambroise-arm @angry-crab Hi, recently the build-and-test CIs are failing partially due to this package's test failure. Mentioning you since this PR might be relevant: #5431. |
Note: from looking quickly at the github actions, it seems to only happen on the self-hosted aarch64 pipelines, and it seems it has only been happening for a few days. Unless the failure has some random component to it, as I didn't check all pipelines. |
@ambroise-arm Thank you for checking. I suspect this is has been occurring for days, just been hidden by the build failure that has been fixed a couple of day before with this PR: #5749 |
I couldn't reproduce locally. It is not obvious to me what is wrong. |
@ambroise-arm As stated in the description, I think it's because the CI cannot access deploy_lib.so |
Indeed. But it is expected that this deploy_lib.so file (and a couple of other files) will not be present in CI. Some code was added to the tests to skip them if the files are not present: autoware.universe/perception/lidar_apollo_segmentation_tvm/test/main.cpp Lines 109 to 115 in 60b4030
I don't know why it works as expected on the x86 CI runners (as well as locally for me on an arm64 machine), but fails on the arm64 CI runners. |
Now make sense. But have no idea why the CI fails 🤔 |
This pull request has been automatically marked as stale because it has not had recent activity. |
@kminoda , I can try to help on this topic. Firstly pls confirm if this problem still exists, I have tried to build/run in our ARM64 test target, can not repeat the problem so far.
|
@JunWu-ARM Thank you for checking. Actually it seems that we no longer have this issue in |
@kminoda I see that there are passing pipelines in https://github.com/autowarefoundation/autoware.universe/actions/workflows/build-and-test-daily-arm64.yaml, but inside of those I only see EDIT: It probably got removed following the remark from Fatih in https://github.com/orgs/autowarefoundation/discussions/4794#discussioncomment-9605616 |
@kminoda My steps for the test:
What I found is inside the docker, the pre-installed library is for x86_64 architecture
And we can see ( |
@oguzkaganozt , @youtalk, could you please review my investigation ? Summary:Whether the test will report an error depends on who runs the test:
In our development environment, we login as host user by run ./docker/run.sh so the user in docker is non-root, so it reports success (detailed log show test skipped). In the autoware github pipeline, it runs docker image as root so it reports the error
Please note that the user inside the Docker container depends on how the Docker image was built. If no user is set during the build of the Docker image, the default user inside the container will be root (uid 0) (or we can set userid and groupid when run the docker) |
Closing the issue as the package is being removed by #7996 |
Checklist
Description
Test of
lidar_apollo_segmentation_tvm
failingsays:
https://github.com/autowarefoundation/autoware.universe/actions/runs/7080300141/job/19267993325
Expected behavior
Should pass
Actual behavior
Does not pass
Steps to reproduce
See the CI result
Versions
No response
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: