[
https://issues.apache.org/jira/browse/SLIDER-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086123#comment-15086123
]
ASF subversion and git services commented on SLIDER-1039:
---------------------------------------------------------
Commit 0992e85500239d88f77cbd76f142b1daf02d5219 in incubator-slider's branch
refs/heads/develop from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=0992e85 ]
Merge branch 'develop' of
https://git-wip-us.apache.org/repos/asf/incubator-slider into develop
* 'develop' of https://git-wip-us.apache.org/repos/asf/incubator-slider:
SLIDER-1042 Use the correct cluster name when fetching the description
SLIDER-1041 Fix consistency for exports, enumerate all exports on HTML index.
SLIDER-1040 Better formatting on the AM's web ui.
SLIDER-1012 Modify server and quicklinks for Tomcat (fengyongshe)
SLIDER-809 First implementation of an Apache Tomcat app-package
SLIDER-1039 Run python tests from target directory
> Run slider-agent (py)tests from target directory not src directory
> ------------------------------------------------------------------
>
> Key: SLIDER-1039
> URL: https://issues.apache.org/jira/browse/SLIDER-1039
> Project: Slider
> Issue Type: Improvement
> Components: build
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: Slider 0.91
>
>
> I had to -1 the slider-0.90.2-incubating RC0 build because I saw a bunch of
> pyc files in the source archive.
> Upon investigation on how these got there, it seems like the pytests that we
> run for the slider-agent module are invoked inside the src/ directory.
> We should really follow the same approach that is done for the Java files:
> * Compilation from src into target (just a copy for python)
> * Invocation of tests from inside target
> This should net us two things:
> * A build does not dirty the workspace (lots of ways this is good)
> * We can remove the {{*.pyc}} entry from {{.gitignore}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
