Skip to content

Gatling performance test enhancements - HTTPS, path configuration, AWS SigV4 #6774

Gatling performance test enhancements - HTTPS, path configuration, AWS SigV4

Gatling performance test enhancements - HTTPS, path configuration, AWS SigV4 #6774

Triggered via pull request September 7, 2023 01:52
Status Success
Total duration 8m 33s
Artifacts
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (17, 0.16.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (17, 0.9.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (11, 0.9.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (11, 0.16.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/