devtool and recipetool selftests both contain assertNotIn() calls which cause oe-selftest to fail if there's a WARNING in the commands output. This results in a failure when running builds on the debian-testing worker on the autobuilder cluster because the non-versioned/rolling release Debian testing distro isn't listed in SANITY_TESTED_DISTROS and therefore emits a warning from sanity.bbclass: WARNING: Host distribution "debian" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. If we really don't want oe-selftest to run on distros which aren't in SANITY_TESTED_DISTROS we should make oe-selftest check and warn/error for this up front, otherwise we should hack the whitelist so the tests don't fail.
I think the selftest buildset should set SANITY_TESTED_DISTROS="".
Perhaps the tested distros list is outdated, I get the same error for F25 and it should be white-listed as it is tested: https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest See the buildslaves list.
(In reply to comment #2) > Perhaps the tested distros list is outdated, I get the same error for F25 > and it should be white-listed as it is tested: > > > https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest > > See the buildslaves list. I refrain from this comment, the right way to go is to ignore the sanity tested distros, now the question for me is whether this is ignored on request or by default.
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=6f4622c88933defbf05812614c240289f8bf7177