-
Notifications
You must be signed in to change notification settings - Fork 416
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_vhost_user_blk tests failed on aarch64 worker #5934
Comments
It is very strange that I can't reproduce the above errors offline when I ran the complete integration test suite with @michael2012z @MrXinWang Please let me know if you have any tips. Thank you. |
See: cloud-hypervisor#5934 Signed-off-by: Bo Chen <chen.bo@intel.com>
See: cloud-hypervisor#5934 Signed-off-by: Bo Chen <chen.bo@intel.com>
See: cloud-hypervisor#5934 Signed-off-by: Bo Chen <chen.bo@intel.com>
See: #5934 Signed-off-by: Bo Chen <chen.bo@intel.com>
The problem seems tricky, I cannot reproduce the failure in my local machine. |
I ran test_vhost_user_blk on Ampere Altra and Ampere One and all tests passed.
|
Right. That's the tricky part. We can't reproduce the error manually, even though the CI is using the same machine... |
See: cloud-hypervisor#5934 Signed-off-by: Bo Chen <chen.bo@intel.com> (cherry picked from commit 62db13b)
See: cloud-hypervisor#5934 Signed-off-by: Bo Chen <chen.bo@intel.com> (cherry picked from commit 62db13b)
See: cloud-hypervisor#5934 Signed-off-by: Bo Chen <chen.bo@intel.com> (cherry picked from commit 62db13b)
See: cloud-hypervisor#5934 Signed-off-by: Bo Chen <chen.bo@intel.com> (cherry picked from commit 62db13b)
These tests have been failing multiple times on the main branch:
https://cloud-hypervisor-jenkins.westus.cloudapp.azure.com/blue/rest/organizations/jenkins/pipelines/cloud-hypervisor/branches/main/runs/675/nodes/151/log/?start=0
https://cloud-hypervisor-jenkins.westus.cloudapp.azure.com/blue/rest/organizations/jenkins/pipelines/cloud-hypervisor/branches/main/runs/676/nodes/47/log/?start=0
https://cloud-hypervisor-jenkins.westus.cloudapp.azure.com/blue/rest/organizations/jenkins/pipelines/cloud-hypervisor/branches/main/runs/677/nodes/47/steps/176/log/?start=0
Also errors being reported seem to be very consistent:
The first failure was from commit 815c7f4 while the corresponding PR #5925 passed the CI (and I confirmed the PR was running the tests with the latest container image e.g.
20231108-0
).The text was updated successfully, but these errors were encountered: