net/http: only disable fetch in test

[Zxilly]

This change allows the js/wasm port binary to perform network
access correctly on Node.js without breaking tests
that have not yet been migrated.

Updates #57613
Fixes #69106

[gopherbot]

This PR (HEAD: fb4bdb6) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/611215.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Zxilly Chou:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Johan Brandhorst-Satzkorn:

Patch Set 2: Code-Review+2 Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-05T16:53:03Z","revision":"e4befa74861b0bd2638637bb664741eb56d88b80"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Johan Brandhorst-Satzkorn:

Patch Set 2: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-arm64 has failed with summary (view all results):

---

• go on master (change 611215)

Build or test failure, click here for results.

To reproduce, try gomote repro 8737617949827760881.

Additional links for debugging:

• Output for go tool dist test -json [shard 1]

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Zxilly Chou:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Zxilly Chou:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Johan Brandhorst-Satzkorn:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Johan Brandhorst-Satzkorn:

Patch Set 2: -Code-Review

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Zxilly Chou:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Johan Brandhorst-Satzkorn:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 140640b) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/611215.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Zxilly Chou:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Zxilly Chou:

Patch Set 3:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ian Lance Taylor:

Patch Set 3: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 3:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-07T20:46:32Z","revision":"39256ffd2f08f7acf7dcf00900ac83b26e8b8955"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ian Lance Taylor:

Patch Set 3: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 3:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 3: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Dmitri Shuralyov:

Patch Set 3:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/611215.
After addressing review feedback, remember to publish your drafts!