Run Kotlin macOS tests without EngFlow

[jpsim]

These jobs fail when run with remote execution but pass when run directly on GitHub Actions agents.

Signed-off-by: JP Simard jp@jpsim.com

[jpsim]

The android_tests / kotlin_tests_mac job is now passing:

//test/kotlin/io/envoyproxy/envoymobile:engine_builder_test              PASSED in 5.9s
//test/kotlin/io/envoyproxy/envoymobile:grpc_request_headers_builder_test PASSED in 2.7s
//test/kotlin/io/envoyproxy/envoymobile:grpc_stream_test                 PASSED in 2.4s
//test/kotlin/io/envoyproxy/envoymobile:headers_builder_test             PASSED in 2.3s
//test/kotlin/io/envoyproxy/envoymobile:pulse_client_impl_test           PASSED in 5.8s
//test/kotlin/io/envoyproxy/envoymobile:request_headers_builder_test     PASSED in 3.1s
//test/kotlin/io/envoyproxy/envoymobile:response_headers_test            PASSED in 2.6s
//test/kotlin/io/envoyproxy/envoymobile:retry_policy_mapper_test         PASSED in 1.1s
//test/kotlin/io/envoyproxy/envoymobile/stats:element_test               PASSED in 2.2s
//test/kotlin/io/envoyproxy/envoymobile/stats:tags_builder_test          PASSED in 2.3s

It seems increasingly likely that something in the remote execution environment is responsible for these test failures.

@lfpino how can we troubleshoot CI failures that only happen with EngFlow remote execution?

[lfpino]

What kind of failure are you observing? Is it similar to #2007?

If you're suspecting an Engflow infrastructure failure please page us using envoy-vyuw3pbm@engflow.pagerduty.com and our oncall will get on it.

Can you please open an issue in the meantime with some of the failure links and I'll take a look?

[jpsim]

Can you please open an issue in the meantime with some of the failure links and I'll take a look?

Sure, I'll open two issues actually, one for this and another for the integration tests which I also had to disable similarly.

[jpsim]

@lfpino I've filed #2019 & #2020 for the two situations in which we've had to disable remote execution due to test failures. If you'd like me to send an email to the pager duty address to trigger your on-call process I'm happy to do that, but as of this PR these two issues are mitigated so it's not urgent from our perspective.

[lfpino]

Thanks @jpsim, I'll take a look so no need to page the oncall, even if it's not urgent, this isn't ideal so let's make sure we can fix it back in Engflow soon.