linaro-release team mailing list archive

[Guilherme Salgado <guilherme.salgado@xxxxxxxxxx>]

On Wed, 2011-11-16 at 13:42 +0000, Данило Шеган 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).
> 
> Ideally though, we'd be able to run full testsuite on all of our
> supported hosts either pre- or post-commit to lp:linaro-image-tools
> (hey, nothing beats finding problems early). We have a gazillion of
> build services, but none of them is exactly what we need here.

I've thought about that and even started doing it, but I gave up when I
realized linaro-image-tools is "Architecture:all" so it will not be
built on all architectures -- in fact it will probably be built only on
i386.

We could have separate LP recipes with different packaging branches; one
for each architecture we want to build on.  But then it might not be too
cheap anymore.

-- 
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