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

Hoss Man commented on SOLR-3268:
--------------------------------

i think you're talking about SOLR-3112 which was dealt with .. but even if 
there are others, we can start by adding this check now, and then file issues 
to fix & remove whatever is left.

this isn't a silver bullet, it's certainly not as good as actually looking down 
src to fail on writes, but it will at least force people to be aware if/when 
they add a test that pollutes src/
                
> remove write acess to source tree (chmod 555) when running tests in jenkins
> ---------------------------------------------------------------------------
>
>                 Key: SOLR-3268
>                 URL: https://issues.apache.org/jira/browse/SOLR-3268
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>             Fix For: 4.0
>
>         Attachments: SOLR-3268_sync.patch
>
>
> Some tests are currently creating files under the source tree.
> This causes a lot of problems, it makes my checkout look dirty after running 
> 'ant test' and i have to cleanup.
> I opened and issue for this a month in a half for 
> solrj/src/test-files/solrj/solr/shared/test-solr.xml (SOLR-3112), 
> but now we have a second file 
> (core/src/test-files/solr/conf/elevate-data-distrib.xml).
> So I think hudson needs to chmod these src directories to 555, so that solr 
> tests that do this will fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to