Add ability to run a function on a given thread #1096
Triggered via pull request
January 17, 2024 13:13
Status
Failure
Total duration
6h 8m 6s
Artifacts
–
ci.yml
on: pull_request
gir
1m 19s
macos-x86_64
6h 0m
linux-x86
2m 45s
linux-x86_64
2m 13s
freebsd-arm64
1m 54s
ios-arm64
1m 30s
qnx-armeabi
2m 20s
Matrix: android-arm
Matrix: android-intel
Matrix: linux-mips
Matrix: windows
Annotations
9 errors and 2 warnings
ios-arm64
Process completed with exit code 1.
|
android-intel (x86)
The process '/bin/sh' failed with exit code 139
|
android-intel (x86_64)
The process '/bin/sh' failed with exit code 139
|
windows (amd64)
The job running on runner GitHub Actions 6 has exceeded the maximum execution time of 360 minutes.
|
windows (amd64)
The operation was canceled.
|
windows (amd64_x86)
The job running on runner GitHub Actions 1 has exceeded the maximum execution time of 360 minutes.
|
windows (amd64_x86)
The operation was canceled.
|
macos-x86_64
The job running on runner GitHub Actions 7 has exceeded the maximum execution time of 360 minutes.
|
macos-x86_64
The operation was canceled.
|
android-intel (x86)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
|
android-intel (x86_64)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
|