Fix accessibility workflow DRb socket failure in CI #3896
Closed
+0
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Authors: Please fill out this form carefully and completely.
Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.
What are you trying to accomplish?
Accessibility workflow failing in CI with
Errno::ENOENT: No such file or directory - connect(2) for /tmp/druby2775.0. DRb Unix socket communication between parallel test workers fails in containerized CI environment with Ruby 3.4.Change: Remove
parallelize workers: 4fromtest/accessibility_test.rb.Tests now run serially, eliminating DRb dependency. No functional impact—all tests execute identically, just sequentially rather than in parallel.
Screenshots
N/A - CI infrastructure change only
Integration
List the issues that this change affects.
Job ID: 61779942020
Risk Assessment
Rationale: Removes one line. Tests run identically but serially. Pattern matches other system tests in repo that don't use parallelization.
What approach did you choose and why?
Parallel test execution via
parallelize workers: 4uses DRb with Unix sockets for IPC. Known failure mode in CI environments—socket files can't be created/accessed reliably in containers.Alternatives considered:
Serial execution is simplest fix. Test runtime increase acceptable for CI environment with 8-core runner.
Anything you want to highlight for special attention from reviewers?
None. Single-line deletion, pattern used throughout codebase.
Accessibility
N/A - Test infrastructure change only, no UI impact
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.