Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Travis-ci: AMD64 build is failing

Open
#216 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go

Research direction

Start with .travis.yml and the Travis build log linked in the issue. Reproduce the AMD64 build, inspect the Go environment and the failing go get github.com/golang/lint/golint command, then trace the IsAlias errors in the reported go-tools files. Done means the default AMD64 Travis build completes successfully.

Written by the indexing model from the issue text.

Description

Hi,
I am enabling ppc64le support on Travis, but its failing for both of the arch. Then i removed my changes from .travis.yml. Amd then tried to build just for AMD64 which is default. But i am getting below error:

"# golang.org/x/tools/go/internal/gcimporter
../../../golang.org/x/tools/go/internal/gcimporter/bexport.go:212: obj.IsAlias undefined (type *types.TypeName has no field or method IsAlias)
../../../golang.org/x/tools/go/internal/gcimporter/iexport.go:234: obj.IsAlias undefined (type *types.TypeName has no field or method IsAlias)
The command "go get github.com/golang/lint/golint" failed and exited with 2 during .
Your build has been stopped."

The full log can be seen here : https://travis-ci.com/github/sanjay-cpu/libkv/builds/187011429

Please have a look on this.

Thanks !!

Dominant language
Go
Stars
848
Forks
204
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/libkv

All issues in docker/libkv

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.