[Group.of.nepali.translators] [Bug 1704979] Re: The snap.sh autopkgtest suite failes on non amd64/i386 arches
** Changed in: ubuntu-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1704979 Title: The snap.sh autopkgtest suite failes on non amd64/i386 arches Status in Ubuntu Image: Fix Released Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: Fix Released Status in ubuntu-image source package in Yakkety: Invalid Status in ubuntu-image source package in Zesty: Fix Released Bug description: [Impact] With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and arm64 will fail (the snap.sh test). This test does not make sense to be run as part of .deb migration as it's testing snap buildability - it's a bad idea to mix those two worlds. [Test Case] Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped). [Regression Potential] None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull- request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users. [Original Description] We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu- image 1.1 for armhf, ppc64el and s390x. By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non- snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed. In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with: error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-image/+bug/1704979/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1704979] Re: The snap.sh autopkgtest suite failes on non amd64/i386 arches
This bug was fixed in the package ubuntu-image - 1.1+17.04ubuntu3 --- ubuntu-image (1.1+17.04ubuntu3) zesty; urgency=medium * Only run the snap.sh test on github PRs as it doesn't make sense to run it as part of regular deb package migration. (LP: #1704979) ubuntu-image (1.1+17.04ubuntu1) zesty; urgency=medium [ Łukasz 'sil2100' Zemczak ] * SRU tracking number LP: #1702933 * Fix snapcraft.yaml for classic snappage. (LP:1673576) * Add a new step in the builder that generates .manifest files listing all snaps installed in the resulting image. (LP:1680574) * Further fixes to snapcraft.yaml, making sure that we only have one ubuntu-image version installed in the snap. (LP:1692901) * Move files around during snap build to have all needed libraries and python files in common accessible paths, install missing dependencies into the snap. (LP:1694982, LP:1694993) [ Michael Vogt ] * Use fakeroot when running mkfs.ext4. (LP:1702628) [ Steve Langasek ] * Add fakeroot to the snapcraft.yaml and as a test dep. (LP:1702628) -- Łukasz 'sil2100' Zemczak Wed, 19 Jul 2017 15:31:06 +0200 ** Changed in: ubuntu-image (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1704979 Title: The snap.sh autopkgtest suite failes on non amd64/i386 arches Status in Ubuntu Image: Fix Committed Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: Fix Released Status in ubuntu-image source package in Yakkety: Invalid Status in ubuntu-image source package in Zesty: Fix Released Bug description: [Impact] With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and arm64 will fail (the snap.sh test). This test does not make sense to be run as part of .deb migration as it's testing snap buildability - it's a bad idea to mix those two worlds. [Test Case] Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped). [Regression Potential] None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull- request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users. [Original Description] We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu- image 1.1 for armhf, ppc64el and s390x. By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non- snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed. In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with: error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-image/+bug/1704979/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1704979] Re: The snap.sh autopkgtest suite failes on non amd64/i386 arches
This bug was fixed in the package ubuntu-image - 1.1+16.04ubuntu4 --- ubuntu-image (1.1+16.04ubuntu4) xenial; urgency=medium * Drop part of the xenial delta, adding the fakeroot dependency as per master. Properly handling the lack of the dependency and still getting 100% code coverage on all series requires too much unnecessary work. (LP: #1709029) ubuntu-image (1.1+16.04ubuntu3) xenial; urgency=medium * Only run the snap.sh test on github PRs as it doesn't make sense to run it as part of regular deb package migration. (LP: #1704979) ubuntu-image (1.1+16.04ubuntu1) xenial; urgency=medium [ Łukasz 'sil2100' Zemczak ] * SRU tracking number LP: #1702933 * Fix snapcraft.yaml for classic snappage. (LP:1673576) * Add a new step in the builder that generates .manifest files listing all snaps installed in the resulting image. (LP:1680574) * Further fixes to snapcraft.yaml, making sure that we only have one ubuntu-image version installed in the snap. (LP:1692901) * Move files around during snap build to have all needed libraries and python files in common accessible paths, install missing dependencies into the snap. (LP:1694982, LP:1694993) [ Michael Vogt ] * Use fakeroot when running mkfs.ext4. (LP:1702628) [ Steve Langasek ] * Add fakeroot to the snapcraft.yaml and as a test dep. (LP:1702628) -- Łukasz 'sil2100' Zemczak Tue, 08 Aug 2017 10:44:33 +0200 ** Changed in: ubuntu-image (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1704979 Title: The snap.sh autopkgtest suite failes on non amd64/i386 arches Status in Ubuntu Image: Fix Committed Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: Fix Released Status in ubuntu-image source package in Yakkety: Invalid Status in ubuntu-image source package in Zesty: Fix Released Bug description: [Impact] With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and arm64 will fail (the snap.sh test). This test does not make sense to be run as part of .deb migration as it's testing snap buildability - it's a bad idea to mix those two worlds. [Test Case] Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped). [Regression Potential] None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull- request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users. [Original Description] We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu- image 1.1 for armhf, ppc64el and s390x. By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non- snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed. In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with: error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-image/+bug/1704979/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1704979] Re: The snap.sh autopkgtest suite failes on non amd64/i386 arches
** Description changed: + [Impact] + + With the current ubuntu-image 1.1, it is impossible for the package to + migrate to the release pocket as the autopkgtests for armhf, ppc64el and + am64 will be failing (the snap.sh test). This test does not make sense + to be ran as part of .deb migration as it's testing snap buildability - + it's a bad idea to mix those two worlds. + + [Test Case] + + Make sure that all the autopkgtests pass for all architectures (with the + snap.sh test skipped). + + [Regression Potential] + + None. This is only a test change. Skipping the test on package migration + introduces no real possibility of regressions. Snap buildability is + checked during the github source CI for each pull-request. Besides, snap + buildability is a feature of the source that is not used by the .deb + parts and is completely irrelevant to users. + + [Original Description] + We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu-image 1.1 for armhf, ppc64el and s390x. By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu- image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non-snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed. In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with: error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. ** Changed in: ubuntu-image (Ubuntu Yakkety) Status: New => Invalid ** Changed in: ubuntu-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1704979 Title: The snap.sh autopkgtest suite failes on non amd64/i386 arches Status in Ubuntu Image: Fix Committed Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: New Status in ubuntu-image source package in Yakkety: Invalid Status in ubuntu-image source package in Zesty: New Bug description: [Impact] With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and am64 will be failing (the snap.sh test). This test does not make sense to be ran as part of .deb migration as it's testing snap buildability - it's a bad idea to mix those two worlds. [Test Case] Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped). [Regression Potential] None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull- request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users. [Original Description] We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu- image 1.1 for armhf, ppc64el and s390x. By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non- snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed. In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with: error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-image/+bug/1704979/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators
[Group.of.nepali.translators] [Bug 1704979] Re: The snap.sh autopkgtest suite failes on non amd64/i386 arches
This bug was fixed in the package ubuntu-image - 1.1+17.10ubuntu3 --- ubuntu-image (1.1+17.10ubuntu3) artful; urgency=medium * Only run the snap.sh test on github PRs as it doesn't make sense to run it as part of regular deb package migration. (LP: #1704979) -- Łukasz 'sil2100' Zemczak Wed, 19 Jul 2017 15:31:06 +0200 ** Changed in: ubuntu-image (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1704979 Title: The snap.sh autopkgtest suite failes on non amd64/i386 arches Status in Ubuntu Image: In Progress Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: New Status in ubuntu-image source package in Yakkety: New Status in ubuntu-image source package in Zesty: New Bug description: We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu- image 1.1 for armhf, ppc64el and s390x. By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non- snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed. In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with: error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-image/+bug/1704979/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
