~ubuntu-release/britney/britney2-ubuntu : changes

~ubuntu-release/britney/britney2-ubuntu » Changes from revision 599

From Revision 586 to 567

Rev	Summary	Authors	Date
586	run-autopkgtest: put requests into appropriate per-context A... run-autopkgtest: put requests into appropriate per-context AMQP queue	Martin Pitt	8 years ago
585	Send PPA test requests into PPA AMQP queues Send PPA test requests into PPA AMQP queues This separates them from Ubuntu and upstream test requests, avoids that any of those can completely starve the other two, and makes queues easier to manage.	Martin Pitt	8 years ago
584	Don't check components when testing PPAs, as they do not hav... Don't check components when testing PPAs, as they do not have this concept	Martin Pitt	8 years ago
583	Teach excuse_unsat_deps() about components ogre model Teach excuse_unsat_deps() about components ogre model	Martin Pitt	8 years ago
582	Add autopkgtest test case for different tested package versi... Add autopkgtest test case for different tested package versions on different architectures	Martin Pitt	8 years ago
581	Add version-independent per-architecture force-badtest hints Add version-independent per-architecture force-badtest hints Some tests are known-broken on a particular architecture only. force-badtest'ing the entire version is overzealous as it hides regressions on the other architectures that we expect to work. It's also hard to maintain as the version has to be bumped constantly. Support hints of the form "force-badtest srcpkg/architecture/all" (e. g. "force-badtest chromium-browser/armhf/all"). The special version "all" will match any version.	Martin Pitt	8 years ago
580	Support force-{bad,skip}test hints for multiple versions Support force-{bad,skip}test hints for multiple versions	Martin Pitt	8 years ago
579	Autopkgtest: Show force-badtest results more prominently Autopkgtest: Show force-badtest results more prominently Add new state "IGNORE-FAIL" for regressions which have a 'force' or 'force-badtest' hint. In the HTML, show them as yellow "Ignored failure" (without a retry link) instead of "Regression", and drop the separate "Should wait for ..." reason, as that is hard to read for packages with a long list of tests. This also makes retry-autopkgtest-regressions more useful as this will now only run the "real" regressions.	Martin Pitt	8 years ago
578	Merge change from Niels Thykier to fix --hint-tester Merge change from Niels Thykier to fix --hint-tester	Iain Lane	8 years ago
577	run-autopkgtest: Add --all-proposed option run-autopkgtest: Add --all-proposed option This is useful if two packages in -proposed depend on each other for successful testing but don't have versioned dependencies.	Martin Pitt	8 years ago
576	Adjust URL for retrying failed tests Adjust URL for retrying failed tests retry.cgi is now request.cgi.	Martin Pitt	8 years ago
575	run-autopkgtest: Add --build-git option run-autopkgtest: Add --build-git option	Martin Pitt	8 years ago
574	Autopkgtest: Trim triggered tests for gccgo-6 Autopkgtest: Trim triggered tests for gccgo-6 Similar to commit 504, gccgo-6 builds all binary packages of gcc-5.	Martin Pitt	8 years ago
573	Don't use latest timestamp from results.cache if it is share... Don't use latest timestamp from results.cache if it is shared When using a shared results cache with PPAs (silos) we cannot rely on the latest time stamp from the distro's results.cache. As soon as there is a new run for a package in Ubuntu proper, that updated time stamp hides all previous results for the PPA, and causes tests to be re-requested unnecessarily.	Martin Pitt	8 years ago
572	Remove extra debug logging again Remove extra debug logging again Revert commit 568, LP#1537866 is understood now.	Martin Pitt	8 years ago
571	Add retry links to PPA excuses Add retry links to PPA excuses autopkgtest-retrier supports "ppa=" GET arguments now.	Martin Pitt	8 years ago
570	Fail hard on unexpected HTTP errors Fail hard on unexpected HTTP errors In the CI train we sometimes run into transient "HTTP Error 502: Proxy Error". As we don't keep a results.cache there, this leads to retrying tests for which we already have a result in swift, but can't download it. Treat this as a hard failure now, to let the next britney run try again. This will also tell us if we need to handle any other status code than 200, 204 (empty result), or 401 (container does not exist).	Martin Pitt	8 years ago
569	mock_swift.py: Use status code 401 on nonexisting container,... mock_swift.py: Use status code 401 on nonexisting container, like the real Swift	Martin Pitt	8 years ago
568	Add more debug logging to investigate LP#1537866 Add more debug logging to investigate LP#1537866	Martin Pitt	8 years ago
567	Add option for using a shared r/o results.cache Add option for using a shared r/o results.cache This is needed by the CI train, where we (1) don't want to cache intermediate results for PPA runs, as they might "accidentally" pass in between and fail again for the final silo, (2) want to seed britney with the Ubuntu results.cache, to detect regressions relative to Ubuntu. Introduce ADT_SHARED_RESULTS_CACHE option which can point to a path to results.cache. This will then not be updated by britney.	Martin Pitt	8 years ago

Older »