Migrate e2e test for MongoDB to Go.

[v-shenoy]

Signed-off-by: Vighnesh Shenoy [email protected]

Provide a description of what has been changed

Checklist

• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• Tests have been added

Fixes #3241

Relates to #2737

[v-shenoy]

/run-e2e mongo
Update: You can check the progress here

[v-shenoy]

Any idea why the tests are queued for so long? @JorTurFer

[v-shenoy]

/run-e2e mongo
Update: You can check the progress here

[JorTurFer]

Any idea why the tests are queued for so long? @JorTurFer

I have changed the previous approach of using GH concurrency to the approach of using a single runner to not lose any execution during the process. Now we are working 3 people running e2e tests, and it could produce longer delays waiting for the resources.
It's true that we have "higher" concurrency than usually . With e2e tests migration, we are enqueueing more e2e tests and even thought I optimized the process, it's not enough.
Let's see if we need to address this with other solution or if it's only a temporal problem related with the migrations.

[v-shenoy]

Ah, got it. Probably won't be as much of a problem once the migrations are done.

The only cases where it might be a problem is when some PR requires the entire e2e suite to be run.

[JorTurFer]

The only cases where it might be a problem is when some PR requires the entire e2e suite to be run.

yes, and that is not really often

[zroubalik]

@v-shenoy do you think that you can also implement the activation* for this scaler?
#2800

#3383

[v-shenoy]

@zroubalik Sorry, I don't think I will be able to take this up. Have some personal things going on.

[JorTurFer]

I'll do it, no worries

[zroubalik]

@zroubalik Sorry, I don't think I will be able to take this up. Have some personal things going on.

No worries, focus on what's important!