chore(deps): update dependency @types/uuid to v9.0.3 #9900
Triggered via pull request
August 30, 2023 21:09
repo-ranger[bot]
synchronize
#1512
Status
Failure
Total duration
32m 35s
Artifacts
1
test.yml
on: pull_request_target
build
56s
Run shellcheck
4s
Test with multiple repositories
6s
Test changed-files using since and until
0s
Test changed-files similar base and commit sha
6s
Test unset GITHUB_OUTPUT env
8s
Test changed-files with pull request head ref
5s
Test changed-files non existent base sha
10s
Test changed-files non existent sha
26s
Test changed-files with REST API
6s
Matrix: Test changed-files with limited commit history
Matrix: Test changed-files with pull request without persist credentials
Matrix: Test changed-files recover deleted file
Matrix: Test changed-files with submodule
Matrix: Test changed-files with yaml
Matrix: Test changed-files
Annotations
27 errors and 40 warnings
Test changed-files (macos-latest, 0)
Similar commit hashes detected: previous sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff is equivalent to the current sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff.
|
Test changed-files (macos-latest, 0)
Similar commit hashes detected.
|
Test changed-files (windows-latest, 0)
Similar commit hashes detected: previous sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff is equivalent to the current sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff.
|
Test changed-files (windows-latest, 0)
Similar commit hashes detected.
|
Test with multiple repositories
Similar commit hashes detected: previous sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff is equivalent to the current sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff.
|
Test with multiple repositories
Similar commit hashes detected.
|
Test changed-files similar base and commit sha
Similar commit hashes detected: previous sha: d1c0ee4 is equivalent to the current sha: d1c0ee4.
|
Test changed-files similar base and commit sha
Please verify that both commits are valid, and increase the fetch_depth to a number higher than 50.
|
Test changed-files similar base and commit sha
Similar commit hashes detected.
|
Test unset GITHUB_OUTPUT env
Similar commit hashes detected: previous sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff is equivalent to the current sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff.
|
Test unset GITHUB_OUTPUT env
Similar commit hashes detected.
|
Test changed-files with pull request without persist credentials (0)
Similar commit hashes detected: previous sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff is equivalent to the current sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff.
|
Test changed-files with pull request without persist credentials (0)
Similar commit hashes detected.
|
Test changed-files non existent base sha
Unable to locate the commit sha: 4554456
|
Test changed-files non existent base sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
|
Test changed-files non existent base sha
The process '/usr/bin/git' failed with exit code 128
|
Test changed-files non existent base sha
Unable to locate the commit sha: 4554456
|
Test changed-files non existent base sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
|
Test changed-files non existent base sha
The process '/usr/bin/git' failed with exit code 128
|
Test changed-files non existent sha
Unable to locate the commit sha: 4774456
|
Test changed-files non existent sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
|
Test changed-files non existent sha
Unable to determine a difference between 0fc9663aa70243d87319dbd32fd926344d18d38f..4774456
|
Test changed-files non existent sha
Unable to locate the commit sha: 4774456
|
Test changed-files non existent sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
|
Test changed-files non existent sha
Unable to determine a difference between 0fc9663aa70243d87319dbd32fd926344d18d38f..4774456
|
Test changed-files (ubuntu-latest, 0)
Similar commit hashes detected: previous sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff is equivalent to the current sha: 50f623482f13ff783ea3495d9c9a106d8f17d2ff.
|
Test changed-files (ubuntu-latest, 0)
Similar commit hashes detected.
|
Test changed-files (macos-latest, 0)
Unable to locate the commit sha: 842dba5a94c88f94ad6678155d1d9b54c21467d8
|
Test changed-files (macos-latest, 0)
If this pull request is from a forked repository, please set the checkout action `repository` input to the same repository as the pull request.
|
Test changed-files (macos-latest, 0)
This can be done by setting actions/checkout `repository` to ${{ github.event.pull_request.head.repo.full_name }}
|
Test changed-files (windows-latest, 0)
Unable to locate the commit sha: 842dba5a94c88f94ad6678155d1d9b54c21467d8
|
Test changed-files (windows-latest, 0)
If this pull request is from a forked repository, please set the checkout action `repository` input to the same repository as the pull request.
|
Test changed-files (windows-latest, 0)
This can be done by setting actions/checkout `repository` to ${{ github.event.pull_request.head.repo.full_name }}
|
Test with multiple repositories
Unable to locate the commit sha: 842dba5a94c88f94ad6678155d1d9b54c21467d8
|
Test with multiple repositories
If this pull request is from a forked repository, please set the checkout action `repository` input to the same repository as the pull request.
|
Test with multiple repositories
This can be done by setting actions/checkout `repository` to ${{ github.event.pull_request.head.repo.full_name }}
|
Test unset GITHUB_OUTPUT env
Unable to locate the commit sha: 842dba5a94c88f94ad6678155d1d9b54c21467d8
|
Test unset GITHUB_OUTPUT env
If this pull request is from a forked repository, please set the checkout action `repository` input to the same repository as the pull request.
|
Test unset GITHUB_OUTPUT env
This can be done by setting actions/checkout `repository` to ${{ github.event.pull_request.head.repo.full_name }}
|
Test changed-files with pull request without persist credentials (0)
Unable to locate the commit sha: 842dba5a94c88f94ad6678155d1d9b54c21467d8
|
Test changed-files with pull request without persist credentials (0)
If this pull request is from a forked repository, please set the checkout action `repository` input to the same repository as the pull request.
|
Test changed-files with pull request without persist credentials (0)
This can be done by setting actions/checkout `repository` to ${{ github.event.pull_request.head.repo.full_name }}
|
Test changed-files non existent base sha
fatal: ambiguous argument '4554456...842dba5a94c88f94ad6678155d1d9b54c21467d8': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
|
Test changed-files non existent base sha
fatal: ambiguous argument '4554456...842dba5a94c88f94ad6678155d1d9b54c21467d8': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files non existent sha
Unable to find merge base between 0fc9663aa70243d87319dbd32fd926344d18d38f and 4774456
|
Test changed-files (ubuntu-latest, 0)
Unable to locate the commit sha: 842dba5a94c88f94ad6678155d1d9b54c21467d8
|
Test changed-files (ubuntu-latest, 0)
If this pull request is from a forked repository, please set the checkout action `repository` input to the same repository as the pull request.
|
Test changed-files (ubuntu-latest, 0)
This can be done by setting actions/checkout `repository` to ${{ github.event.pull_request.head.repo.full_name }}
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
build-assets
Expired
|
3.33 MB |
|