Nelson Osacky

Thanks for the repro :D i should have noticed since its in this project. Will take a look!

Related issue: calling `isPresent` eagerly evaluates properties: https://github.com/gradle/gradle/issues/13932 This feature may help alleviate this in the future: https://github.com/gradle/gradle/issues/13401

Hey, interesting bug. I'm not sure there is any mapping or guarantee between the `configs` and the build variants. If you set the path explicitly does it work? What would...

Sorry it took so long to look at this bug. This feature isn't supported. I could build it if needed, but maybe additionalTestApks is a better option? https://runningcode.github.io/fladle/configuration/#additionaltestapks

Hey sorry this took a while to get a real response. I took a first stab at this and realized it is impossible to know if the variants should auto-detect...

Thanks for the feature request. It would be really nice. If you are a customer of Gradle Enterprise please directly ask Gradle to support this feature. It is not currently...

Thanks for filing. This is a good idea. 👍 I'll try to take a look at your solution soon.

Hey, sorry there's no ETA on this. Sorry I haven't got a chance to look at it. October is a busy month for me but perhaps later I will be...

Yes, you can check the xml report. It will indicate which tests were flaky.

Thanks for filing this @ccjernigan and for the details. This stack trace actually comes from flank itself here: https://github.com/Flank/flank/blob/master/test_runner/src/main/kotlin/ftl/args/ArgsHelper.kt#L197 I think you might be better off filing the bug over...