Skip to content

Avoid waiting forever on API response #1458

Avoid waiting forever on API response

Avoid waiting forever on API response #1458

GitHub Actions / JUnit Test Report failed Jan 16, 2025 in 0s

39 tests run, 37 passed, 0 skipped, 2 failed.

Annotations

Check failure on line 1 in Deploy a java application using Eclipse JKube in pod and then verify it's health

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

Deploy a java application using Eclipse JKube in pod and then verify it's health

Step stdout should contain "{"applicationName":"JKube","message":"Subatomic JKube really whips the llama's ass!"}": output did not match. Expected: '{"applicationName":"JKube","message":"Subatomic JKube really whips the llama's ass!"}', Actual: '<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>'

Check failure on line 1 in CRC config set and get preset property (positive cases) #2

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

CRC config set and get preset property (positive cases) #2

Step setting config property "preset" to value "okd" succeeds: command 'crc config set preset okd', expected to succeed, exited with exit code: 1
Command stdout: 
Command stderr: level=debug msg="CRC version: 2.46.0+6225a0\n"
level=debug msg="OpenShift version: 4.17.10\n"
level=debug msg="MicroShift version: 4.17.10\n"
level=debug msg="Running 'crc config set'"
Value 'okd' for configuration property 'preset' is invalid, reason: preset 'okd' is not supported on arm64 architecture, please use different preset value