Bug#460402: [debian-mysql] Bug#460402: FTBFS on testsuite failure on armel
Am Samstag, den 12.01.2008, 15:01 +0200 schrieb Riku Voipio: Personally I would prefer that the testsuite was run, but errors would ignored on selected architectures. Thus if we get enduser bugreport of mysql, we can check if there was regressions on testsuite run for package version enduser was using. Agreed, I'll change this in the next upload. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460402: FTBFS on testsuite failure on armel
Package: mysql-dfsg-5.0 Version: 5.0.51-2 Severity: normal User: [EMAIL PROTECTED] Usertags: eabi Failed 2/484 tests, 99.59% were successful. Looking at build log[1], the testsuite errors appear to non-serious: -mysqlcheck: Got error: 2005: Unknown MySQL server host 'not_existing_host' (errno) when trying to connect +mysqlcheck: Got error: 2003: Can't connect to MySQL server on 'not_existing_host' (errno) when trying to connect -ERROR 2005 (HY000) at line 1: Unknown MySQL server host 'invalid_hostname' (errno) +ERROR 2003 (HY000) at line 1: Can't connect to MySQL server on 'invalid_hostname' (errno) The current strategy from mysql maintainers appears to not running the testsuite at all on architectures with testsuite failures. The easiest solution is to add armel to the list of architectures where testsuite is not run. personally I would prefer that the testsuite was run, but errors would ignored on selected architectures. Thus if we get enduser bugreport of mysql, we can check if there was regressions on testsuite run for package version enduser was using. [1] http://buildd.debian-ports.org/fetch.php?pkg=mysql-dfsg-5.0ver=5.0.51-2arch=armelstamp=1200113517file=logas=raw -- rm -rf only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
