Flaky TestMetrics

[lburgazzoli]

What happened?

The test is marked a problematic and fails for a slightly different metric values:

camel-k/e2e/advanced/operator_metrics_test.go

Lines 48 to 55 in 4114271

	/*
	* TODO
	* The duration_seconds tests keep randomly failing on OCP4 with slightly different duration values
	* May need to lessen the strict checking parameters
	*
	* Adding CAMEL_K_TEST_SKIP_PROBLEMATIC env var for the moment.
	*/
	func TestMetrics(t *testing.T) {

We should investigate the reason of the flakiness

Relevant log output

##[group]�[0;31m❌ TestMetrics�[0;37m (3m36.99s)�[0m
Copy catalog camel-catalog-3.8.1 from namespace default
Setting build timeout to 10m
OLM is not available in the cluster. Fallback to regular installation.
Camel K installed in namespace test-d75e73db-6a7e-442c-b7d7-6471ffbdbb76 
2024-05-08T21:43:47Z	DEBUG	camel-k	Finding available platforms in namespace test-d75e73db-6a7e-442c-b7d7-6471ffbdbb76
2024-05-08T21:43:47Z	DEBUG	camel-k	Found active integration platform camel-k-metrics
Integration "javapmdgm" created
2024-05-08T21:44:18Z	DEBUG	camel-k	Finding available platforms in namespace test-4e73dff2-ea42-45af-b99e-48af4da2e033
2024-05-08T21:44:18Z	DEBUG	camel-k	Found active integration platform camel-k-cli-reset
0 pipes deleted from namespace test-4e73dff2-ea42-45af-b99e-48af4da2e033
2024-05-08T21:44:18Z	INFO	KubeAPIWarningLogger	v1apha1.KameletBinding is deprecated, please, use v1.Pipe instead
0 kameletbindings deleted from namespace test-4e73dff2-ea42-45af-b99e-48af4da2e033
2 integrations deleted from namespace test-4e73dff2-ea42-45af-b99e-48af4da2e033
Camel K platform has been reset successfully!
2024-05-08T21:44:18Z	DEBUG	camel-k	Finding available platforms in namespace test-4e73dff2-ea42-45af-b99e-48af4da2e033
2024-05-08T21:44:18Z	DEBUG	camel-k	Found active integration platform camel-k-cli-reset
Nothing to delete
    operator_metrics_test.go:325: 
        Expected
            <uint>: 10
        to be ==
            <uint64>: 9

[squakez]

Probably not an issue (at least, not in upstream CI). See #5484

[lburgazzoli]

That is an error I observed upstream at least on two unrelated PRs

[squakez]

Let's add it to the flakiness bucket then.