Community
Participate
Working Groups
2 tests against Jenkins 1.532.2 are failing. We should check if any code changes are needed to support 1.532.2. Unexpected response from Hudson server for '/jenkins-1.532.2/job/test-succeeding/build': Created Stacktrace org.eclipse.mylyn.internal.hudson.core.client.HudsonException: Unexpected response from Hudson server for '/jenkins-1.532.2/job/test-succeeding/build': Created at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.validate(HudsonOperation.java:235) at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient$7.doValidate(RestfulHudsonClient.java:359) at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.processAndRelease(HudsonOperation.java:220) at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient$7.execute(RestfulHudsonClient.java:353) at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.run(HudsonOperation.java:167) at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient.runBuild(RestfulHudsonClient.java:361)
The fixture was aded on bug 428030. Does the gerrit build not run all fixtures? If not we should run them manually when adding new versions.
(In reply to comment #1) > The fixture was aded on bug 428030. Does the gerrit build not run all fixtures? It runs the default fixtures. > If not we should run them manually when adding new versions. It's a chicken and egg problem. Unless you provision the new fixtures you can't run tests unless you provision everything locally first. Often it's more efficient to re-provision the server, let Hudson run tests and fix problems then and revert if it's a bigger deal.
I see. That makes sense.
*** Bug 430483 has been marked as a duplicate of this bug. ***
Thanks very much, Tim, for the contribution!