You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Daniel Takamori (JIRA)" <ji...@apache.org> on 2016/08/09 22:24:20 UTC

[jira] [Commented] (INFRA-12400) Unable to recreate a /tmp folder on Windows build agents

    [ https://issues.apache.org/jira/browse/INFRA-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414348#comment-15414348 ] 

Daniel Takamori commented on INFRA-12400:
-----------------------------------------

Can you create a folder named f:\tmp\mesos-tmp (or something similar) instead, that way you will be the only writers to the directory and won't have conflict in a system wide tmp folder.

> Unable to recreate a /tmp folder on Windows build agents
> --------------------------------------------------------
>
>                 Key: INFRA-12400
>                 URL: https://issues.apache.org/jira/browse/INFRA-12400
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: Jenkins agent(s): windows2012-1 
>            Reporter: Joseph Wu
>            Priority: Minor
>
> The Jenkins job for Mesos on Windows [1] will eventually need a /tmp folder on the same drive in order to run tests.  This folder holds test artifacts that are ordinarily cleaned up during tests.  However if tests fail (i.e. crash), as they inevitably will, some test artifacts will not be cleaned up.
> Before Build #346 [2] (Aug 9, 2016 6:03 AM), we would recreate the /tmp folder on each job run.  Permissions on the folder appear to have changed:
>   f:\jenkins\jenkins-slave\workspace\Mesos-Windows>RMDIR /q /s f:\tmp 
>   Access is denied.
>   f:\jenkins\jenkins-slave\workspace\Mesos-Windows>MKDIR f:\tmp 
>   A subdirectory or file f:\tmp already exists.
> If we do not clean up the /tmp folder, the agent may eventually run out of disk space.
> [1] https://builds.apache.org/job/Mesos-Windows/
> [2] https://builds.apache.org/job/Mesos-Windows/346/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)