The problem I hit usually:
There are some packages that rely on X for some tests, that way, when I
for example emerge tk, it's nearly impossible to keep working because I
get tons of windows opened and closed.
Wouldn't be better to make that tests *always* use virtual X?
Thanks for your
On 07/19/2013 02:50 PM, Pacho Ramos wrote:
The problem I hit usually:
There are some packages that rely on X for some tests, that way, when I
for example emerge tk, it's nearly impossible to keep working because I
get tons of windows opened and closed.
Wouldn't be better to make that
Pacho Ramos schrieb:
Wouldn't be better to make that tests *always* use virtual X?
One issue could be that Xvfb is not very representative of a modern X
server any more. I am not sure how this affects the validity of the test
results. This problem however exists already with all virtualx users
On Fri, Jul 19, 2013 at 7:50 AM, Pacho Ramos pa...@gentoo.org wrote:
Wouldn't be better to make that tests *always* use virtual X?
As Patrick said, yes, if they don't they are broken. Especially so if Xvfb
does not represent a modern X anymore, as that would mean that tests will
behave
On Fri, Jul 19, 2013 at 1:40 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
[...]
And non-deterministic tests are stupid, useless, broken tests.
Amen.
Even though there is that 1% of cases in where you want to have
non-deterministic tests. For instance, if you want to run the same
test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/07/13 08:20 AM, Fabio Erculiani wrote:
On Fri, Jul 19, 2013 at 1:40 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
[...]
And non-deterministic tests are stupid, useless, broken tests.
Amen. Even though there is that 1% of cases
On Fri, Jul 19, 2013 at 1:20 PM, Fabio Erculiani lx...@gentoo.org wrote:
Even though there is that 1% of cases in where you want to have
non-deterministic tests. For instance, if you want to run the same
test thousands of times and randomly pick an initial state to see if
you spot a scenario
