tadayosi commented on issue #3667: URL: https://github.com/apache/camel-k/issues/3667#issuecomment-1259177605
> Upstream, the tests install the operator without OLM and therefore adds the correct operatorID (the test uses "[camel-k-kamelet](https://github.com/apache/camel-k/blob/main/e2e/global/common/kamelet_test.go#L36)"). So the integration-platform is named with this id and the warning message above is avoided. I don't think so. For upstream global e2e testing, `KamelInstallWithOperatorID()` also omits the operator ID so the IntegrationPlatform should be always `camel-k`: https://github.com/apache/camel-k/blob/main/e2e/support/test_support.go#L246 As I understand it, when `CAMEL_K_FORCE_GLOBAL_TEST=true` is set, e2e tests always skip the operator ID part and use `camel-k` throughout the tests. I think what's problematic is this line. Since it explicitly specifies `-x <operator-id>` it should happen to skip the `globalTest` guard provided by `Kamel*()` test support funcs. I wonder why upstream e2e still passes the test :thinking: https://github.com/apache/camel-k/blob/main/e2e/global/common/kamelet_test.go#L65 -- 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]
