Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Kim Lester
All, I've not been around here long enough to know/care _where_ tests are located. Nor have I studied the tests in question (so I probably don't know what I'm talking about :-) ) However I have been a developer long enough to know that ideally all tests should be self contained. Tests should

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Vincent Torri
On Sun, 19 Dec 2010, Kim Lester wrote: All, I've not been around here long enough to know/care _where_ tests are located. Nor have I studied the tests in question (so I probably don't know what I'm talking about :-) ) However I have been a developer long enough to know that ideally all

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Albin Tonnerre
On Sun, 19 Dec 2010 09:11 +0100, Vincent Torri wrote : tests are for developpers, not packagers That is terribly wrong. Packagers care about testsuites for one simple reason: as thoroughly as developers may be testing the code, that will never guarantee proper behaviour on the system on which

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Thomas Sachau
Am 19.12.2010 04:51, schrieb Carsten Haitzler (The Rasterman): On Sat, 18 Dec 2010 17:14:02 +0100 Thomas Sachau to...@gentoo.org said: Attached is a build log with the failures. ok. since your position is that tests should work even if u enable them and they cant connect to a display, or

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread The Rasterman
On Sun, 19 Dec 2010 10:28:20 +0100 Albin Tonnerre lu...@debian.org said: On Sun, 19 Dec 2010 09:11 +0100, Vincent Torri wrote : tests are for developpers, not packagers That is terribly wrong. Packagers care about testsuites for one simple reason: as thoroughly as developers may be testing

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread The Rasterman
On Sun, 19 Dec 2010 13:26:21 +0100 Thomas Sachau to...@gentoo.org said: Am 19.12.2010 04:51, schrieb Carsten Haitzler (The Rasterman): On Sat, 18 Dec 2010 17:14:02 +0100 Thomas Sachau to...@gentoo.org said: Attached is a build log with the failures. ok. since your position is that

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Albin Tonnerre
On Sun, 19 Dec 2010 22:14 +0900, Carsten Haitzler wrote : On Sun, 19 Dec 2010 10:28:20 +0100 Albin Tonnerre lu...@debian.org said: On Sun, 19 Dec 2010 09:11 +0100, Vincent Torri wrote : tests are for developpers, not packagers That is terribly wrong. Packagers care about testsuites

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Thomas Sachau
Am 19.12.2010 14:16, schrieb Carsten Haitzler (The Rasterman): On Sun, 19 Dec 2010 13:26:21 +0100 Thomas Sachau to...@gentoo.org said: Am 19.12.2010 04:51, schrieb Carsten Haitzler (The Rasterman): On Sat, 18 Dec 2010 17:14:02 +0100 Thomas Sachau to...@gentoo.org said: packagers should test

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Vincent Torri
On Sun, 19 Dec 2010, Albin Tonnerre wrote: On Sun, 19 Dec 2010 09:11 +0100, Vincent Torri wrote : tests are for developpers, not packagers That is terribly wrong. Packagers care about testsuites for one simple reason: as thoroughly as developers may be testing the code, that will never

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Albin Tonnerre
On Sun, 19 Dec 2010 19:49 +0100, Vincent Torri wrote : On Sun, 19 Dec 2010, Albin Tonnerre wrote: On Sun, 19 Dec 2010 09:11 +0100, Vincent Torri wrote : tests are for developpers, not packagers That is terribly wrong. Packagers care about testsuites for one simple reason: as

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Albin Tonnerre
On Sun, 19 Dec 2010 20:02 +0100, Vincent Torri wrote : I understand users not listening or unwilling to fix the suite to fit their needs is a pain, but let's not make it an even greater pain for people who just want to use it and manage to. Things have improved a lot as far as packaging is

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread The Rasterman
On Sun, 19 Dec 2010 15:29:36 +0100 Thomas Sachau to...@gentoo.org said: Am 19.12.2010 14:16, schrieb Carsten Haitzler (The Rasterman): On Sun, 19 Dec 2010 13:26:21 +0100 Thomas Sachau to...@gentoo.org said: Am 19.12.2010 04:51, schrieb Carsten Haitzler (The Rasterman): On Sat, 18 Dec

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-19 Thread Mike McCormack
On 12/19/2010 09:26 PM, Thomas Sachau wrote: test the package. As already said, tests should not require external services like X to run and if some tests need such a service, they should be skipped or there should be an option to skip them. You want to verify EFL, which is all about

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-18 Thread Albin Tonnerre
On Sat, 18 Dec 2010 17:14 +0100, Thomas Sachau wrote : Attached is a build log with the failures. Are you by any chance building on a headless machine, or in a tty ? If so, that failure is expected - the test fails whenever ecore can't reach the X server. I ended up disabling this test

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-18 Thread Vincent Torri
hey On Sat, 18 Dec 2010, Thomas Sachau wrote: Attached is a build log with the failures. thanks for the log, but: 1) configure gcc to display english messages 2) please strip the log so that it contains the usefull messages 3) if it's about DSO (i looked at the log and it is too huge to

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-18 Thread The Rasterman
On Sat, 18 Dec 2010 17:14:02 +0100 Thomas Sachau to...@gentoo.org said: Attached is a build log with the failures. gentoo ebuild problem - not ecore. pay closer attention to what failed and have a think about it :) -- - Codito, ergo sum - I code, therefore I am -- The

Re: [E-devel] ecore tests fail with beta3 tarballs

2010-12-18 Thread The Rasterman
On Sat, 18 Dec 2010 17:14:02 +0100 Thomas Sachau to...@gentoo.org said: Attached is a build log with the failures. ok. since your position is that tests should work even if u enable them and they cant connect to a display, or that we need to go fine-graining tests just so you can --enable