Skip to content

CI: Split up build flow to inject interop tests #601

CI: Split up build flow to inject interop tests

CI: Split up build flow to inject interop tests #601

Triggered via pull request October 31, 2024 09:05
Status Failure
Total duration 1m 4s
Artifacts 2

build.yml

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

Annotations

3 errors and 1 warning
test
Process completed with exit code 2.
MamIntegrationTest.XEP0313/MamIntegrationTest.mamTest (Normal): output/MamIntegrationTest.mamPageTest (Normal).log#L1
smack-inttest-two-yptrf@example.org/two-yptrf received an unexpected amount of messages in response to a MAM query. ==> expected: <1> but was: <0>
MamIntegrationTest.XEP0313/MamIntegrationTest.mamPageTest (Normal): output/MamIntegrationTest.mamPageTest (Normal).log#L1
Expected the first MAM response received by smack-inttest-two-yptrf@example.org/two-yptrf to NOT be complete (but it was). ==> expected: <false> but was: <true>
build (11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
XMPP debug logs
10.4 KB
monitoring Expired
28.1 MB