Skip to content

[v6] Fix wrong serialization of PKESK v6 for x25519/x448 #451

[v6] Fix wrong serialization of PKESK v6 for x25519/x448

[v6] Fix wrong serialization of PKESK v6 for x25519/x448 #451

Triggered via pull request March 21, 2024 09:19
Status Failure
Total duration 2m 56s
Artifacts

benchmark.yml

on: pull_request
Time and memory usage benchmark
2m 47s
Time and memory usage benchmark
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Memory usage benchmark (attempt #1): performance regression detected for test 'openpgp.encrypt/decrypt (CFB, text @ 10MB, with unauthenticated streaming)': test/benchmarks/memory_usage.js#L1
Previous value was 129.91 and current value is 145.04. It is 1.1164652451697328x worse, exceeding the failure threshold of 1.10.
Time and memory usage benchmark
1 of 1 alerts exceeded the failure threshold `1.10` specified by fail-threshold input: # **Performance Alert** Possible performance regression was detected for benchmark **'Memory usage benchmark'**. Benchmark result of this commit is worse than the previous benchmark result exceeding threshold `1.02`. | Benchmark suite | Current: 38f445091e4ad8fcb90aa905f66e2ba00c8160ad | Previous: 147d043a32e27ddfec82f5efffb790ac7803c34f | Ratio | |-|-|-|-| | `openpgp.encrypt/decrypt (CFB, text @ 10MB, with unauthenticated streaming)` | `145.04` MB (`heapTotal: 57.00, heapUsed: 29.26, external: 43.45, arrayBuffers: 41.40`) | `129.91` MB (`heapTotal: 48.46, heapUsed: 14.02, external: 30.35, arrayBuffers: 9.40`) | `1.12` | This comment was automatically generated by [workflow](https://github.com/openpgpjs/openpgpjs/actions?query=workflow%3APerformance%20Regression%20Test).