New (currently failing) test for clashing direct and indirect dependencies #347
GitHub Actions / Test Results (Ubuntu)
failed
Sep 20, 2025 in 0s
1 fail, 224 pass in 4m 24s
23 files 23 suites 4m 24s ⏱️
225 tests 224 ✅ 0 💤 1 ❌
249 runs 248 ✅ 0 💤 1 ❌
Results for commit cbc9f4e.
Annotations
Check warning on line 0 in build.buf.gradle.LintWithProtobufGradleTest
github-actions / Test Results (Ubuntu)
lint a file with an implementation dependency and the same package as an indirect protobuf dependency() (build.buf.gradle.LintWithProtobufGradleTest) failed
build/test-results/test/TEST-build.buf.gradle.LintWithProtobufGradleTest.xml [took 0s]
Raw output
org.gradle.testkit.runner.UnexpectedBuildFailure: Unexpected build execution failure in /tmp/junit-9906377684898430205 with arguments [-PprotobufGradleVersion=0.9.5, -PprotobufVersion=4.32.1, -PkotlinVersion=2.1.21, -PandroidGradleVersion=7.3.1, --configuration-cache, check]
Output:
Calculating task graph as no cached configuration is available for tasks: check
> Task :protobufDummy UP-TO-DATE
> Task :extractTestProto
> Task :processTestResources NO-SOURCE
> Task :extractIncludeTestProto
> Task :extractIncludeProto
> Task :extractProto
> Task :generateTestProto NO-SOURCE
> Task :createSymLinksToModules
> Task :writeWorkspaceYaml
> Task :processResources
> Task :bufFormatCheck
> Task :bufLint FAILED
> Task :generateProto
[Incubating] Problems report is available at: file:///tmp/junit-9906377684898430205/build/reports/problems/problems-report.html
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':bufLint'.
> Some Protobuf files had lint violations:
src-main-proto/buf/test/v1/test.proto:19:8:google/protobuf/any.proto is contained in multiple modules:
path: "build-extracted--include--protos-main"
path: "build-extracted--protos-main"
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.14.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 846ms
10 actionable tasks: 10 executed
Configuration cache entry stored.
at app//org.gradle.testkit.runner.internal.DefaultGradleRunner.lambda$build$2(DefaultGradleRunner.java:274)
at app//org.gradle.testkit.runner.internal.DefaultGradleRunner.run(DefaultGradleRunner.java:367)
at app//org.gradle.testkit.runner.internal.DefaultGradleRunner.build(DefaultGradleRunner.java:272)
at app//build.buf.gradle.AbstractBufIntegrationTest$WrappedRunner.build(AbstractBufIntegrationTest.kt:62)
at app//build.buf.gradle.LintTestUtilities.assertSuccess(AbstractLintTest.kt:71)
at app//build.buf.gradle.LintWithProtobufGradleTest.lint a file with an implementation dependency and the same package as an indirect protobuf dependency(LintWithProtobufGradleTest.kt:64)
at java.base@11.0.28/java.lang.reflect.Method.invoke(Method.java:566)
at java.base@11.0.28/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base@11.0.28/java.util.ArrayList.forEach(ArrayList.java:1541)
Loading