Skip to content

Refine AGENTS.md#11854

Open
PerfectSlayer wants to merge 1 commit into
masterfrom
bbujon/ci
Open

Refine AGENTS.md#11854
PerfectSlayer wants to merge 1 commit into
masterfrom
bbujon/ci

Conversation

@PerfectSlayer

Copy link
Copy Markdown
Contributor

What Does This Do

This PR refines the AGENTS.md to avoid porting modules that are not supported yet by JUnit testing.

Motivation

Avoid trying to port modules to JUnit where the related features are missing. This tends to create a good amont of code that we will have a hard time to migrate later. Whereas if it uses Spock, we could migrate with the same tools and process than the original codebase migration.

Additional Notes

Contributor Checklist

  • Format the title according to the contribution guidelines
  • Assign the type: and (comp: or inst:) labels in addition to any other useful labels
  • Avoid using close, fix, or any linking keywords when referencing an issue
    Use solves instead, and assign the PR milestone to the issue
  • Update the CODEOWNERS file on source file addition, migration, or deletion
  • Update public documentation with any new configuration flags or behaviors
  • Add your completed PR to the merge queue by commenting /merge. You can also:
    • Customize the commit message associated with the merge with /merge --commit-message "..."
    • Remove your PR from the merge queue with /merge -c
    • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
    • Get more information in this doc

Jira ticket: [PROJ-IDENT]

@PerfectSlayer PerfectSlayer requested a review from a team as a code owner July 3, 2026 14:02
@PerfectSlayer PerfectSlayer requested a review from ygree July 3, 2026 14:02
@PerfectSlayer PerfectSlayer added type: documentation tag: no release notes Changes to exclude from release notes labels Jul 3, 2026
@datadog-prod-us1-3

This comment has been minimized.

@dd-octo-sts

dd-octo-sts Bot commented Jul 3, 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.01 s [-1.1%; +0.3%] (no difference)
startup:insecure-bank:tracing:Agent 13.02 s 13.02 s [-0.7%; +0.6%] (no difference)
startup:petclinic:appsec:Agent 16.85 s 16.67 s [+0.2%; +1.9%] (maybe worse)
startup:petclinic:iast:Agent 16.89 s 16.40 s [-1.5%; +7.4%] (no difference)
startup:petclinic:profiling:Agent 16.80 s 16.87 s [-1.5%; +0.6%] (no difference)
startup:petclinic:sca:Agent 16.93 s 16.76 s [-0.3%; +2.3%] (no difference)
startup:petclinic:tracing:Agent 16.04 s 15.91 s [-0.3%; +1.9%] (no difference)

Commit: 09a4a7f5 · 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: no release notes Changes to exclude from release notes type: documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants