Closed simondeziel closed 2 months ago
@masnax I think you've been working in this area, any idea why those tests now all fail early with:
Error: System "micro02" failed to join the cluster: Failed to update cluster status of services: Failed to join "LXD" cluster: Failed to configure cluster :Failed request to add member: The joining server version doesn't match (expected 5.21.1 with API count 385)
@masnax I think you've been working in this area, any idea why those tests now all fail early with:
Error: System "micro02" failed to join the cluster: Failed to update cluster status of services: Failed to join "LXD" cluster: Failed to configure cluster :Failed request to add member: The joining server version doesn't match (expected 5.21.1 with API count 385)
Was a one time hiccup it seems. Sorry for the ping.
Yay, it seems the longest test consistently finishes in around 3.5h. Not great when taken at face value but it used to hit the timeout limit of 6 hours pretty often before, for me at least.
Here are some boot time and memory usage for the 2nd boot (1st one being ignored due to cloud-init does its thing) of a guest VM.
From:
To:
This helps speeding up the boot of the nested
micro0X
VMs even if the total test runtime seems only slightly reduced.The biggest test runtime gain is from
test/includes/microcloud: don't start VMs after snapshot, reset_systems will
's commit that speeds up thesetup
phase (~9.5 minutes down to ~7.5 minutes).