Skip to content

cmd/go: GOMIPS environment variable does not affect caching of mipsle code [1.10 backport] #27421

Closed
@gopherbot

Description

@gopherbot

@FiloSottile requested issue #27260 to be considered for backport to the next 1.10 minor release.

@gopherbot please file this issue for backport to 1.11 and 1.10 (GOMIPS and the cache were introduced in 1.10, so it might affect both, if not please close the 1.10 issue).

@ianlancetaylor had milestoned this for 1.11.1 and I don't see a cherry-pick, but it was closed by the master fix.

Activity

added this to the Go1.10.5 milestone on Aug 31, 2018
gopherbot

gopherbot commented on Nov 1, 2018

@gopherbot
ContributorAuthor

Change https://golang.org/cl/146560 mentions this issue: [release-branch.go1.10] cmd/go: add GOMIPS value to build id for mipsle

gopherbot

gopherbot commented on Nov 1, 2018

@gopherbot
ContributorAuthor

Closed by merging 15c6cc7 to release-branch.go1.10.

added a commit that references this issue on Nov 1, 2018
15c6cc7
locked and limited conversation to collaborators on Nov 1, 2019
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

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @dmitshur@gopherbot

        Issue actions

          cmd/go: GOMIPS environment variable does not affect caching of mipsle code [1.10 backport] · Issue #27421 · golang/go