Skip to content
Compatibility Test Windows-X64

fix: shouldn't use stack-pointer to avoid stackgrow problem #29

Sign in to view logs

fix: shouldn't use stack-pointer to avoid stackgrow problem

fix: shouldn't use stack-pointer to avoid stackgrow problem #29

Triggered via pull request August 25, 2023 07:55
@AsterDYAsterDY
opened #515
fix/enc_stkptr
Status Failure
Total duration 2m 59s
Artifacts –

compatibility_test-windows.yml

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

Annotations

2 errors and 4 warnings
build (1.21.x)
Process completed with exit code 1.
build (1.17.x)
The operation was canceled.
build (1.21.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (1.21.x)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
build (1.17.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (1.17.x)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128