Skip to content
Performance Regression Test

Reorg EdgeRef and NodeRef and CI Fixes #48

Sign in to view logs

Reorg EdgeRef and NodeRef and CI Fixes

Reorg EdgeRef and NodeRef and CI Fixes #48

Triggered via pull request December 1, 2023 15:48
@bcollazobcollazo
synchronize #262
feature/refactor
Status Failure
Total duration 1m 17s
Artifacts –

perf-regression.yml

on: pull_request
build-python-and-test-performance
1m 6s
build-python-and-test-performance
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Benchmark (attempt #null): performance regression detected for test 'tests/integration_tests/test_speed.py::test_alphabeta_speed'
Previous value was 4.175247998207542 and current value is 0.6157200094029885. It is 6.781082203672292x worse, exceeding the failure threshold of 1.50.
build-python-and-test-performance
1 of 1 alerts exceeded the failure threshold `1.50` specified by fail-threshold input: # **Performance Alert** Possible performance regression was detected for benchmark. Benchmark result of this commit is worse than the previous benchmark result exceeding threshold `1.30`. | Benchmark suite | Current: 911505b0393ade41aa4b08008025a0bb1be16173 | Previous: 2ae972fb72ddcdf9c0793478647b9137f3b76b3c | Ratio | |-|-|-|-| | `tests/integration_tests/test_speed.py::test_alphabeta_speed` | `0.6157200094029885` iter/sec (`stddev: 1.4444843852101494`) | `4.175247998207542` iter/sec (`stddev: 0.3184915924761945`) | `6.78` | This comment was automatically generated by [workflow](https://github.com/bcollazo/catanatron/actions?query=workflow%3APerformance%20Regression%20Test).
build-python-and-test-performance
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/