patchelf fails on i386 vscode

Bug #1798881 reported by Alan Pope 🍺🐧🐱 🦄
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Snapcraft
Incomplete
Undecided
Unassigned
vscodium.snap
New
High
Unassigned

Bug Description

https://launchpadlibrarian.net/393792896/buildlog_snap_ubuntu_xenial_i386_8530e5f76cb0f52c411b1e115ff18a11-xenial_BUILDING.txt.gz

Seems the i386 build of vscode hasn't built for a while due to patchelf failure.

Staging electron-launch
Staging vscode
Priming electron-launch
Priming vscode
virtual address space underrun!
Failed to update '/build/vscode/prime/usr/share/code/code'. Retrying after stripping the .note.go.buildid from the elf file.
virtual address space underrun!
An attempt to patch '/build/vscode/prime/usr/share/code/code' so that it would work correctly in diverse environments was made and failed. To disable this behavior set `build-attributes: [no-patchelf]` for the part.
'/build/vscode/prime/usr/share/code/code' cannot be patched to function properly in a classic confined snap: /usr/bin/patchelf --set-interpreter /snap/core/current/lib/ld-linux.so.2 --force-rpath --set-rpath $ORIGIN/lib/:$ORIGIN/../../lib/i386-linux-gnu:$ORIGIN/../../../lib/i386-linux-gnu:$ORIGIN:/snap/core/current/usr/lib/i386-linux-gnu:/snap/core/current/lib/i386-linux-gnu /tmp/tmpk1puj0w0 failed with exit code 1.
'patchelf 0.9' may be too old. A newer version of patchelf may be required.
Try adding the `after: [patchelf]` and a `patchelf` part that would filter out files from prime `prime: [-*]` or `build-snaps: [patchelf/latest/edge]` to the failing part in your `snapcraft.yaml` to use a newer patchelf.
Build failed
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/lpbuildd/target/build_snap.py", line 229, in run
    self.build()
  File "/usr/lib/python2.7/dist-packages/lpbuildd/target/build_snap.py", line 218, in build
    env=env)
  File "/usr/lib/python2.7/dist-packages/lpbuildd/target/build_snap.py", line 75, in run_build_command
    return self.backend.run(args, env=full_env, **kwargs)
  File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lxd.py", line 460, in run
    subprocess.check_call(cmd, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['lxc', 'exec', 'lp-xenial-i386', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build_url": "https://launchpad.net/~build.snapcraft.io/+snap/8530e5f76cb0f52c411b1e115ff18a11-xenial/+build/355956"}', '--env', 'http_proxy=http://10.10.10.1:8222/', '--env', 'https_proxy=http://10.10.10.1:8222/', '--env', 'GIT_PROXY_COMMAND=/usr/local/bin/snap-git-proxy', '--', '/bin/sh', '-c', 'cd /build/vscode && linux32 snapcraft']' returned non-zero exit status 2
Revoking proxy token...
RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes --backend=lxd --series=xenial --arch=i386 SNAPBUILD-355956
Scanning for processes to kill in build SNAPBUILD-355956

Changed in vscodium.snap:
importance: Undecided → High
no longer affects: vscodium.snap
no longer affects: ubuntu
Changed in vscodium.snap:
importance: Undecided → High
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

Can you reproduce this when using the snapcraft snap and setting base to either core or core18?

Changed in snapcraft:
status: New → Incomplete
Revision history for this message
Ermesto Castellotti (ernytech) wrote :

with snapcraft snap (edge ​​channel) and core18 I get the same issue

Here is the build log: https://launchpadlibrarian.net/419684583/buildlog_snap_ubuntu_xenial_i386_vscodium.snap_BUILDING.txt.gz

Revision history for this message
Sergio Schvezov (sergiusens) wrote : Re: [Bug 1798881] Re: patchelf fails on i386 vscode

El miércoles, 17 de abril de 2019 16:27:05 -03 usted escribió:
> with snapcraft snap (edge ​​channel) and core18 I get the same issue
>
> Here is the build log:
> https://launchpadlibrarian.net/419684583/buildlog_snap_ubuntu_xenial_i386_vs
> codium.snap_BUILDING.txt.gz

It does not look like you are using the snapcraf snap, how are you building
this? launchpad directly or build.snapcraft.io? Also make sure the "base"
keyword is set in snapcraft.yaml

Revision history for this message
Ermesto Castellotti (ernytech) wrote :

I compile directly from launchpad

Revision history for this message
Ermesto Castellotti (ernytech) wrote :

I think it's using snapcraft snap because this is present in the logs:

Processing triggers for libc-bin (2.23-0ubuntu11) ...
Processing triggers for systemd (229-4ubuntu21.21) ...
2019-04-17T20:32:56Z INFO Waiting for restart...
core (edge) 16-2.38.1+git1244.bf45eba from Canonical* installed
snapcraft (edge) 3.4+git4.g3d4483d from Canonical* installed
/usr/lib/python2.7/dist-packages/pylxd/model.py:116: UserWarning: Attempted to set unknown attribute "description" on instance of "Container"
  key, self.__class__.__name__
Running repo phase...
Cloning into 'vscodium'...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.