Skip to content

ci: e2e shards give new links no IPv6, so Chrome sees no network change (the module stalls) #796

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.

Sign up for GitHub

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

Merged
futurepaul merged 1 commit into from
Oct 31, 2026
Merged

ci: e2e shards give new links no IPv6, so Chrome sees no network change (the module stalls) #796

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,6 +217,16 @@ jobs:
matrix:
shard: [1, 2, 3, 4]
steps:
# first, before any container: no IPv6 address on a link made from
# here on, nor on Docker's bridge. Chrome takes a link's IPv6 address
# coming or going for a network change, and fails every request still
# waiting for a connection (ERR_NETWORK_CHANGED); Docker adds a link
# for each container a computer starts. So a page's module loads queued
# behind its six connections failed, and the page never started
# ("Still loading…", billing-page's `__held`): the module stalls.
- run: |
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1
if [ -e /proc/sys/net/ipv6/conf/docker0 ]; then sudo sysctl -w net.ipv6.conf.docker0.disable_ipv6=1; fi
- uses: actions/checkout@v4
# the caches, the stub image and the build (.github/actions/e2e-build);
# the first shard saves them on master's pushes
Expand Down
Loading