Add EdDSA signature verification step to detect and avoid outputting faulty signatures #31
larabrbenchmark.yml
on: pull_request
Time and memory usage benchmark
2m 55s
Annotations
3 errors
|
Time benchmark (attempt #1): performance regression detected for test 'openpgp.generateKey':
test/benchmarks/time.js#L1
Previous value was 84.39 and current value is 29.49. It is 2.861648016276704x worse, exceeding the failure threshold of 1.50.
|
|
Time benchmark (attempt #1): performance regression detected for test 'openpgp.sign':
test/benchmarks/time.js#L1
Previous value was 340 and current value is 104. It is 3.269230769230769x worse, exceeding the failure threshold of 1.50.
|
|
Time and memory usage benchmark
2 of 2 alerts exceeded the failure threshold `1.50` specified by fail-threshold input:
# **Performance Alert**
Possible performance regression was detected for benchmark **'Time benchmark'**.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold `1.30`.
| Benchmark suite | Current: 624debed0a122bb793c37e0264edbb218ef2152c | Previous: 743217216c654bb9ab961fec2e42fe20b153f5b5 | Ratio |
|-|-|-|-|
| `openpgp.generateKey` | `29.49` ops/sec (`±2.49%`) | `84.39` ops/sec (`±2.29%`) | `2.86` |
| `openpgp.sign` | `104` ops/sec (`±2.47%`) | `340` ops/sec (`±2.15%`) | `3.27` |
This comment was automatically generated by [workflow](https://github.com/ProtonMail/openpgpjs/actions?query=workflow%3APerformance%20Regression%20Test).
|