Skip to content

runtime: "fatal error: unexpected signal during runtime execution" in cmd/go tests on darwin-amd64-race running macOS 12.0 [1.17 backport] #49729

Closed
@gopherbot

Description

@gopherbot

@bcmills requested issue #49723 to be considered for backport to the next 1.17 minor release.

@gopherbot, please backport to Go 1.16 and 1.17. This works around a regression in macOS 12.0.

Activity

added this to the Go1.17.4 milestone on Nov 22, 2021
bcmills

bcmills commented on Nov 22, 2021

@bcmills
Contributor

Approving as a test-only fix due to a regression in an external platform.

gopherbot

gopherbot commented on Nov 22, 2021

@gopherbot
ContributorAuthor

Change https://golang.org/cl/366257 mentions this issue: [release-branch.go1.17] cmd/go: forward the MallocNanoZone variable to script tests

gopherbot

gopherbot commented on Nov 22, 2021

@gopherbot
ContributorAuthor

Closed by merging 364f15f to release-branch.go1.17.

added a commit that references this issue on Nov 22, 2021
364f15f
added
TestingAn issue that has been verified to require only test changes, not just a test failure.
on Nov 23, 2021
locked and limited conversation to collaborators on Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CherryPickApprovedUsed during the release process for point releasesFrozenDueToAgeTestingAn issue that has been verified to require only test changes, not just a test failure.release-blocker

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @dmitshur@bcmills@gopherbot

        Issue actions

          runtime: "fatal error: unexpected signal during runtime execution" in cmd/go tests on darwin-amd64-race running macOS 12.0 [1.17 backport] · Issue #49729 · golang/go