On 25-09-19 09:16, Andrea Aime wrote:
These errors keep on popping up, anyone has figured out what's going on?
The file system seems to be extremely unstable
for some reason, files not found, files that are not files.... maybe
Amazon is pulling the node away from the fleet and it starts by
unloading the file system?
Perhaps the workspace cleanup that Jenkins does in another job causes this?
I noticed that the job is doing:
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
[WS-CLEANUP] Done
While the Jenkins plugin docs say:
== Disable deferred wipeout method ==
In particular deployment (e.g. cloud) it might be useful to be sure
deferred wipeout is never selected as a cleanup method. Therefore there
is a new feature introduced to do this, implemented via regular
NodeProperty which you can attach to any node via UI or via script like:
https://plugins.jenkins.io/ws-cleanup
Also I never ever use /tmp for storing anything I need to hang on to for
more than a little while there are unix variants that have a /tmp
cleanup running at midnight or after resuming from "sleep", so perhaps
something like that? the builds are running from /tmp/jenkins-xxxxxx.../
-M
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
