I just now am fixing some demo/jvmti tests, which seemed to fail
with samevm and pass with othervm, the problem seemed to be that
when run with samevm, the current directory (user.dir) is different.
So if a test is assuming anything about the current directory, that
could be an issue. But again,
Kelly O'Hair wrote:
I just now am fixing some demo/jvmti tests, which seemed to fail
with samevm and pass with othervm, the problem seemed to be that
when run with samevm, the current directory (user.dir) is different.
The current directory should always be the scratch/ subdirectory of the
wor
Jonathan Gibbons wrote:
Kelly O'Hair wrote:
I just now am fixing some demo/jvmti tests, which seemed to fail
with samevm and pass with othervm, the problem seemed to be that
when run with samevm, the current directory (user.dir) is different.
The current directory should always be the scratc
But I think your shell tests may have been just problematic when
multiple
instances of them are run on one machine, like a port number problem.
That's hard for me to diagnose quickly, so when tests failed with
any kind of BindException or 'address already in use', I just added
them to the list a
Max (Weijun) Wang wrote:
But I think your shell tests may have been just problematic when multiple
instances of them are run on one machine, like a port number problem.
That's hard for me to diagnose quickly, so when tests failed with
any kind of BindException or 'address already in use', I jus
