linaro-release team mailing list archive

[Fathi Boudra <fathi.boudra@xxxxxxxxxx>]

On 16 November 2011 18:59, Loïc Minier <lool@xxxxxxxx> wrote:
> On Wed, Nov 16, 2011, Данило Шеган wrote:
>> linaro-image-tools are designed to run on different development hosts.
>>
>> As an ugly hack, we could perhaps introduce full test suite runs inside
>> the package build to leverage the pre-existing Launchpad automated build
>> services. If a package fails to build on a particular Ubuntu
>> release/arch, we'd see the problem. That'd be quick and dirty, but
>> would, at the same time, be abusing package building process (imho, at
>> least).
>
>  The testsuite was definitely enabled during package build when I
>  was uploading to Ubuntu, I still see it in e.g. the 0.4.3-0ubuntu2
>  packaging, but the Debian unstable packaging which someone has synced
>  into Ubuntu (and which apparently started from the Ubuntu packaging
>  anyway) doesn't run the testsuite anymore, no idea why.

The package from PPA doesn't have the tests enabled because (afair) it
required access to internet during the build.
When I took over the package maintenance (2011.08), the tests were
already disabled.

>  Fathi, would you please:
>  - re-add running the testsuite to the packaging
discussed with salgado, it seems the testsuite doesn't require/fail
anymore due to missing internet access.

>  - re-add the debian/changelog entries from the Ubuntu package you
>   copied over
There's no reason to do that. We have a different packaging for the
PPA and Debian/Ubuntu Oneiric/Precise.
The latter packages were re-done from scratch.

>  - consider changing Vcs-Bzr: lp:ubuntu/linaro-image-tools unless that's
>   truly where the current *Debian* packaging is kept?
It's considered but as mentioned, we have 2 different packaging.
For PPA, where we should keep lucid running and have a packaging to
easy the backport.
For current distro, using dh_python2.
We need 2 branches and "current" packaging isn't kept anywhere atm

>  The current build-deps are quite long just to run the testsuite.

-- 
You received this bug notification because you are a member of linaro-
infrastructure-drivers, which is the registrant for Linaro Image Tools.
https://bugs.launchpad.net/bugs/888555

Title:
  Set up l-i-t testing on multiple archs and releases

Status in Linaro Image Tools:
  Triaged

Bug description:
  We need to test l-i-t on all supported releases and architectures. We
  have seen a number of cases where new features are later found to not
  work on old releases or older versions of Python. We just had a
  problem with linaro-hwpack create not working on Oneiric 64 bit, but
  happily work on 32 bit.

  For testing new code and especially for release testing we would need
  to set something up to enable this since a single developer won't have
  access to all variants of installations.

  We could perhaps automate something to set up virtual machines on
  local dev PC:s with possible impact on TDD since tests would take many
  times longer to run. Perhaps we can use LAVA?

  For full coverage we'd need to test on all possible combinations of
  the below components (please add to them as you see fit), but that is
  probably overkill.

  Python:
      2.6
      2.7

  Ubuntu:
      Precise
      Oneiric
      Natty
      Maverick
      (how far back do we want to ensure support?)

  Archs:
      i386
      x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-image-tools/+bug/888555/+subscriptions