tests: enable regression, upgrade and completion test suites for fedora #3622

Merged
merged 33 commits into from Aug 7, 2017

Conversation

Projects
None yet
5 participants
Contributor

sergiocazzolato commented Jul 26, 2017

Enable 3 test suites for fedora.

Simon Fels and others added some commits Jun 8, 2017

@@ -426,6 +426,8 @@ install -m 644 -D data/info %{buildroot}%{_libexecdir}/snapd/info
# Install bash completion for "snap"
install -m 644 -D data/completion/snap %{buildroot}%{_datadir}/bash-completion/completions/snap
+install -m 644 -D data/completion/complete.sh %{buildroot}%{_libexecdir}/snapd
+install -m 644 -D data/completion/etelpmoc.sh %{buildroot}%{_libexecdir}/snapd
@Conan-Kudo

Conan-Kudo Jul 26, 2017

Contributor

Why are completion files being installed into %{_libexecdir}/snapd?

@sergiocazzolato

sergiocazzolato Jul 26, 2017

Contributor

Thanks for reviewing
It is where other scripts are looking for to make snap-completion.
Any suggestion about how to improve it?

@zyga

zyga Jul 27, 2017

Contributor

@Conan-Kudo Note that those are special files that make snapd implement completion internally. The things you are thinking about about are in the usual location.

@Conan-Kudo

Conan-Kudo Jul 27, 2017

Contributor

It's fine, just making sure it's supposed to be there.

tests/lib/pkgdb.sh
@@ -315,6 +315,16 @@ distro_install_build_snapd(){
fi
}
+distro_get_package_extention() {
@Conan-Kudo

Conan-Kudo Jul 26, 2017

Contributor

extention -> extension

tests/upgrade/basic/task.yaml
@@ -39,7 +40,8 @@ execute: |
echo Do upgrade
# allow-downgrades prevents errors when new versions hit the archive, for instance,
# trying to install 2.11ubuntu1 over 2.11+0.16.04
- distro_install_local_package --allow-downgrades "$GOHOME"/snapd*.deb
+ pkg_extention="$(distro_get_package_extention)"
@Conan-Kudo

Conan-Kudo Jul 26, 2017

Contributor

extention -> extension

sergiocazzolato added some commits Jul 26, 2017

Codecov Report

Merging #3622 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           master   #3622      +/-   ##
=========================================
- Coverage   75.21%   75.2%   -0.01%     
=========================================
  Files         384     387       +3     
  Lines       33538   33452      -86     
=========================================
- Hits        25226   25159      -67     
+ Misses       6491    6481      -10     
+ Partials     1821    1812       -9
Impacted Files Coverage Δ
interfaces/builtin/joystick.go 45% <0%> (-25%) ⬇️
interfaces/builtin/framebuffer.go 27.27% <0%> (-21.57%) ⬇️
interfaces/builtin/ubuntu_download_manager.go 31.25% <0%> (-18.75%) ⬇️
interfaces/builtin/time_control.go 57.14% <0%> (-16.55%) ⬇️
interfaces/builtin/physical_memory_observe.go 57.14% <0%> (-16.55%) ⬇️
interfaces/builtin/physical_memory_control.go 57.14% <0%> (-16.55%) ⬇️
interfaces/builtin/io_ports_control.go 61.29% <0%> (-14.32%) ⬇️
interfaces/builtin/hardware_random_control.go 61.53% <0%> (-10.69%) ⬇️
interfaces/builtin/gpio.go 50.98% <0%> (-10.04%) ⬇️
interfaces/builtin/hardware_random_observe.go 61.53% <0%> (-9.9%) ⬇️
... and 57 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf28721...ff9c0cb. Read the comment docs.

zyga approved these changes Aug 4, 2017

LGTM with the comment on classic confinement checks. I think this could be done via snapd's API query.

@@ -43,3 +43,23 @@ install_generic_consumer() {
snap install --dangerous generic-consumer/*.snap
rm -rf generic-consumer
}
+
+is_classic_confinement_supported() {
@zyga

zyga Aug 4, 2017

Contributor

I think it'd be better to ask snapd about it, so that we have to maintain less tables. Also this is likely to change a little (in what it really mans to support it) so this may (hopefully) go away.

@morphis

morphis Aug 4, 2017

Contributor

We already ask snapd if strict confinement is supported or not. Asking for classic confinement would be just another option.

@@ -61,7 +61,7 @@ backends:
kernel: GRUB 2
workers: 4
- fedora-25-64:
- workers: 1
+ workers: 2
@morphis

morphis Aug 4, 2017

Contributor

Why do we bump the number of workers to two? @niemeyer requested this to be a single one for the time being. Anything has changed since then?

@zyga

zyga Aug 4, 2017

Contributor

Not sure but I think it's because we now have more tests than before.

@@ -43,3 +43,23 @@ install_generic_consumer() {
snap install --dangerous generic-consumer/*.snap
rm -rf generic-consumer
}
+
+is_classic_confinement_supported() {
@zyga

zyga Aug 4, 2017

Contributor

I think it'd be better to ask snapd about it, so that we have to maintain less tables. Also this is likely to change a little (in what it really mans to support it) so this may (hopefully) go away.

@morphis

morphis Aug 4, 2017

Contributor

We already ask snapd if strict confinement is supported or not. Asking for classic confinement would be just another option.

Contributor

Conan-Kudo commented Aug 6, 2017

I'm not a fan of commits that just say "WIP". Can we get some descriptive commit messages for the two "WIP" commits?

@zyga zyga merged commit ac443ce into snapcore:master Aug 7, 2017

7 checks passed

artful-amd64 autopkgtest finished (success)
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
xenial-amd64 autopkgtest finished (success)
Details
xenial-i386 autopkgtest finished (success)
Details
xenial-ppc64el autopkgtest finished (success)
Details
yakkety-amd64 autopkgtest finished (success)
Details
zesty-amd64 autopkgtest finished (success)
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment