Disable failing activemq tests

[cmacknz]

Skip the activemq test suite until we can determine why the tests are failing.

• Relates x-pack.metricbeat.module.activemq.test_activemq tests are failing with a timeout #35851

[elasticmachine]

Pinging @elastic/integrations-services (Team:Services)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @cmacknz? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[shmsr]

Approving this as we need to debug this.

@cmacknz Is it because of this 62374dd because there were some Python-related changes? I'll also debug on what's happening but haven't found it.

[cmacknz]

@cmacknz Is it because of this 62374dd because there were some Python-related changes? I'll also debug on what's happening but haven't found it.

I suppose it is possible, I swear I had the these test pass after rerunning that test suite but it looks like the results may have just been delayed.

The odd thing is that there were no changes to activemq at all. If you start only the activemq container it never becomes healthy.

cd x-pack/metricbeat/module/activemq
docker-compose up

The health check that is failing is:

beats/x-pack/metricbeat/module/activemq/_meta/Dockerfile

Lines 31 to 32 in 1e280d4

	HEALTHCHECK --interval=1s --retries=90 CMD nc -w 1 -v 127.0.0.1 $ACTIVEMQ_STOMP </dev/null && \
	nc -w 1 -v 127.0.0.1 $ACTIVEMQ_REST </dev/null

If you run this in the container started manually it fails with no output.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-06-21T13:54:51.349+0000

• Duration: 54 min 4 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1419
Skipped	96
Total	1515

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[shmsr]

@cmacknz Is it because of this 62374dd because there were some Python-related changes? I'll also debug on what's happening but haven't found it.

I suppose it is possible, I swear I had the these test pass after rerunning that test suite but it looks like the results may have just been delayed.

The odd thing is that there were no changes to activemq at all. If you start only the activemq container it never becomes healthy.

cd x-pack/metricbeat/module/activemq
docker-compose up

The health check that is failing is:

beats/x-pack/metricbeat/module/activemq/_meta/Dockerfile

Lines 31 to 32 in 1e280d4

	HEALTHCHECK --interval=1s --retries=90 CMD nc -w 1 -v 127.0.0.1 $ACTIVEMQ_STOMP </dev/null && \
	nc -w 1 -v 127.0.0.1 $ACTIVEMQ_REST </dev/null

If you run this in the container started manually it fails with no output.

Oh, okay. I'll also take a look.