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

   _AI-generated update on behalf of Sanjeev Kumar (@knockknock10)_
   
   I investigated the failure from the linked run. The repeated ScaledObject 
not found messages are the expected result of the test's initial polling before 
Camel K creates the resource; they are not the assertion that fails.
   
   The underlying problem was that the KEDA e2e suite had a 20-minute 
package-wide go test deadline. The Spring RabbitMQ test began near that 
deadline and the suite was terminated while it was still waiting for the 
generated ScaledObject.
   
   This has already been resolved on main by #6974 (commit d804867748), which 
raises test-keda to 30 minutes specifically because the suite was already close 
to the 20-minute limit. Its KEDA workflow completed successfully: 
https://github.com/apache/camel-k/actions/runs/44020321449/job/133900753939
   
   No additional PR is needed; creating one would duplicate the merged fix.


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