Skip to content

runtime: test failures introduced on ppc64le with change to improve fastrand #22047

Open
@laboger

Description

@laboger

What version of Go are you using (go version)?

tip

Does this issue reproduce with the latest release?

intermittently, only seen on the golang build page so far

What operating system and processor architecture are you using (go env)?

ppc64le

What did you do?

When the fastrand change was merged e7e4a4f runtime failures started to happen intermittently for ppc64le on the build page. Another change was merged after that resulting in consistent failures on ppc64le that hid this one for a while, but that one has now been fixed.

What did you expect to see?

ok for the ppc64le build on the build page

What did you see instead?

fail for the ppc64le build on the build page intermittently

Here is an example of when it fails https://build.golang.org/log/8552765394dde8879c15b4e35b2f995606b8ed1b.

Looks like the tests are all parked waiting to run and it times out.

If I look at the change where this started happening, the only thing that looks like it could affect this is the code that was moved in mcommoninit to be under control of a lock where it wasn't before, but I can't say that is wrong, just different.

I have not been able to reproduce this anywhere else.

Metadata

Metadata

Assignees

No one assigned

    Labels

    NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions