To avoid problems with the cache, and specifically running the AzureComputeImageExtensionLiveTest suite.
ARM is quite slow and it takes usually more than one minute (default value) for certain operations. The testImageIsCachedAfterBeingCreated in that suite fails often since it takes longer than one minute to destroy the created node in testCreateImage and cache does not contain the image. It should be safe to increase this value in the provider metadata. 5 minutes looks good but open to discuss Would be good to add this also to https://github.com/danielestevez/jclouds/blob/83c0a3c7b255ec744c6150ce76c40e8301280c79/providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/internal/AzureLiveTestUtils.java ? You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/1206 -- Commit Summary -- * Sets session interval from 60 seconds to a higher value to avoid problems with cache -- File Changes -- M providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/AzureComputeProviderMetadata.java (1) -- Patch Links -- https://github.com/jclouds/jclouds/pull/1206.patch https://github.com/jclouds/jclouds/pull/1206.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1206