andrijapanicsb commented on PR #13656:
URL: https://github.com/apache/cloudstack/pull/13656#issuecomment-5159210126

   > [SF] Trillian test result (tid-16666) Environment: kvm-ol8 (x2), zone: 
Advanced Networking with Mgmt server ol8 Total time taken: 55055 seconds Marvin 
logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr13656-t16666-kvm-ol8.zip
 Smoke tests completed. 154 look OK, 2 have errors, 0 did not run Only failed 
and skipped tests results shown below:
   > Test       Result  Time (s)        Test File
   > test_08_arping_in_ssvm     `Failure`       5.28    test_diagnostics.py
   > test_01_ssl_offloading_isolated_network    `Failure`       703.98  
test_ssl_offloading.py
   > test_02_ssl_offloading_project_vpc         `Failure`       689.71  
test_ssl_offloading.py
   
   Ran the full smoke test suite against an environment built from this PR (two 
management servers + two KVM hosts on Rocky Linux 9, NFS primary and secondary 
storage).
   
   Result: **154 test files passed, 2 had failures** (4 failing tests in total):
   
   - `test_02_list_cpvm_vm` / `test_04_cpvm_internals` (test_ssvm.py) — the 
console proxy VM was down/restarting at the moment the tests listed it (the log 
shows "Found a stopped console proxy" right at that time). Timing, not a 
functional problem.
   - `test_11_destroy_ssvm` (test_ssvm.py) — the destroy raced a replacement 
SSVM that was still in Starting state, so the API correctly refused to expunge 
it.
   - `test_02_ssl_offloading_project_vpc` (test_ssl_offloading.py) — single 
VPC/SSL test failure, unrelated area.
   
   None of the four touch anything changed by this PR — no VMware import, CBT, 
RBD or Linstor code paths are involved. They look like the usual system-VM 
timing flakiness rather than regressions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to