Pass explicit JUnit outfile to critest.exe in Windows workflow.
Following kubernetes-sigs/cri-tools#910 the Ginkgo reporters are left configured with default settings and thus do not generate a JUnit report file unless we explicitly pass a path for the outfile in the Windows workflow when calling critest.exe. Signed-off-by: Nashwan Azhari <nazhari@cloudbasesolutions.com>
This commit is contained in:
parent
68d9d462c9
commit
09c2c2a753
2
.github/workflows/windows-periodic.yml
vendored
2
.github/workflows/windows-periodic.yml
vendored
@ -205,7 +205,7 @@ jobs:
|
|||||||
ssh -i $HOME/.ssh/id_rsa ${{ env.SSH_OPTS }} azureuser@${{ env.VM_PUB_IP }} "powershell.exe -command { C:\containerd\bin\containerd.exe --log-level=debug --log-file=C:/logs/containerd.log --service-name containerd --register-service ; Set-Service containerd -StartupType Automatic; Start-Service containerd }"
|
ssh -i $HOME/.ssh/id_rsa ${{ env.SSH_OPTS }} azureuser@${{ env.VM_PUB_IP }} "powershell.exe -command { C:\containerd\bin\containerd.exe --log-level=debug --log-file=C:/logs/containerd.log --service-name containerd --register-service ; Set-Service containerd -StartupType Automatic; Start-Service containerd }"
|
||||||
ssh -i $HOME/.ssh/id_rsa ${{ env.SSH_OPTS }} azureuser@${{ env.VM_PUB_IP }} "sh.exe -s" <<EOF
|
ssh -i $HOME/.ssh/id_rsa ${{ env.SSH_OPTS }} azureuser@${{ env.VM_PUB_IP }} "sh.exe -s" <<EOF
|
||||||
sleep 5
|
sleep 5
|
||||||
c:/cri-tools/build/bin/critest.exe $SKIP --runtime-endpoint='npipe://./pipe/containerd-containerd' --test-images-file='c:/cri-test-images.yaml' --report-dir='c:/Logs' | tee c:/Logs/critest.log
|
c:/cri-tools/build/bin/critest.exe $SKIP --runtime-endpoint='npipe://./pipe/containerd-containerd' --test-images-file='c:/cri-test-images.yaml' --report-dir='c:/Logs' -ginkgo.junit-report="C:\Logs\junit_critest.xml" | tee c:/Logs/critest.log
|
||||||
EOF
|
EOF
|
||||||
|
|
||||||
- name: PullLogsFromWinNode
|
- name: PullLogsFromWinNode
|
||||||
|
Loading…
Reference in New Issue
Block a user