Fix pod install issue when git's core.fsmonitor feature is enabled
#1083
Triggered via pull request
November 21, 2023 23:50
justinseanmartin
Status
Failure
Total duration
20m 16s
Artifacts
–
Annotations
4 errors and 5 warnings
|
SPECS / ubuntu-20.04 / Ruby 3
Process completed with exit code 1.
|
|
SPECS / ubuntu-20.04 / Ruby 2.7
Process completed with exit code 1.
|
|
SPECS / ubuntu-20.04 / Ruby 2.6
Process completed with exit code 1.
|
|
SPECS / macos-12 / Ruby system
Process completed with exit code 1.
|
|
SPECS / ubuntu-20.04 / Ruby 3
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/
|
|
SPECS / ubuntu-20.04 / Ruby 2.7
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/
|
|
SPECS / ubuntu-20.04 / Ruby 2.6
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/
|
|
SPECS / macos-12 / Ruby system
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/
|
|
EXAMPLES / macos-12 / Ruby system
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/
|