[GitHub] [camel-k] phantomjinx commented on pull request #3824: chore(e2e): segregate flaky tests from common,install ITs

[GitBox <gi...@apache.org>]

phantomjinx commented on PR #3824:
URL: https://github.com/apache/camel-k/pull/3824#issuecomment-1324881204

   Hey @tadayosi 
   
   Sorry for the late comment.
   
   I like the idea and in fact there is a "PROBLEMATIC" comment already applied to a number of the tests. When a switch is turned on (midstream OCP test suite has this on by default), these tests are listed and skipped. So we can certainly improve on that as its a little clunky.
   
   My concern is that over the course of the last 8-10 months of executing the tests midstream, the failures can be completely random. Some tests do fail more often than others but sometimes inexplicably the `upgrade` tests fail or the `binding` tests in `common`. Rerunning those tests the following morning and all is good. I do not have a solution for this at this time. Accepting that most of the time the midstream test suite shows "red" after a full run has become the norm.


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org