knockknock10 commented on issue #6979:
URL: https://github.com/apache/camel-k/issues/6979#issuecomment-6999035395

   I went through the failure and found that the KEDA e2e suite was hitting its 
20-minute suite-wide timeout, rather than a RabbitMQ scaler issue.
   
   Upstream commit 
[[d804867](https://github.com/apache/camel-k/commit/d804867748ce62c7f8136cf15433237eb00df8eb)](https://github.com/apache/camel-k/commit/d804867748ce62c7f8136cf15433237eb00df8eb)
 increased the KEDA suite timeout to 30 minutes. I also checked a subsequent 
successful KEDA workflow run on `main`, and confirmed the updated timeout is 
present in the current Makefile.
   
   I couldn't reproduce the test locally because my Kubernetes context was 
unreachable, but the upstream CI result supports this being resolved. 


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