[jira] [Commented] (BIGTOP-638) fix package test yum package manifest to make yum service test pass

["Johnny Zhang (JIRA)" <ji...@apache.org>]

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

Johnny Zhang commented on BIGTOP-638:
-------------------------------------

I suggest move the <services> block moved from bigtop-tests/test-artifacts/package/src/main/resources/package_date.xml to yum/pakcage_data.xml, apt/package_data.xml and zypper/package_date.xml

since different platform family has different runlevel and oninstall status, putting <services> block in a common place will fail tests on certain platforms. take flume-node runlevel as example, it will pass in Debian, whose runlevel is 2,3,4,5, but will fail in yum, which is 3,4,5. The same apply to <oninstall>
                
> fix package test yum package manifest to make yum service test pass
> -------------------------------------------------------------------
>
>                 Key: BIGTOP-638
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-638
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 0.4.0
>            Reporter: Johnny Zhang
>            Assignee: Johnny Zhang
>             Fix For: 0.4.0
>
>
> run TestPackagesPseudoDistributed in yum platform (like centos5_64), get several service test failures, due to manifest is incorrect, for example
> {noformat}
> testPackageServices[flume-node](org.apache.bigtop.itest.packagesmoke.TestPackagesPseudoDistributed)  Time elapsed: 12.487 sec  <<< FAILURE!
> java.lang.AssertionError: wrong list of runlevels for service flume-node
> Expected: <[3=3, 2=2, 5=5, 4=4, ]>
>      got: <{3=3, 4=4, 5=5}>
> {noformat}

--
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