fix(ci): Prepare workflows for merge queue#902
Merged
Merged
Conversation
gtema
added this pull request to the merge queue
Jul 2, 2026
|
🦢 Load Test Results Goose Attack ReportPlan Overview
Request Metrics
Response Time Metrics
Status Code Metrics
Transaction Metrics
Scenario Metrics
|
gtema
removed this pull request from the merge queue due to a manual request
Jul 2, 2026
gtema
force-pushed
the
fix/merge-queue-ci
branch
4 times, most recently
from
July 2, 2026 14:39
c188029 to
e089b16
Compare
|
| Branch | fix/merge-queue-ci |
| Testbed | ubuntu-latest |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result nanoseconds (ns) (Result Δ%) | Upper Boundary nanoseconds (ns) (Limit %) |
|---|---|---|---|
| Command_Serde/apply/remove | 📈 view plot 🚷 view threshold | 135,480.00 ns(-52.16%)Baseline: 283,221.33 ns | 1,686,423.26 ns (8.03%) |
| Command_Serde/apply/set | 📈 view plot 🚷 view threshold | 144,460.00 ns(-38.31%)Baseline: 234,153.67 ns | 983,724.82 ns (14.69%) |
| Command_Serde/pack/delete | 📈 view plot 🚷 view threshold | 124.68 ns(+3.48%)Baseline: 120.49 ns | 142.24 ns (87.66%) |
| Command_Serde/pack/delete_index | 📈 view plot 🚷 view threshold | 112.09 ns(+2.13%)Baseline: 109.76 ns | 129.40 ns (86.62%) |
| Command_Serde/pack/set | 📈 view plot 🚷 view threshold | 209.82 ns(+8.58%)Baseline: 193.24 ns | 231.58 ns (90.61%) |
| Command_Serde/pack/set_index | 📈 view plot 🚷 view threshold | 112.11 ns(+2.34%)Baseline: 109.55 ns | 128.77 ns (87.06%) |
| Command_Serde/unpack/delete | 📈 view plot 🚷 view threshold | 201.90 ns(+4.69%)Baseline: 192.85 ns | 233.48 ns (86.47%) |
| Command_Serde/unpack/delete_index | 📈 view plot 🚷 view threshold | 157.54 ns(-1.74%)Baseline: 160.32 ns | 195.96 ns (80.40%) |
| Command_Serde/unpack/set | 📈 view plot 🚷 view threshold | 287.46 ns(+9.69%)Baseline: 262.06 ns | 324.38 ns (88.62%) |
| Command_Serde/unpack/set_index | 📈 view plot 🚷 view threshold | 175.57 ns(+10.30%)Baseline: 159.17 ns | 193.44 ns (90.76%) |
| Payload_encryption/pack/remove_cmd | 📈 view plot 🚷 view threshold | 123.88 ns(+6.39%)Baseline: 116.44 ns | 138.78 ns (89.26%) |
| Payload_encryption/pack/set_cmd | 📈 view plot 🚷 view threshold | 222.62 ns(+8.39%)Baseline: 205.40 ns | 271.81 ns (81.90%) |
| Payload_encryption/unpack/remove_cmd | 📈 view plot 🚷 view threshold | 214.03 ns(+4.25%)Baseline: 205.30 ns | 248.00 ns (86.30%) |
| Payload_encryption/unpack/set_cmd | 📈 view plot 🚷 view threshold | 302.91 ns(+10.12%)Baseline: 275.06 ns | 340.71 ns (88.91%) |
| Raft_1Node_Latency/prefix/1node | 📈 view plot 🚷 view threshold | 2,653,300.00 ns(-8.19%)Baseline: 2,890,072.97 ns | 6,573,432.09 ns (40.36%) |
| Raft_1Node_Latency/read/1node | 📈 view plot 🚷 view threshold | 44,364.00 ns(+349.57%)Baseline: 9,868.13 ns | 50,764.35 ns (87.39%) |
| Raft_1Node_Latency/remove/1node | 📈 view plot 🚷 view threshold | 385,010.00 ns(-29.73%)Baseline: 547,930.16 ns | 2,295,486.44 ns (16.77%) |
| Raft_1Node_Latency/write/1node | 📈 view plot 🚷 view threshold | 406,750.00 ns(-28.48%)Baseline: 568,723.75 ns | 2,128,606.52 ns (19.11%) |
| build_snapshot/default | 📈 view plot 🚷 view threshold | 120,600.00 ns(+13.88%)Baseline: 105,903.06 ns | 161,989.09 ns (74.45%) |
| fernet token/project | 📈 view plot 🚷 view threshold | 1,435.30 ns(+3.70%)Baseline: 1,384.10 ns | 1,620.91 ns (88.55%) |
| get_data_keyspace | 📈 view plot 🚷 view threshold | 0.31 ns(-0.94%)Baseline: 0.32 ns | 0.37 ns (84.73%) |
| get_db | 📈 view plot 🚷 view threshold | 0.31 ns(-1.11%)Baseline: 0.32 ns | 0.37 ns (84.68%) |
| get_fernet_token_timestamp/project | 📈 view plot 🚷 view threshold | 133.47 ns(-7.43%)Baseline: 144.18 ns | 179.14 ns (74.51%) |
| get_keyspace | 📈 view plot 🚷 view threshold | 4.40 ns(-6.65%)Baseline: 4.71 ns | 8.74 ns (50.27%) |
gtema
force-pushed
the
fix/merge-queue-ci
branch
2 times, most recently
from
July 2, 2026 15:20
169c6c5 to
4157179
Compare
- committed action was silently ignoring its merge_group override: crate-ci/committed reads the commits input, not a COMMITTED_REV env var, so on merge_group it kept using the default HEAD~..HEAD^2 range, which doesn't resolve on the queue's single-commit ref. - ci.yml and functional.yml gated required jobs behind pull_request path filters, so a required status check on those jobs would never report on PRs that don't touch matched paths, blocking merge forever. Both workflows now always trigger and use dorny/paths-filter in a new changes job to skip the actual work when nothing relevant changed, so the check always reports. Apparently due to the wrong filters the clippy job was not properly running, which is why unrelated clippy fixes are included. Signed-off-by: Artem Goncharov <Artem.goncharov@gmail.com>
gtema
enabled auto-merge
July 2, 2026 16:02
gtema
disabled auto-merge
July 2, 2026 16:09
gtema
enabled auto-merge
July 2, 2026 16:09
gtema
disabled auto-merge
July 2, 2026 16:18
gtema
enabled auto-merge
July 2, 2026 16:18
gtema
disabled auto-merge
July 2, 2026 16:23
gtema
enabled auto-merge
July 2, 2026 16:23
gtema
disabled auto-merge
July 2, 2026 16:25
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
crate-ci/committed reads the commits input, not a COMMITTED_REV env
var, so on merge_group it kept using the default HEAD~..HEAD^2 range,
which doesn't resolve on the queue's single-commit ref.
path filters, so a required status check on those jobs would never
report on PRs that don't touch matched paths, blocking merge forever.
Both workflows now always trigger and use dorny/paths-filter in a new
changes job to skip the actual work when nothing relevant changed,
so the check always reports.
Apparently due to the wrong filters the clippy job was not properly
running, which is why unrelated clippy fixes are included.
Signed-off-by: Artem Goncharov Artem.goncharov@gmail.com