Skip to content

Experiment with detecting overlapping-output-failure#12035

Draft
bric3 wants to merge 2 commits into
masterfrom
bdu/explore-overlapping-output-failure
Draft

Experiment with detecting overlapping-output-failure#12035
bric3 wants to merge 2 commits into
masterfrom
bdu/explore-overlapping-output-failure

Conversation

@bric3

@bric3 bric3 commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

⚠️Not ready for review, it's an experiment. I'm just creating a PR draft to trac work better. I just reased over the latest master.

What Does This Do

Motivation

Additional Notes

Contributor Checklist

Jira ticket: [PROJ-IDENT]

bric3 added 2 commits July 22, 2026 16:30
Motivation:
The build correctness requires that tasks don't overlap accidentaly.
However today there's no way to make gradle detect and fail the build
when tasks have overlapping outputs.

* Gradle detects overlapping outputs internally and disables caching for
  those tasks, but never fails the build — this has been an
  gradle/gradle#9080, explicitly requested by
  Google engineers at KotlinConf, still unimplemented as of 2024.

* There's a --warning-mode=fail but it fails for every warning, and
  NEED TO VERIFY may not trigger a failure on task dependency
  overlapping output warnings.

* https://github.com/gradle/develocity-build-validation-scripts tooling
  surfaces overlapping outputs visually in build scan timelines, but
  don't act during the build.

# Conflicts:
#	buildSrc/build.gradle.kts

# Conflicts:
#	buildSrc/build.gradle.kts
@bric3 bric3 added the tag: do not merge Do not merge changes label Jul 22, 2026
@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 57.37% (-0.02%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: f562614 | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite Status
Startup 🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results
Scenario Candidate master Δ (95% CI of mean)
startup:insecure-bank:iast:Agent 13.96 s 14.00 s [-1.1%; +0.6%] (no difference)
startup:insecure-bank:tracing:Agent 12.91 s 12.98 s [-1.3%; +0.1%] (no difference)
startup:petclinic:appsec:Agent 17.43 s 17.21 s [+0.2%; +2.3%] (maybe worse)
startup:petclinic:iast:Agent 17.44 s 16.93 s [-1.5%; +7.5%] (no difference)
startup:petclinic:profiling:Agent 17.25 s 17.23 s [-1.1%; +1.3%] (no difference)
startup:petclinic:sca:Agent 17.44 s 17.39 s [-0.7%; +1.2%] (no difference)
startup:petclinic:tracing:Agent 16.42 s 16.61 s [-2.1%; -0.2%] (maybe better)

Commit: f5626149 · CI Pipeline · Benchmarking Platform UI


Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tag: do not merge Do not merge changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant