When is the cut off date for this?
A first 2.27~rc3 candidate is in the “beta” channel now.
@mvo it would be great to have https://github.com/snapcore/snapd/pull/3596 added to the release branch too once merged, it will prevent the snapd-notify error we were hitting last week.
Thanks!
@fgimenez, I reproduced that error during beta validation, would be nice if for next RC we can have this fix.
The current results for beta validations are being tracked in:
https://docs.google.com/document/d/15R26w7cwjdYegUDofAwI28LUtdfLNyp0um0WXWCzS60/edit?usp=sharing
snapd-2.27~rc4 currently does not build on Fedora for 32-bit architectures.
cd /builddir/build/BUILD/snapd-2.27~rc4/src/github.com/snapcore/snapd/cmd/snap-seccomp
CGO_LDFLAGS="-g" "-O2" "-Wl,-Bstatic" "-lseccomp" "-Wl,-Bdynamic" /usr/lib/golang/pkg/tool/linux_386/cgo -
objdir $WORK/github.com/snapcore/snapd/cmd/snap-seccomp/_obj/ -importpath
github.com/snapcore/snapd/cmd/snap-seccomp -- -I $WORK/github.com/snapcore/snapd/cmd/snap-
seccomp/_obj/ -g -O2 main.go
# github.com/snapcore/snapd/cmd/snap-seccomp
In file included from /usr/include/xfs/xqm.h:21:0,
from src/github.com/snapcore/snapd/cmd/snap-seccomp/main.go:49:
/usr/include/xfs/xfs.h:51:12: error: size of array 'xfs_assert_largefile' is too large
extern int xfs_assert_largefile[sizeof(off_t)-8];
^~~~~~~~~~~~~~~~~~~~
This issue has come up before in the distant past with snap-confine, and @zyga-snapd and @morphis fixed it before. It looks like the new snap-seccomp will need similar treatment.
I’ll try to fix it now.
What is current target date for 2.27? This Thursday?
Hey Sergio, thanks a lot for the validation. It seems we have a few failures in there (it would be nice if the scenarios that have failures and need looking at would be marked somehow).
Looks like we have quite a few failures, where do I get e.g. the console-conf automated tests? Did you run the tests from the release/2.27
branch? I will try to reproduce the failures now.
The target date is (tentatively) Monday, we need to get to the bottom of those test failures first though.
Today or next Monday?
Sorry, next Monday, we need to sort out the issues that Sergio reported first
If I could get comment rights to the gdoc, that would be great. I am going over the failed tests now (from top to bottom):
- db res1: https://paste.ubuntu.com/25190950/:
error: cannot copy request into temporary file: write /tmp/snapd-sideload-pkg-453861150: no space left on device
- amd64: https://paste.ubuntu.com/25190256/:
-
MATCH 'activation done in' error: pattern not found, got:
- I cherry picked 405d0e6 to fix this 2017-07-28 02:40:50 Error executing external:ubuntu-core-16-64:tests/main/prepare-image-uboot : ... Fetching core core 48.58 MB / 69.93 MB 69.47% 49.25 KB/s 7m23ss6s <kill-timeout reached>
- i386: https://paste.ubuntu.com/25190576/: `
-
+ echo 'Remove hook was executed. It shouldn'\''t.'
: fixed with #3661 Fetching pi2-kernel pi2-kernel 92.91 MB / 96.31 MB 96.46% 132.82 KB/s 26ssss5s <kill-timeout reached>
- snapd-notify test, same as above for amd64
- pi2: https://paste.ubuntu.com/25223576/
- snapd-notify: same as amd64
- install-hook: same as amd64
- prepare-image-uboot: same as amd64
- pi3: https://paste.ubuntu.com/25223117/
2017-08-01 20:03:07 Error executing external:ubuntu-core-16-32:tests/main/failover:rclocalcrash : kill-timeout reached, cannot reconnect to external:ubuntu-core-16-32 after reboot: dial tcp 192.168.1.10:22: getsockopt: no route to host
The failure on refresh in:
-
2017-08-05 10:01:15 Error executing external:ubuntu-core-16-arm-32:tests/main/snap-repair
should be fixed once https://github.com/snapcore/core/pulls/53 is merged.
The failure: 2017-08-01 00:22:49 Error executing external:ubuntu-core-16-64:tests/main/interfaces-account-control :
should be fixed once we cherry-pick http://github.com/snapcore/snapd/pull/3664 to release/2.27
I released a new 2.27~rc7 into “beta” that should fix most of the above failures.
The 2.27 release is now in the candidate channel. Please help testing by snap refresh --candidate core
and let us know if everything works as expected. If we don’t find any regressions we plan to release 2.27 (-final) to stable early next week.
snapd 2.27 and snapd-glib 1.16 have been submitted as updates for Fedora 25 and Fedora 26:
- F26: https://bodhi.fedoraproject.org/updates/FEDORA-2017-f24fd67e3a
- F25: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4f8de51e27
As Fedora 24 reached EOL on August 8, updates for snapd and snapd-glib have ended for this release and it will remain on snapd 2.26.3 and snapd-glib 1.15.
snapd 2.27 for openSUSE is still in progress, pending investigation into a test case failure that seems to be related to golang goroutine scheduling. This has been observed reliably on golang 1.8.3 and kernel 4.11.8-2. I will keep you posted when the issue is understood and resolved.
I just tried running hiri
snap with 2.27 on Ubuntu 16.04 and QtWebEngine browser isn’t loading. The app uses browser-support
interface with QTWEBENGINE_DISABLE_SANDBOX=1
.
Everything works fine with core 16-2.26.14
.