chore(deps): bump pytest-timeout from 2.1.0 to 2.4.0 (#499) #439
fstrAnnotations
2 errors and 1 warning
|
unit-tests
Github returned error "Resource not accessible by integration - https://docs.github.com/rest/commits/statuses#create-a-commit-status" when setting status on commit: c3d0fd76983c30581082d08466d56862979bb2ba
Request object:
{
"context": "unit test result",
"description": "",
"state": "success",
"owner": "firebolt-db",
"repo": "firebolt-python-sdk",
"sha": "c3d0fd76983c30581082d08466d56862979bb2ba",
"target_url": "https://python.docs.firebolt.io//allure/_c3d0fd76983c30581082d08466d56862979bb2ba_unit"
} Possible issues could be that the token used does not have access to the repository containing the commit or the commit/repository does not exist.
|
|
unit-tests
Action failed with "The process '/usr/bin/git' failed with exit code 1"
|
|
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: guibranco/github-status-action-v2@v1.1.13, peaceiris/actions-gh-pages@v4, schneegans/dynamic-badges-action@e9a478b16159b4d31420099ba146cdc50f134483. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
pytest-coverage-report
Expired
|
9.58 KB |
sha256:1503a1db8055986b22d41dc89d3d5f2e86e9bddf35aedf162dcec84a641235b1
|
|