dependency verification error reporting incorrect task name

[mathjeff]

Expected Behavior

When Gradle observes a dependency verification error and Gradle outputs the name of the failing task, that task should be the failing task

Current Behavior

We've encountered a case where Gradle outputs a different task name than the one required to reproduce the error.
See the repro at https://github.com/mathjeff/gradle-samples/tree/master/signature-verification-reports-wrong-task

Context

When we encounter a dependency verification error, it helps us to investigate it and address it if we can easily reproduce it by running ./gradlew someTask. It was more difficult for us to diagnose this error because the task listed by Gradle wasn't the task required to reproduce the error.

We originally observed this behavior with the change at https://android-review.googlesource.com/c/platform/frameworks/support/+/2105845/5 and build error at https://ci.android.com/builds/pending/P35431944/androidx_incremental/latest/view/logs/build_error.log .

Steps to Reproduce

I've uploaded the simplest repro I could find to https://github.com/mathjeff/gradle-samples/tree/master/signature-verification-reports-wrong-task

Your Environment

Initial problematic scan which printed the wrong task name when running ./gradlew buildOnServer
https://scans.gradle.com/s/lmhmbzzhee7cu

Passing scan when running just the task name mentioned in the previous scan (./gradlew :compose:foundation:foundation-lint:jar)
https://scans.gradle.com/s/ejdnwya45w3u2

Failing scan when instead running :compose:foundation:foundation-lint:ktlint
https://gradle.com/s/6bv45bhs56nto