Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 28, 2026

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: 4 from test/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

  • Low risk the change is small, highly observable, and easily rolled back.
  • Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
  • High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

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: 4 uses DRb with Unix sockets for IPC. Known failure mode in CI environments—socket files can't be created/accessed reliably in containers.

Alternatives considered:

  • Configure socket directory: Complex, non-portable across CI environments
  • Use threads instead of processes: Requires larger refactor, thread safety concerns
  • Debug DRb initialization: Addresses symptom, not root cause

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

  • Added/updated tests
  • Added/updated documentation
  • Added/updated previews (Lookbook)
  • Tested in Chrome
  • Tested in Firefox
  • Tested in Safari
  • Tested in Edge

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

Fix the failing GitHub Actions workflow Accessibility
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 61779942020
Job URL: https://github.com/primer/view_components/actions/runs/21451142941/job/61779942020


💡 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.

@changeset-bot
Copy link

changeset-bot bot commented Jan 28, 2026

⚠️ No Changeset found

Latest commit: ec83327

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copilot AI changed the title [WIP] Fix failing GitHub Actions workflow for accessibility Fix accessibility workflow DRb socket failure in CI Jan 28, 2026
Copilot AI requested a review from llastflowers January 28, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants