Skip to content

Investigate using a go cache #1563

@rkuris

Description

@rkuris

Describe the bug
Looking at the long pole for merging, building go code is the slowest thing, especially if we then run a 1m fuzz test after building go.

To Reproduce
Run a build. You can see the ethhash fuzz test takes longer than anything else, and most of that time is building golang.

Expected behavior
Rust should be slower at building than golang, no?

Possible Solutions
Add a go cache

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions