© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Looks like this is happening most in the nova-next job which runs tempest.api.compute and scenario tests, slow and non-slow, concurrently, so maybe the concurrency on the scenario tests in that job is what is teasing out the race failure since the tempest-slow job runs the scenario tests serially.