gnodet commented on pull request #5634:
URL: https://github.com/apache/camel/pull/5634#issuecomment-857436717


   > @gnodet there is a log file created by failsafe. Within the component 
directory (ie.: `component/camel-couchbase`) there should be a file named 
`target/camel-couchbase-test.log` which should display something like:
   > 
   > ```
   > 2021-06-09 07:43:04,569 [main           ] ERROR ContainerEnvironmentUtil   
    - Failed to evaluate whether the docker environment is available:  <reason 
> 
   > <stack trace>
   > ...
   > 2021-06-09 07:43:04,572 [main           ] WARN  ContainerEnvironmentUtil   
    - Turning off container-based tests because docker does not seem to be 
working correctly
   > 2021-06-09 07:43:04,573 [main           ] WARN  ContainerService           
    - Test class 
org.apache.camel.component.couchbase.integration.RemoveMessagesIT is disabled 
because docker is not available
   > 2021-06-09 07:43:04,577 [main           ] WARN  ContainerService           
    - Test class 
org.apache.camel.component.couchbase.integration.ConsumeMessagesWithLimitIT is 
disabled because docker is not available
   > 2021-06-09 07:43:04,579 [main           ] WARN  ContainerService           
    - Test class 
org.apache.camel.component.couchbase.integration.ProduceMessagesSimpleIT is 
disabled because docker is not available
   > 2021-06-09 07:43:04,581 [main           ] WARN  ContainerService           
    - Test class 
org.apache.camel.component.couchbase.integration.ProduceMessagesWithAutoIDIT is 
disabled because docker is not available
   > ```
   > 
   > Do you have that file?
   
   Yes, you're right.  The file is here and the reason `Could not find a valid 
Docker environment.` too.  It seems not really intuitive to not have anything 
in the maven log somehow.  
   I wonder if we could have the tests flagged as if a junit assumption was not 
met (which is somewhat the case), the problem is that they are simply not 
listed at all.  


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

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


Reply via email to