Skip to content

Fix incorrect null value for xml attributes when the expected field type is an array #470

Fix incorrect null value for xml attributes when the expected field type is an array

Fix incorrect null value for xml attributes when the expected field type is an array #470

Triggered via pull request October 30, 2024 11:09
Status Failure
Total duration 26m 34s
Artifacts
Run StdLib Workflow  /  Build with bal test graalvm on Ubuntu
16m 48s
Run StdLib Workflow / Build with bal test graalvm on Ubuntu
Run StdLib Workflow  /  Build with bal test graalvm on Windows
26m 20s
Run StdLib Workflow / Build with bal test graalvm on Windows
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Run StdLib Workflow / Build with bal test graalvm on Ubuntu
Process completed with exit code 1.
Run StdLib Workflow / Build with bal test graalvm on Windows
Exception calling "SetPageFileSize" with "3" argument(s): "The operation completed successfully" At D:\a\_actions\al-cheb\configure-pagefile-action\v1.3\scripts\SetPageFileSize.ps1:193 char:1 + [Util.PageFile]::SetPageFileSize($minimumSize, $maximumSize, $diskRoo ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : Win32Exception
Run StdLib Workflow / Build with bal test graalvm on Windows
Process completed with exit code 1.
Run StdLib Workflow / Build with bal test graalvm on Ubuntu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run StdLib Workflow / Build with bal test graalvm on Windows
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v3, actions/checkout@v3, al-cheb/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/