On Wed, Jun 20, 2012 at 6:48 AM, Eric Ayers zun...@google.com wrote:
Now, the problem with diagnosing this is that the file is set to be
deleted on exit. So after the program exits, you can't see how
ridiculously huge the file might have been. To test that theory, you
could try commenting
Hey,
I'm running into the same thing on a Linux workstation. It's a virtual
instance, so I'm not sure if that might have something to do with it, but
it's definitely strange.
Here's one exception that I see:
[junit] Exception in thread pool-1-thread-1
java.lang.RuntimeException: Unable to
I have had periodic failures like this that go away when I re-run it.
--
John A. Tamplin
Software Engineer (GWT), Google
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
[junit] Exception in thread pool-1-thread-569
java.lang.NullPointerException [junit] at
com.google.gwt.dev.util.DiskCache.transferToStream(DiskCache.java:187)
[junit] at
com.google.gwt.dev.util.DiskCacheToken.writeObject(DiskCacheToken.java:91)
At the very
Hey,
So, is ant test supposed to run to completion on a reasonable
dev machine? I don't know that I've ever had it work, and so don't
generally run it.
But I was feeling guilty tonight, so tried again, went away for awhile,
and came back to my RAM (12gb) and CPUs both pegged. And lots of these
On Sat, Jun 9, 2012 at 10:26 PM, Stephen Haberman
stephen.haber...@gmail.com wrote:
So, is ant test supposed to run to completion on a reasonable
dev machine? I don't know that I've ever had it work, and so don't
generally run it.
I don't run it that often (we have a distributed test farm
Hi,
I was trying to execute the test but I got this error:
...
...
...
-filter.props:
build:
compile.emma.if.enabled:
-compile.emma.if.enabled:
compile.tests:
compile.emma.if.enabled:
-compile.emma.if.enabled:
compile.tests:
[mkdir] Created dir: /Users/Luis/Documents/workspace-gwt/gwt/build/
Reviewers: Ray Ryan,
Description:
1. Problems in assertFirstHeader().
1.1. invalid condition;
1.2. invalid reference on second argument.
2. Use addStatement() instead of addInitStatement(), because same is
done everywhere.
3. Small tweaks.
4. Set of tests, including all bad cases.
Please review
