~fginther/britney/disable-boottest : changes

~fginther/britney/disable-boottest » Changes from revision 510

From Revision 510 to 491

Rev	Summary	Authors	Date
510	Disable boottest. Disable boottest.	Francis Ginther	8 years ago
509	Autopkgtest: Trigger LXC from linux only on valid architectu... 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.	Martin Pitt	8 years ago
508	autopkgtest.py: Drop unused itertools autopkgtest.py: Drop unused itertools	Martin Pitt	8 years ago
507	Autopkgtest: Fix updating results with explicit triggers 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.	Martin Pitt	8 years ago
506	Autopkgtest: Collect results for requested tests before subm... 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.	Martin Pitt	8 years ago
505	Autopkgtest: Track/cache results by triggering package 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 accordingly. 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 testinfo.json. ATTENTION: This breaks the format of results.cache, so this needs to be removed when rolling this out.	Martin Pitt	8 years ago
504	Autopkgtest: Trim triggered tests for gccgo-5 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.	Martin Pitt	8 years ago
503	Autopkgtest: Ignore results without package/version 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".	Martin Pitt	8 years ago
502	Autopkgtest: Include triggering package version in test requ... 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 '/'.	Martin Pitt	8 years ago
501	tests/mock_swift.py: Support adding testinfo.json tests/mock_swift.py: Support adding testinfo.json	Martin Pitt	8 years ago
500	autopkgtest: Check for new results on a per-architecture gra... autopkgtest: Check for new results on a per-architecture granularity In collect(), check if there are new results for failed tests on a per-architecture level. This updates results while tests for other architectures are still in progress (i. e. in self.pending_tests).	Martin Pitt	8 years ago
499	autopkgtest: Make Linux -> DKMS triggering arch specific autopkgtest: Make Linux -> DKMS triggering arch specific Only trigger DKMS tests for architectures on which the given kernel actually exists.	Martin Pitt	8 years ago
498	autopkgtest: Make tests_for_source() arch specific autopkgtest: Make tests_for_source() arch specific So far we've only calculated the reverse dependencies on amd64. This breaks when triggering packages which do not exist on some architectures, like bcmwl-kernel-source. It also makes it impossible to e. g. trigger DKMS tests on armhf only for an ARM-only kernel like linux-ti-omap4.	Martin Pitt	8 years ago
497	Autopkgtest tests: Publish test packages on all architecture... Autopkgtest tests: Publish test packages on all architectures by default This is a prerequisite for introducing per-architecture test calculation.	Martin Pitt	8 years ago
496	Only trigger autopkgtests for some key packages for gcc-* Only trigger autopkgtests for some key packages for gcc-* Through the usual reverse dependency triggering, gcc-* usually triggers many hundreds of (mostly universe) tests via libgccN. But: - This does not help to prevent compiler regressions: as all packages are built in -proposed anyway, the new compiler is being used immediately, so we can't hold it back in -proposed. - It does not trigger toolchain tests which actually are affected, most importantly binutils and linux. - This puts enormous stress onto our test infrastructure. So special case gcc by triggering binutils and linux, and fglrx-installer as a typical (and important) example of a DKMS package which also needs a compiler, and libreoffice as our favourite tool chain stress test to cover libgccN.	Martin Pitt	8 years ago
495	autopkgtest: Trigger lxc tests from linux-meta, not linux autopkgtest: Trigger lxc tests from linux-meta, not linux This is more consistent with the DKMS triggers, and will make things easier for the kernel status matrix.	Martin Pitt	8 years ago
494	run-autopkgtest: Add --trigger option run-autopkgtest: Add --trigger option	Martin Pitt	8 years ago
493	autopkgtest: Request separate tests for linux-meta* triggers autopkgtest: Request separate tests for linux-meta* triggers If a package gets triggered by several sources, we can ordinarily run just one test for all triggers. But for proposed kernels we want to run a separate test for each, so that the test can run under that particular kernel.	Martin Pitt	8 years ago
492	AutoPackageTest.submit(): Factor out calculation of requests AutoPackageTest.submit(): Factor out calculation of requests	Martin Pitt	8 years ago
491	tests/mock_swift.py: Fix ResourceWarning due to unclosed log... tests/mock_swift.py: Fix ResourceWarning due to unclosed log file	Martin Pitt	8 years ago

Older »