Skip to content

Bump maxitest from 6.1.0 to 7.1.1#11118

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bundler/maxitest-7.1.1
Open

Bump maxitest from 6.1.0 to 7.1.1#11118
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bundler/maxitest-7.1.1

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 11, 2026

Bumps maxitest from 6.1.0 to 7.1.1.

Changelog

Sourced from maxitest's changelog.

v7.1.1

  • fix backtrace cleaner not ignoring maxitest traces

v7.1.0

  • update vendored gems

v7.0.0

  • only support minitest 6 (which does not work with any released rails version)
  • removed mtest binary, use minitest instead
  • stoped using alias method chaining, so things might break if you have other minitest extensions
  • use frozen strings everywhere

v6.2.0

  • test and unblock ruby 4
Commits

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies ruby Pull requests that update Ruby code labels Feb 11, 2026
@github-actions
Copy link

⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

This application is owned by the Whitehall Experience team. Please let us know in #govuk-whitehall-experience-tech when you raise any PRs.

Follow these steps if you are doing a Rails upgrade.

@TonyGDS
Copy link
Contributor

TonyGDS commented Feb 11, 2026

We need to merge in #11079 first as this update will upgrade Minitest to v6 which fails to run on rails 8.1.x < 8.1.2

@ChrisBAshton
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/bundler/maxitest-7.1.1 branch from f8241a0 to c2783bf Compare February 16, 2026 15:29
@TonyGDS
Copy link
Contributor

TonyGDS commented Feb 16, 2026

@dependabot rebase

Bumps [maxitest](https://github.com/grosser/maxitest) from 6.1.0 to 7.1.1.
- [Changelog](https://github.com/grosser/maxitest/blob/master/CHANGELOG.md)
- [Commits](grosser/maxitest@v6.1.0...v7.1.1)

---
updated-dependencies:
- dependency-name: maxitest
  dependency-version: 7.1.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/bundler/maxitest-7.1.1 branch from c2783bf to c8e3420 Compare February 16, 2026 16:52
@TonyGDS
Copy link
Contributor

TonyGDS commented Feb 17, 2026

segfault only occurs with parallel execution. The errors fall into these categories:

  1. Mysql2::Error: This connection is in use by: #Fiber:... — MySQL connection being shared across fibers. This is the most concerning one and likely the root cause of the segfault. Something in minitest 6 or Rails' parallel runner is now using
    fibers differently, causing MySQL connections to be accessed concurrently within a single process.
  2. Mysql2::Error: Commands out of sync — cascading from the fiber/connection issue above.
  3. NoMethodError: undefined method 'rollback' for nil — transaction state corruption from the connection issues.
  4. WebMock::NetConnectNotAllowedError — unstubbed HTTP requests, likely because test setup ran on a different fiber/connection than expected.
  5. Capybara::ElementNotFound — integration test failures, possibly also related to the connection issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies do-not-merge ruby Pull requests that update Ruby code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants