jamesnetherton commented on PR #8828:
URL: https://github.com/apache/camel-quarkus/pull/8828#issuecomment-4892167578

   Not sure if it's related to these changes, but the `azure-grouped` native 
tests failed:
   
   ```
   Error:  Failures: 
   Error:    AzureStorageBlobIT>AzureStorageBlobTest.blobConsumer:469 1 
expectation failed.
   Expected status code <201> but was <500>.
   Error:    AzureStorageBlobIT>AzureStorageBlobTest.blobContainer:380 1 
expectation failed.
   JSON path containers.name doesn't match.
   Expected: (a collection containing 
"camel-quarkus-7f7f24d7-036c-48e5-96c9-604b5067c8f1" and a collection 
containing "camel-quarkus-4ee2b542-f9ae-4bdf-98db-8feb2df89413")
     Actual: <[camel-quarkus-4ee2b542-f9ae-4bdf-98db-8feb2df89413]>
   Error:    AzureStorageBlobIT>AzureStorageBlobTest.blockBlobStageCommit:188 1 
expectation failed.
   Expected status code <200> but was <500>.
   Error:    AzureStorageBlobIT>AzureStorageBlobTest.crud:97 1 expectation 
failed.
   Expected status code <201> but was <500>.
   Error:    AzureStorageBlobIT>AzureStorageBlobTest.download:142 1 expectation 
failed.
   Expected status code <201> but was <500>.
   Error:    AzureStorageBlobIT>AzureStorageBlobTest.pageBlob:276 1 expectation 
failed.
   Expected status code <201> but was <500>.
   Error:  Errors: 
   Error:  
org.apache.camel.quarkus.component.azure.storage.blob.it.AzureStorageBlobIT.<beforeAll>
   Error:    Run 1: AzureStorageBlobIT>AzureStorageBlobTest.afterAll:83 ยป 
Connect Connection refused
   [INFO]   Run 2: PASS
   [INFO]   Run 3: PASS
   [INFO]   Run 4: PASS
   [INFO]   Run 5: PASS
   [INFO]   Run 6: PASS
   [INFO]   Run 7: PASS
   [INFO] 
   [INFO] 
   Error:  Tests run: 51, Failures: 6, Errors: 1, Skipped: 28
   [INFO] 
   ```


-- 
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