Skip to content

SLO: migrate comparisons and reports to Action v3 - #300

Draft
KirillKurdyukov wants to merge 3 commits into
claude/simplify-pr-291-0ea485from
ci/slo-v3-20261021
Draft

KirillKurdyukov wants to merge 3 commits into
claude/simplify-pr-291-0ea485from
ci/slo-v3-20261021

Conversation

@KirillKurdyukov

@KirillKurdyukov KirillKurdyukov commented Oct 21, 2026 •

Copy link
Copy Markdown

Summary

  • Stack this Action v3 follow-up on Migrate SLO tests to ydb-slo-action (simplified workload) #294, targeting claude/simplify-pr-291-0ea485 at unchanged 76140011b4135373ce0344bc745b86649e18f0b4. The colleague's branch is not modified.
  • Keep the existing PHP workload source, SDK calls, metrics, thresholds, 600-second duration and 1000/100 read/write RPS. Select workload_type: table.
  • Always build the selected baseline SDK independently, using the shared current workload harness. A baseline build failure fails the job; there is no fallback to the current image.
  • Keep same-repository reporting direct and fork reporting privileged, without checking out PR code in the privileged publisher. Use Action v3 label cleanup instead of duplicate scripts.

Dependency

Init is pinned to verified Action commit d66bd1e10f893e5f70d542c4430a3cffb6d6f9f8 from ydb-platform/ydb-slo-action#81 until its legacy telemetry fixes land in v3.

Earlier SDK verification

  • Both workflows pass actionlint with the real custom runner configuration.
  • git diff --check passes.
  • Native baseline/current SLO verification remains pending and will be attached to this draft.

Current workload metric contract

Use only existing workload sdk.* counters and successful-operation latency Gauges. workload_type selects table (default), topic, or topic_tx; it does not select a metric format. No SDK convention instruments or native/legacy schema split are supported by this change.

Init pins Action PR81 at immutable d66bd1e10f893e5f70d542c4430a3cffb6d6f9f8. Table retains independently built current/baseline SDKs and requires successful read AND write observations for both refs. Topic requires read/write and Topic-tx transaction observations, including any supplied baseline. Existing actual scenario names, SDK source, metrics YAML, retries, deadlines, load, data checks and fatal process criteria are unchanged.

The selector/pin changes pass actionlint across all seven SDK workflows. Action has135/135 Linux tests, clean static checks/bundle, public exact-SHA verify, independent gate approval and real SDK/OTLP PASS/FAIL/INVALID evidence. These are not a claim that historical native SDK runtime failures were fixed or that new SDK CI is green.

All PRs remain draft; no merge, ready transition or v3 tag move. Default-branch publisher changes are not active merely because this branch was pushed.

Related migration PRs

@codecov

codecov Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.67%. Comparing base (7614001) to head (ff52e48).

Additional details and impacted files

Impacted file tree graph

@@                       Coverage Diff                        @@
##             claude/simplify-pr-291-0ea485     #300   +/-   ##
================================================================
  Coverage                            52.67%   52.67%           
  Complexity                             989      989           
================================================================
  Files                                   66       66           
  Lines                                 2690     2690           
================================================================
  Hits                                  1417     1417           
  Misses                                1273     1273           
Components Coverage Δ
Native SDK 52.67% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions github-actions Bot removed the SLO Run SLO tests label Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant