snapcraft fails on s390x with utf8 error

[Oliver Grawert]

with snapcraft 2.18 landing in xenial-updates last night the daily build of ubuntu-core started to fail reliably on the s390x architecture with the following traceback:

Staging livebuild
Priming livebuild
'utf-8' codec can't encode character '\udcc5' in position 87: surrogates not allowed
Traceback (most recent call last):
  File "/usr/share/launchpad-buildd/slavebin/buildsnap", line 191, in main
    builder.build()
  File "/usr/share/launchpad-buildd/slavebin/buildsnap", line 137, in build
    ["snapcraft"], path=os.path.join("/build", self.name))
  File "/usr/share/launchpad-buildd/slavebin/buildsnap", line 88, in run_build_command
    self.chroot(["/bin/sh", "-c", command], echo=echo)
  File "/usr/share/launchpad-buildd/slavebin/buildsnap", line 66, in chroot
    "/usr/bin/sudo", "/usr/sbin/chroot", self.chroot_path] + args)
  File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['/usr/bin/sudo', '/usr/sbin/chroot', '/home/buildd/build-SNAPBUILD-5660/chroot-autobuild', 'linux64', '/bin/sh', '-c', 'cd /build/ubuntu-core && snapcraft']' returned non-zero exit status 1
Revoking proxy token...

a build log is at https://launchpadlibrarian.net/287056073/buildlog_snap_ubuntu_xenial_s390x_ubuntu-core_BUILDING.txt.gz

as https://code.launchpad.net/~snappy-dev/+snap/ubuntu-core shows all other architectures build fine.
this used to work well with snapcraft 2.17 and before.

[Sergio Schvezov (sergiusens)]

El miércoles, 28 de septiembre de 2016 07h'40:20 ART, Oliver Grawert
<email address hidden> escribió:
> Public bug reported:
>
> with snapcraft 2.18 landing in xenial-updates last night the daily build
> of ubuntu-core started to fail reliably on the s390x architecture with
> the following traceback:

Can you run snapcraft with --debug?

>
> Staging livebuild
> Priming livebuild
> 'utf-8' codec can't encode character '\udcc5' in position 87:
> surrogates not allowed
> Traceback (most recent call last):
> File "/usr/share/launchpad-buildd/slavebin/buildsnap", line 191, in main
> builder.build()
> File "/usr/share/launchpad-buildd/slavebin/buildsnap", line 137, in build
> ["snapcraft"], path=os.path.join("/build", self.name))
> File "/usr/share/launchpad-buildd/slavebin/buildsnap", line
> 88, in run_build_command
> self.chroot(["/bin/sh", "-c", command], echo=echo)
> File "/usr/share/launchpad-buildd/slavebin/buildsnap", line 66, in chroot
> "/usr/bin/sudo", "/usr/sbin/chroot", self.chroot_path] + args)
> File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
> raise CalledProcessError(retcode, cmd)
> CalledProcessError: Command '['/usr/bin/sudo',
> '/usr/sbin/chroot',
> '/home/buildd/build-SNAPBUILD-5660/chroot-autobuild', 'linux64',
> '/bin/sh', '-c', 'cd /build/ubuntu-core && snapcraft']' returned
> non-zero exit status 1
> Revoking proxy token...
>
> a build log is at https://launchpadlibrarian.net/287056073
> /buildlog_snap_ubuntu_xenial_s390x_ubuntu-core_BUILDING.txt.gz
>
> as https://code.launchpad.net/~snappy-dev/+snap/ubuntu-core
> shows all other architectures build fine.
> this used to work well with snapcraft 2.17 and before.

Strange as we did not change any code paths here. --debug will clear this
up.

--
Enviado con Dekko desde mi dispositivo Ubuntu

[Mark Shuttleworth (sabdfl)]

Just to say I love how this IoT tech moved so fast to big iron :)

Mark

[Sergio Schvezov (sergiusens)]

https://github.com/snapcore/snapcraft/pull/838

[Oliver Grawert (ogra)]

just wait til we have these snappy based s390x phones out there ;)