group.of.nepali.translators team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

Public bug reported:

[Impact]

 * sbuild adt tests assume that the test is running on the host, which
is the current devel series, which is not the case when adt tests are
running as part of SRU regression testing.

[Test Case]

 * ADT test should pass

[Regression Potential]

 * sbuild itself is not modified, only the autopkgtest themself are
fixed to not make unrealistic assumptions

[Other Info]
 
 * Original bug report / problem description

src:sbuild has test build-procenv which can only pass in devel series,
as it assumes that the release test is running is the devel series.

This was true, until we started to run adt tests for stable releases and
SRUs.

Here is the detailed log of running build-procenv on xenial, whilst
devel series is called artful:

# ADTTMP=$(mktemp -d) sh -x debian/tests/build-procenv
+ set -e
+ pkg=procenv
+ components=
+ lsb_release -is
+ tr [A-Z] [a-z]
+ distro=ubuntu
+ [ -z ubuntu ]
+ lsb_release -cs
+ host_release=xenial
+ [ -z xenial ]
+ [ ubuntu = ubuntu ]
+ distro-info --devel
+ release=artful
+ components=main,universe
+ dpkg --print-architecture
+ url=http://archive.ubuntu.com/ubuntu
+ dpkg --print-architecture
+ arch=amd64
+ [ -z amd64 ]
+ [ -z /tmp/tmp.QYJvzqYkbV ]
+ dir=/tmp/tmp.QYJvzqYkbV/schroot-artful
+ chroot=artful-amd64-sbuild
+ schroot -l
+ schroots=
+ [ -n  ]
+ [ -z  ]
+ apt-config shell http_proxy Acquire::http::Proxy
+ RES=
+ eval
+ export http_proxy
+ echo INFO: using proxy: (none)
INFO: using proxy: (none)
+ echo INFO: Downloading source for package 'procenv' from release 'artful'
INFO: Downloading source for package 'procenv' from release 'artful'
+ apt-get source --download-only -o APT::Sandbox::User=root procenv/artful
Reading package lists... Done
E: Unable to find a source package for procenv

There are a couple of options here depending what we want to test. We
can either build procenv from $current on $current release -> this will
test that e.g. SRUs in xenial, do not break building packages for xenial
on xenial.

Or we can try to always build procenv from $devel in $devel chroot ->
this will test that all currently supported releases, can build packages
for $devel series.

** Affects: sbuild (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: sbuild (Ubuntu Xenial)
     Importance: Medium
     Assignee: Dimitri John Ledkov (xnox)
         Status: In Progress

** Affects: sbuild (Ubuntu Yakkety)
     Importance: Medium
     Assignee: Dimitri John Ledkov (xnox)
         Status: In Progress

** Also affects: sbuild (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: sbuild (Ubuntu Artful)
   Importance: Undecided
       Status: New

** Also affects: sbuild (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Also affects: sbuild (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** No longer affects: sbuild (Ubuntu Zesty)

** No longer affects: sbuild (Ubuntu Artful)

** Changed in: sbuild (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/1686064

Title:
  sbuild ADT test can only pass in devel series

Status in sbuild package in Ubuntu:
  Fix Released
Status in sbuild source package in Xenial:
  In Progress
Status in sbuild source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * sbuild adt tests assume that the test is running on the host, which
  is the current devel series, which is not the case when adt tests are
  running as part of SRU regression testing.

  [Test Case]

   * ADT test should pass

  [Regression Potential]

   * sbuild itself is not modified, only the autopkgtest themself are
  fixed to not make unrealistic assumptions

  [Other Info]
   
   * Original bug report / problem description

  src:sbuild has test build-procenv which can only pass in devel series,
  as it assumes that the release test is running is the devel series.

  This was true, until we started to run adt tests for stable releases
  and SRUs.

  Here is the detailed log of running build-procenv on xenial, whilst
  devel series is called artful:

  # ADTTMP=$(mktemp -d) sh -x debian/tests/build-procenv
  + set -e
  + pkg=procenv
  + components=
  + lsb_release -is
  + tr [A-Z] [a-z]
  + distro=ubuntu
  + [ -z ubuntu ]
  + lsb_release -cs
  + host_release=xenial
  + [ -z xenial ]
  + [ ubuntu = ubuntu ]
  + distro-info --devel
  + release=artful
  + components=main,universe
  + dpkg --print-architecture
  + url=http://archive.ubuntu.com/ubuntu
  + dpkg --print-architecture
  + arch=amd64
  + [ -z amd64 ]
  + [ -z /tmp/tmp.QYJvzqYkbV ]
  + dir=/tmp/tmp.QYJvzqYkbV/schroot-artful
  + chroot=artful-amd64-sbuild
  + schroot -l
  + schroots=
  + [ -n  ]
  + [ -z  ]
  + apt-config shell http_proxy Acquire::http::Proxy
  + RES=
  + eval
  + export http_proxy
  + echo INFO: using proxy: (none)
  INFO: using proxy: (none)
  + echo INFO: Downloading source for package 'procenv' from release 'artful'
  INFO: Downloading source for package 'procenv' from release 'artful'
  + apt-get source --download-only -o APT::Sandbox::User=root procenv/artful
  Reading package lists... Done
  E: Unable to find a source package for procenv

  There are a couple of options here depending what we want to test. We
  can either build procenv from $current on $current release -> this
  will test that e.g. SRUs in xenial, do not break building packages for
  xenial on xenial.

  Or we can try to always build procenv from $devel in $devel chroot ->
  this will test that all currently supported releases, can build
  packages for $devel series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1686064/+subscriptions