The Jenkins master got rebooted shortly after this failure so I don't know
if the Ops were already up to something. Neither Windows slave is currently
active so I can't see if the reboot has recovered the build or not.
Our Windows builds just generally don't seem right:
JDK 1.8 on Windows gives t
Thanks for the great work Michael,
On Apr 19, 2014, at 1:51 PM, Matt Sicker wrote:
> You can use the ExpectedException rule exactly where you expect the
> exception to be thrown. Using the @Test(expected = foo.class) (or whatever
> the attribute name was) is for the whole method. Unless you're t
Our build is successful but Jenkins is running out of memory processing JUnit
results if I understand correctly.
I wonder whether we should ask Infra to run Jenkins with a larger PermGen space
as the error message suggests or whether there is something else to do on our
end ?
Regards,
Antoine
You can use the ExpectedException rule exactly where you expect the
exception to be thrown. Using the @Test(expected = foo.class) (or whatever
the attribute name was) is for the whole method. Unless you're talking
about larger methods being tested that can throw multiple exceptions, then
that's a d
>
> buildRule.executeTarget("test1");
> ==> could the BuildFileRule use a default (test name) for executeTarget?
> buildRule.executeTarget();
>
I'm not sure it can - the same build file is often used for multiple tests,
each calling a different target, so how would we know which target was
int
> +@Rule
> +public BuildFileRule buildRule = new BuildFileRule();
> +
> +@Before
> public void setUp() {
> -configureProject("src/etc/testcases/taskdefs/available.xml");
> -executeTarget("setUp");
> +
> buildRule.configureProject("src/etc/testcases/taskdefs/
