Make pipeName be WideCStringObj so the data isn't deleted too early
#30
Triggered via pull request
September 19, 2023 10:53
ire4ever1190
Status
Failure
Total duration
1d 0h 34m 17s
Artifacts
–
Annotations
12 errors and 8 warnings
|
windows-i386-nim-devel (master)
Process completed with exit code 127.
|
|
windows-amd64-nim-devel (master)
Process completed with exit code 127.
|
|
windows-i386-nim-v1.4.8 (master)
Process completed with exit code 1.
|
|
linux-amd64-nim-v1.2.12 (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
linux-amd64-nim-v1.4.8 (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
linux-amd64-nim-devel (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
linux-i386-nim-v1.2.12 (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
linux-i386-nim-devel (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
linux-i386-nim-v1.4.8 (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
macos-amd64-nim-devel (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
macos-amd64-nim-v1.2.12 (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
macos-amd64-nim-v1.4.8 (master)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
windows-i386-nim-devel (master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/
|
|
windows-amd64-nim-devel (master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/
|
|
windows-i386-nim-v1.4.8 (master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/
|
|
windows-i386-nim-v1.2.12 (master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/
|
|
windows-amd64-nim-v1.2.12 (master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/
|
|
windows-amd64-nim-v1.4.8 (master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/
|
|
asynctools
The ubuntu-18.04 environment is deprecated, consider switching to ubuntu-20.04(ubuntu-latest), or ubuntu-22.04 instead. For more details see https://github.com/actions/virtual-environments/issues/6002
|
|
asynctools
The macOS-10.15 environment is deprecated, consider switching to macos-11(macos-latest), macos-12 instead. For more details see https://github.com/actions/virtual-environments/issues/5583
|