Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compilation fails on all architectures on Ubuntu Xenial #279

Open
rbalint opened this issue Jan 15, 2021 · 15 comments
Open

Compilation fails on all architectures on Ubuntu Xenial #279

rbalint opened this issue Jan 15, 2021 · 15 comments
Assignees

Comments

@rbalint
Copy link

rbalint commented Jan 15, 2021

https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4159/+build/20820342
https://launchpadlibrarian.net/517348792/buildlog_ubuntu-xenial-amd64.google-osconfig-agent_20210112.00-0ubuntu1~16.04.0~rbalint2_BUILDING.txt.gz

github.com/GoogleCloudPlatform/osconfig/policies
github.com/GoogleCloudPlatform/osconfig
# github.com/GoogleCloudPlatform/osconfig
github.com/GoogleCloudPlatform/osconfig/vendor/golang.org/x/crypto/openpgp/packet.(*Compressed).parse: relocation target compress/zlib.NewReaderDict not defined
github.com/GoogleCloudPlatform/osconfig/vendor/golang.org/x/crypto/openpgp/packet..inittask: relocation target compress/zlib..inittask not defined
dh_auto_build: go install -v -ldflags=-s -w -X main.version=20210112.00-0ubuntu1~16.04.0~rbalint2 github.com/GoogleCloudPlatform/osconfig github.com/GoogleCloudPlatform/osconfig/agentconfig github.com/GoogleCloudPlatform/osconfig/agentendpoint github.com/GoogleCloudPlatform/osconfig/attributes github.com/GoogleCloudPlatform/osconfig/clog github.com/GoogleCloudPlatform/osconfig/external github.com/GoogleCloudPlatform/osconfig/inventory github.com/GoogleCloudPlatform/osconfig/osinfo 
@rojer
Copy link

rojer commented Jan 30, 2021

looks like recently backported go 1.13 has a bug.
reported here - https://bugs.launchpad.net/ubuntu/+source/golang-1.13/+bug/1913852

@zmarano
Copy link
Contributor

zmarano commented Feb 10, 2021

/assign @adjackura

@adjackura
Copy link
Contributor

It looks like this is an issue with 1.13 on Xenial correct? Is the 1.13 the latest version available for Xenial building?

@rbalint
Copy link
Author

rbalint commented Feb 11, 2021

It is 1.13.8-1ubuntu1~16.04.2 , which is a backport of the latest 1.13.x version in Ubuntu:

 golang-1.13 | 1.13.8-1ubuntu1~16.04.2 | xenial-updates/universe | source, all
 golang-1.13 | 1.13.8-1ubuntu1~18.04.2 | bionic-updates/universe | source, all
 golang-1.13 | 1.13.8-1ubuntu1         | focal                   | source, all
 golang-1.13 | 1.13.8-1ubuntu2         | groovy                  | source
 golang-1.13 | 1.13.8-1ubuntu2         | groovy/universe         | all
 golang-1.13 | 1.13.8-1ubuntu2         | hirsute/universe        | source, all

@mwhudson
Copy link

There is a fix in the xenial unapproved queue now.

@rbalint
Copy link
Author

rbalint commented Feb 11, 2021

@mwhudson thanks!

@rojer
Copy link

rojer commented Feb 11, 2021

@mwhudson thanks, confirmed that the fix works. what is the approximate timeline for its release?

@mwhudson
Copy link

@rojer the fix has just been accepted into proposed, which is actually enough (once published) to fix your needs I think as subsequent package builds will use the toolchain from proposed. Would you as reporter be able to verify the fix as described in the bug? If not, I can.

@rojer
Copy link

rojer commented Feb 16, 2021

retried one of the failing builds but it still used the old package (...16.04.2) and failed again.

@mwhudson
Copy link

is this in a ppa? does it have proposed enabled?

@rojer
Copy link

rojer commented Feb 16, 2021

yes it is and no it wasn't. switched to proposed and the build succeeded. thanks for taking care of this!

@mwhudson
Copy link

Great thanks. Can you share the build logs in the bug? Or here and I will paste them in?

@rojer
Copy link

rojer commented Feb 20, 2021

here's a successful build - https://launchpad.net/~mongoose-os/+archive/ubuntu/mos/+build/21000322
it's a retry of a build that failed, i don't know if it's possible to get those logs

@mwhudson
Copy link

It might still be available from a build failure email, there's nowhere in the UI to retrieve it from unfortunately.

@rojer
Copy link

rojer commented Feb 22, 2021

links from failure notifications point to the same log, unfortunately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants