Closed smola closed 2 months ago
Baseline | Candidate | |
---|---|---|
baseline_or_candidate | baseline | candidate |
git_branch | master | smola/jms-flaky |
git_commit_date | 1725274779 | 1725344132 |
git_commit_sha | 352673a4d2 | 0f230b38c7 |
release_version | 1.39.0-SNAPSHOT~352673a4d2 | 1.40.0-SNAPSHOT~0f230b38c7 |
Found 0 performance improvements and 0 performance regressions! Performance is the same for 47 metrics, 16 unstable metrics.
Baseline | Candidate | |
---|---|---|
baseline_or_candidate | baseline | candidate |
end_time | 2024-09-03T06:26:34 | 2024-09-03T06:33:23 |
git_branch | master | smola/jms-flaky |
git_commit_date | 1725274779 | 1725344132 |
git_commit_sha | 352673a4d2 | 0f230b38c7 |
release_version | 1.39.0-SNAPSHOT~352673a4d2 | 1.40.0-SNAPSHOT~0f230b38c7 |
start_time | 2024-09-03T06:26:20 | 2024-09-03T06:33:09 |
Found 0 performance improvements and 1 performance regressions! Performance is the same for 11 metrics, 16 unstable metrics.
scenario | Δ mean http_req_duration | Δ mean throughput | candidate mean http_req_duration | candidate mean throughput | baseline mean http_req_duration | baseline mean throughput |
---|---|---|---|---|---|---|
scenario:load:petclinic:profiling | worse [+32.215µs; +83.672µs] or [+2.173%; +5.644%] |
unstable [-813.991op/s; +339.917op/s] or [-25.437%; +10.622%] |
1.540ms | 2962.963op/s | 1.482ms | 3200.000op/s |
Baseline | Candidate | |
---|---|---|
baseline_or_candidate | baseline | candidate |
git_branch | master | smola/jms-flaky |
git_commit_date | 1725274779 | 1725344132 |
git_commit_sha | 352673a4d2 | 0f230b38c7 |
release_version | 1.39.0-SNAPSHOT~352673a4d2 | 1.40.0-SNAPSHOT~0f230b38c7 |
Found 0 performance improvements and 0 performance regressions! Performance is the same for 12 metrics, 0 unstable metrics.
What Does This Do
Some tests seem to be leaking messages to queues to the next test. Make sure each test uses unique topics/queues.
Motivation
Additional Notes
Contributor Checklist
type:
and (comp:
orinst:
) labels in addition to any usefull labelsclose
,fix
or any linking keywords when referencing an issue.Use
solves
instead, and assign the PR milestone to the issue