[postgis-devel] Debbie is mad at me, why?

[Nicklas Avén]

My fix for #2431 r11807 seems to harm Debbie.

It is PostgreSQL 9.0 and PostGIS 2.1 that errors

I have some difficulties to get to the bottom of the problem with Debbie
but i think that she is yelling something like:

Started by upstream project "PostGIS_Regress" build number 2475
Building in workspace /var/lib/jenkins/workspace/pg
[pg] $ /bin/bash /tmp/hudson1248418341796386426.sh
FATAL: command execution failed
java.io.IOException: Cannot run program "/bin/bash" (in directory
"/var/lib/jenkins/workspace/pg"): java.io.IOException: error=12, Cannot
allocate memory
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
	at hudson.Proc$LocalProc.<init>(Proc.java:244)
	at hudson.Proc$LocalProc.<init>(Proc.java:216)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:709)
	at hudson.Launcher$ProcStarter.start(Launcher.java:338)
	at hudson.Launcher$ProcStarter.join(Launcher.java:345)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild
$AbstractBuildExecution.perform(AbstractBuild.java:717)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
	at hudson.model.AbstractBuild
$AbstractBuildExecution.run(AbstractBuild.java:499)
	at hudson.model.Run.execute(Run.java:1502)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Caused by: java.io.IOException: java.io.IOException: error=12, Cannot
allocate memory
	at java.lang.UNIXProcess.<init>(UNIXProcess.java:164)
	at java.lang.ProcessImpl.start(ProcessImpl.java:81)
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:468)
	... 16 more
Build step 'Execute shell' marked build as failure
Finished: FAILURE




Is it a real problem with the code or is it some server-related problem?

Thanks

Nicklas