Created by Francis Ginther and last modified
Get this branch:
bzr branch lp:~fginther/britney/disable-boottest
Only Francis Ginther can upload to this branch. If you are Francis Ginther please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Francis Ginther

Recent revisions

510. By Francis Ginther

Disable boottest.

509. By Martin Pitt

Autopkgtest: Trigger LXC from linux only on valid architectures

If the linux source package does not build any binaries on the given
architecture, don't trigger an LXC test for it.

508. By Martin Pitt

autopkgtest.py: Drop unused itertools

507. By Martin Pitt

Autopkgtest: Fix updating results with explicit triggers

When fetching a result with explicit triggers, always update self.results, not
just when we have a pending trigger for it. Otherwise satisfied_triggers will
be empty after reading the first result, and we clobber test results for all
triggers with the latest result.

506. By Martin Pitt

Autopkgtest: Collect results for requested tests before submitting

When we need to blow away and rebuild results.cache we want to avoid
re-triggering all tests. Thus collect already existing results for requested
tests before submitting new requests.

This is rather hackish now, as fetch_one_result() now has to deal with both
self.requested_tests and self.pending_tests. The code should be refactored to
eliminate one of these maps.

505. By Martin Pitt

Autopkgtest: Track/cache results by triggering package

When downloading results, check the ADT_TEST_TRIGGERS var in testinfo.json to
get back the original trigger that previous britney runs requested the test run
for. This allows us to much more precisely map a test result to an original
test request.

In order to tell apart test results which pass/fail depending on the package
which triggers them (in particular, if that is a kernel), we must keep track of
pass/fail results on a per-trigger granularity. Rearrange the results map

Keep the old "latest test result applies to all triggers of this pkg/version"
logic around as long as we still have existing test results without

ATTENTION: This breaks the format of results.cache, so this needs to be removed
when rolling this out.

504. By Martin Pitt

Autopkgtest: Trim triggered tests for gccgo-5

gccgo-5 exists in Ubuntu 15.04 only and builds all binary packages of gcc-5.
Triggering all tests is pointless and a big waste of test resources, so trim
down the list to actually useful ones. This can be dropped when 15.04 goes EOL.

503. By Martin Pitt

Autopkgtest: Ignore results without package/version

We often get "tmpfail" results (repeated failure to start cloud instance, etc.)
with no package/version at all. Stop attributing them to the latest pending
request for that package, as that has already messed up some results. With
moving to tracking test triggers in testinfo.jar and running multiple test
requests for each triggering kernel version it becomes completely impossible to
interpret anything into a tmpfail result without testpkg-version, so just
ignore them.

This will leave some orphaned entries in pending.txt and thus require manual
retries after fixing the tmpfail reason. But this needs to happen anyway, so
this does not complicate operation but instead shows those as "in progress"
instead of "regression".

502. By Martin Pitt

Autopkgtest: Include triggering package version in test request params

So far we only added the triggering test name. Add the version as well, so that
we'll retain the complete trigger information in result.tar's testinfo.json in
swift. This will allow us to completely reconstruct our results.cache from
scratch without losing any trigger information.

This isn't significantly harder to parse from shell either (in tests): You can
still iterate over $ADT_TEST_TRIGGERS with a "for" loop and split package and
version on '/'.

501. By Martin Pitt

tests/mock_swift.py: Support adding testinfo.json

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.