Skip to content

Ensure that runner is unregistered on registration failure

Pedro Pombeiro requested to merge 26642-test-unregister-on-failure into master

What does this MR do?

It tests the scenario where the Runner is already registered with the Ruby app, but a subsequent failure causes it to abort. If --leave-runner was passed to the CLI, we should leave the runner, otherwise UnregisterRunner should be called.

Why was this MR needed?

To provide test coverage to areas of the code which have no coverage at all.

What's the best way to test this MR?

Look at the results of the CI build and run the test locally.

What are the relevant issue numbers?

Part of #26642 (closed)

Merge request reports