improve: marking long running tests as integration test by csviri · Pull Request #3028 · operator-framework/java-operator-sdk

Conversation

@csviri

It seems that something changed in fabric8 client at some point, therefore these tests try to connect to a cluster, when the client is created. We can simply mark them as integration tests, so runs part of that suit, and does not prolong the build

Signed-off-by: Attila Mészáros a_meszaros@apple.com

Signed-off-by: Attila Mészáros <a_meszaros@apple.com>

@metacosm

It seems that something changed in fabric8 client at some point, therefore these tests try to connect to a cluster, when the client is created. We can simply mark them as integration tests, so runs part of that suit, and does not prolong the build

Can you point to an occurrence of the issue? Maybe this is something we should address with the Fabric8 team?

metacosm

xstefank

@csviri

It seems that something changed in fabric8 client at some point, therefore these tests try to connect to a cluster, when the client is created. We can simply mark them as integration tests, so runs part of that suit, and does not prolong the build

Can you point to an occurrence of the issue? Maybe this is something we should address with the Fabric8 team?

It seems that when the client is created it already does some connection. Will follow up on in fabric8 when back from vacation

@csviri csviri deleted the long-running-test branch

November 3, 2025 14:29