Last modified: 2014-10-19 17:43:51 UTC
I'm not a 100% sure, but I see this on all contint slaves and suspect it comes from browser tests. If that's the case, please: 1) [required] Give it a more descriptive name to avoid clashing with other programs and to make it possible for others trace what it is. 2) [required] Collect garbage. Either put it in the workspace (auto-cleaned), or ensure its removal with a Jenkins "postbuildscript" publisher (similar to the qunit-cleanup macro). 3) [suggestion] If you want parallelism, be sure to either store it in the workspace (which is already unique for each concurrent job, e.g. project-lint@1 and project-lint@2), or embed a unique id in the file name to avoid race conditions, such as $BUILD_TAG (=$JOB_NAME-$BUILD_NUMBER).
As far as I know, this is not created by browser tests. (But I could be wrong.) I am adding more people to this bug that could know.