linaro-release team mailing list archive

[Fathi Boudra <fathi.boudra@xxxxxxxxxx>]

On 10 November 2011 18:12, James Tunnicliffe <launchpad@xxxxxxxxxxxxx> wrote:
> I think we will want to start with a clean machine, install the listed
> deps, check out the latest version of linaro-image-tools, run all unit
> tests, create an image for a bit of hardware (probably Panda since I
> seem to recall we have the most of those), boot the image.
>
> If we can fold the install and unit test part into the build process
> then that will work, but it feels like a bit of a hack!
>
> Ideally we would use a VM containing an up to date version of the OS we
> are testing on, so we would need a method of keeping the OS images up to
> date, then taking a copy of them each time we use them in a test to
> ensure there isn't anything left over from an old run.

schroot will provide the "VM" up to date and clean.

> We could also use a clean VM for package testing to make sure it
> installs all the prerequisites. Perhaps we should have a dev PPA that is
> being continuously built so we use that for the normal tests and can
> just grab the latest known good package from it at release time.

that's the recipe to build l-i-t daily, we can use the staging overlay
like any other package from the CI loop.

I don't see much difference with my proposal except using a VM instead
of a schroot setup.

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

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