feat(tempest): Add tempest identity compatibility verify test#998
Merged
Conversation
|
🦢 Load Test Results Goose Attack ReportPlan Overview
Request Metrics
Response Time Metrics
Status Code Metrics
Transaction Metrics
Scenario Metrics
|
f6a0b5e to
400a4e8
Compare
|
| Branch | claude/skaffold-identity-tempest-test-kxtqhj |
| 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 | 151,490.00 ns(-26.19%)Baseline: 205,234.59 ns | 669,749.02 ns (22.62%) |
| Command_Serde/apply/set | 📈 view plot 🚷 view threshold | 142,990.00 ns(-45.17%)Baseline: 260,780.84 ns | 1,244,421.28 ns (11.49%) |
| Command_Serde/pack/delete | 📈 view plot 🚷 view threshold | 121.52 ns(-0.55%)Baseline: 122.20 ns | 144.21 ns (84.27%) |
| Command_Serde/pack/delete_index | 📈 view plot 🚷 view threshold | 109.55 ns(+0.33%)Baseline: 109.20 ns | 128.16 ns (85.48%) |
| Command_Serde/pack/set | 📈 view plot 🚷 view threshold | 191.14 ns(-3.76%)Baseline: 198.61 ns | 238.72 ns (80.07%) |
| Command_Serde/pack/set_index | 📈 view plot 🚷 view threshold | 109.57 ns(+0.44%)Baseline: 109.09 ns | 127.91 ns (85.66%) |
| Command_Serde/unpack/delete | 📈 view plot 🚷 view threshold | 204.11 ns(+5.86%)Baseline: 192.81 ns | 235.89 ns (86.53%) |
| Command_Serde/unpack/delete_index | 📈 view plot 🚷 view threshold | 162.72 ns(+0.91%)Baseline: 161.25 ns | 197.41 ns (82.43%) |
| Command_Serde/unpack/set | 📈 view plot 🚷 view threshold | 275.71 ns(+1.59%)Baseline: 271.39 ns | 324.90 ns (84.86%) |
| Command_Serde/unpack/set_index | 📈 view plot 🚷 view threshold | 158.99 ns(-0.26%)Baseline: 159.41 ns | 193.75 ns (82.06%) |
| Payload_encryption/pack/remove_cmd | 📈 view plot 🚷 view threshold | 129.55 ns(+11.58%)Baseline: 116.10 ns | 139.21 ns (93.06%) |
| Payload_encryption/pack/set_cmd | 📈 view plot 🚷 view threshold | 199.78 ns(-1.65%)Baseline: 203.13 ns | 254.23 ns (78.58%) |
| Payload_encryption/unpack/remove_cmd | 📈 view plot 🚷 view threshold | 212.77 ns(+3.64%)Baseline: 205.29 ns | 255.33 ns (83.33%) |
| Payload_encryption/unpack/set_cmd | 📈 view plot 🚷 view threshold | 281.77 ns(-1.31%)Baseline: 285.52 ns | 349.14 ns (80.70%) |
| Raft_1Node_Latency/prefix/1node | 📈 view plot 🚷 view threshold | 3,523,400.00 ns(+28.97%)Baseline: 2,732,010.78 ns | 6,071,718.11 ns (58.03%) |
| Raft_1Node_Latency/read/1node | 📈 view plot 🚷 view threshold | 41,170.00 ns(+3.81%)Baseline: 39,659.20 ns | 53,331.24 ns (77.20%) |
| Raft_1Node_Latency/remove/1node | 📈 view plot 🚷 view threshold | 391,660.00 ns(-35.69%)Baseline: 609,032.81 ns | 2,461,581.69 ns (15.91%) |
| Raft_1Node_Latency/write/1node | 📈 view plot 🚷 view threshold | 409,490.00 ns(-36.02%)Baseline: 640,057.50 ns | 2,954,730.62 ns (13.86%) |
| build_snapshot/default | 📈 view plot 🚷 view threshold | 112,550.00 ns(-2.24%)Baseline: 115,127.22 ns | 158,486.28 ns (71.02%) |
| fernet token/project | 📈 view plot 🚷 view threshold | 1,483.10 ns(+4.16%)Baseline: 1,423.84 ns | 1,652.46 ns (89.75%) |
| get_data_keyspace | 📈 view plot 🚷 view threshold | 0.31 ns(-1.86%)Baseline: 0.32 ns | 0.37 ns (84.90%) |
| get_db | 📈 view plot 🚷 view threshold | 0.31 ns(-1.96%)Baseline: 0.32 ns | 0.37 ns (84.72%) |
| get_fernet_token_timestamp/project | 📈 view plot 🚷 view threshold | 136.07 ns(-4.73%)Baseline: 142.82 ns | 174.54 ns (77.96%) |
| get_keyspace | 📈 view plot 🚷 view threshold | 4.36 ns(-9.02%)Baseline: 4.79 ns | 9.62 ns (45.37%) |
42b33a7 to
19af9fc
Compare
Add a third skaffold module that runs the tempest identity v3 test suite against both keystone-rs and keystone-py (already deployed side by side by the keystone module), packaged as a new tempest-identity image built from tools/Dockerfile.tempest. Not every v3 operation is implemented by keystone-rs yet, so this runs and reports independently of the main verify suite (skaffold verify -m tempest) and is invoked as a non-blocking, continue-on-error step in CI. Failing test IDs are printed per target in the pod logs and, in CI, collected into a job summary and an uploaded log artifact so compatibility gaps and regressions can be tracked over time without gating merges. Assisted-by: Claude <noreply@anthropic.com> Signed-off-by: Artem Goncharov <artem.goncharov@gmail.com>
19af9fc to
976225c
Compare
Open
This was referenced Jul 16, 2026
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.
Add a third skaffold module that runs the tempest identity v3 test
suite against both keystone-rs and keystone-py (already deployed
side by side by the keystone module), packaged as a new
tempest-identity image built from tools/Dockerfile.tempest.
Not every v3 operation is implemented by keystone-rs yet, so this
runs and reports independently of the main verify suite
(skaffold verify -m tempest) and is invoked as a non-blocking,
continue-on-error step in CI. Failing test IDs are printed per
target in the pod logs and, in CI, collected into a job summary and
an uploaded log artifact so compatibility gaps and regressions can
be tracked over time without gating merges.
Signed-off-by: Claude noreply@anthropic.com