-
Notifications
You must be signed in to change notification settings - Fork 3
chore(deps)(deps): bump serial_test from 3.2.0 to 3.3.1 #402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
GitHub Runner Execution ResultsPR: #402 - chore(deps)(deps): bump serial_test from 3.2.0 to 3.3.1 ❌ test-on-pr.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-optimized.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ vm-execution-tests.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-native.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ✅ Powered by terraphim-github-runner |
de785f2 to
544a7f6
Compare
GitHub Runner Execution ResultsPR: #402 - chore(deps)(deps): bump serial_test from 3.2.0 to 3.3.1 ❌ ci.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-optimized.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ test-on-pr.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-native.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ vm-execution-tests.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ✅ Powered by terraphim-github-runner |
544a7f6 to
6387d06
Compare
GitHub Runner Execution ResultsPR: #402 - chore(deps)(deps): bump serial_test from 3.2.0 to 3.3.1 ❌ python-bindings.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-optimized.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ test-on-pr.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ vm-execution-tests.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-native.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ✅ Powered by terraphim-github-runner |
6387d06 to
1d02ebd
Compare
GitHub Runner Execution ResultsPR: #402 - chore(deps)(deps): bump serial_test from 3.2.0 to 3.3.1 ❌ ci-optimized.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-pr.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ test-on-pr.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-native.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ vm-execution-tests.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ✅ Powered by terraphim-github-runner |
1d02ebd to
de3e55e
Compare
GitHub Runner Execution ResultsPR: #402 - chore(deps)(deps): bump serial_test from 3.2.0 to 3.3.1 ❌ python-bindings.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-optimized.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ test-on-pr.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ vm-execution-tests.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-native.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ✅ Powered by terraphim-github-runner |
|
@dependabot rebase |
Bumps [serial_test](https://github.com/palfrey/serial_test) from 3.2.0 to 3.3.1. - [Release notes](https://github.com/palfrey/serial_test/releases) - [Commits](palfrey/serial_test@v3.2.0...v3.3.1) --- updated-dependencies: - dependency-name: serial_test dependency-version: 3.3.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
de3e55e to
33ec5f0
Compare
GitHub Runner Execution ResultsPR: #402 - chore(deps)(deps): bump serial_test from 3.2.0 to 3.3.1 ❌ python-bindings.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ test-on-pr.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-optimized.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ ci-native.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ❌ vm-execution-tests.ymlExecution failed: VM allocation failed: Allocation failed with status: 429 Too Many Requests ✅ Powered by terraphim-github-runner |
Bumps serial_test from 3.2.0 to 3.3.1.
Release notes
Sourced from serial_test's releases.
Commits
0771eb03.3.1ace6ebfMerge pull request #148 from palfrey/docsrs-testing349375dImprove feature flag docsf9deb97Remove doc_auto_cfgd5a4c09Reset cargo.lock89253b1Test docs-rs will work5e84cd43.3.0abfc053Merge pull request #147 from palfrey/non-absolute-file-checking38d6b05Refactor feature name for serial_test_test2620c79test-all-features needs more escapingDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)