Skip to content

Issue #2212 Enhances validation of HTTP header names #67

Issue #2212 Enhances validation of HTTP header names

Issue #2212 Enhances validation of HTTP header names #67

Triggered via pull request November 18, 2024 05:09
Status Failure
Total duration 15m 7s
Artifacts

maven.yml

on: pull_request
Matrix: build
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Test Grizzly on JDK 11
Process completed with exit code 1.
Build Grizzly on JDK 11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@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 Grizzly on JDK 11
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Grizzly on JDK 11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test Grizzly on JDK 11
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/