Skip to content
vertx-core (4.x)

Fix HTTP/1.1 server connection close header processing that close the connection too early #261

Sign in to view logs

Fix HTTP/1.1 server connection close header processing that close the connection too early

Fix HTTP/1.1 server connection close header processing that close the connection too early #261

Triggered via pull request August 9, 2023 13:35
@vietjvietj
synchronize #4804
server-connection-close-4.x
Status Success
Total duration 21m 58s
Artifacts –

ci-4.x.yml

on: pull_request
Matrix: Run tests
Deploy to OSSRH
0s
Deploy to OSSRH
Fit to window
Zoom out
Zoom in

Annotations

25 errors and 5 warnings
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
too many aardvarks!
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
testComplete called after test has completed
Run tests (ubuntu-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8)
too many aardvarks!
Run tests (ubuntu-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8)
testComplete called after test has completed
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
too many aardvarks!
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
testComplete called after test has completed
Run tests (ubuntu-latest, 17)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 17)
too many aardvarks!
Run tests (ubuntu-latest, 17)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 17)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 17)
testComplete called after test has completed
Run tests (windows-latest, 8)
testComplete called after test has completed
Run tests (windows-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (windows-latest, 8)
too many aardvarks!
Run tests (windows-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (windows-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Run tests (ubuntu-latest, 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Run tests (ubuntu-latest, 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Run tests (windows-latest, 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/