Skip to content

cut v2.47.0

cut v2.47.0 #3467

GitHub Actions / JUnit Test Report failed Feb 14, 2025 in 0s

23 tests run, 21 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 ensuring CRC cluster is running: $env:CRC_DISABLE_UPDATE_CHECK=true; crc setup expected succeeds but it did not
Raw output
Step ensuring CRC cluster is running: $env:CRC_DISABLE_UPDATE_CHECK=true; crc setup expected succeeds but it did not

Check failure on line 1 in CRC start usecase

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

CRC start usecase

Step executing "man -P cat crc" fails: command 'man -P cat crc', expected to fail, exited with exit code: 0
Command stdout:
Raw output
Step executing "man -P cat crc" fails: command 'man -P cat crc', expected to fail, exited with exit code: 0
Command stdout: 
Command stderr: help : Parameter cannot be processed because the parameter name 'P' is ambiguous. Possible matches include: -Path 
-Parameter -PipelineVariable.
At line:1 char:5
+ man -P cat crc
+     ~~
    + CategoryInfo          : InvalidArgument: (:) [help], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameter,help