Very old Selenium container in Helm tests

[fleaz]

Hey.

We just discovered that the Helm tests for Keycloakx use a Selenium container from 2023, and because the whole Seleniarm piroject has been archived in 2024, so we can't just update to a newer tag.

Maybe switch to the regular Selenium images?

helm-charts/charts/keycloakx/values.yaml

Lines 613 to 616 in 4e64ddf

	# The image for the test Pod
	repository: docker.io/seleniarm/standalone-chromium
	# The tag for the test Pod image
	tag: "117.0"

A quick test failed at the pip installation in the test.sh, so there need to be a few changes maade, to make it work with the new container.

[github-actions]

This issue has been marked as stale because it has been open for 30 days with no activity. It will be automatically closed in 10 days if no further activity occurs.

[fleaz]

Marking issues as stale, won't make them go away...

[dominiquemetz]

Hi! That is true. We are trying our best, but sometimes we just don't have as much time as we would need and want 🙂 I will take a look and see that we fix this

[fleaz]

Thanks for the fix! :)

Just to clarify my previous post, because it maybe looked more angry than it was:

There is nothing wrong with keeping issues open, when there is no time to fix them. I just really dislike these bots that automatically close them after X days because the bug is not fixed just because the issue got closed and it e.g. helps other people to see that this already got addressed when they look for a matching issue when they encounter a problem