[
https://issues.apache.org/jira/browse/PHOENIX-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109323#comment-15109323
]
Samarth Jain commented on PHOENIX-2612:
---------------------------------------
Other than the java doc warning, the zombie test failure reported is really
weird. Looking at the console output, it looks like the stuck test is a
non-phoenix test -
org.apache.ambari.server.state.alerts.AlertReceivedListenerTest.setup(AlertReceivedListenerTest.java:73).
I do see that the build machine H5 (https://builds.apache.org/computer/H5/) is
also running the ambari test suite. So looks like there is some kind of overlap
happening here. I notice that the H5 machine has also been listed as running
tests for Falcon, Hadoop, Hdfs, Mapreduce, Pig, Tez and Zookeeper. An easier
thing to try would be is to run our QA test runs on a different machine.
[~mujtabachohan] - would you happen to know how to have our patch QA test runs
run on a different build machine?
> Pherf - RuleGeneartor test in phoenix-pherf passes and fails in different
> environments.
> -----------------------------------------------------------------------------------------
>
> Key: PHOENIX-2612
> URL: https://issues.apache.org/jira/browse/PHOENIX-2612
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.6.0
> Reporter: Karan Singhal
> Assignee: Karan Singhal
> Labels: Performance
> Fix For: 4.6.0, 4.7.0
>
> Attachments: PHOENIX-2612.patch
>
>
> This is happening because regex used in test for searching path of
> test-scenario.xml is not specific. The pattern being used is
> *scenario.*scenario.*.xml due to which pattern matcher finds all the
> different xmls in the package. After that all the xml's are parsed if
> pattern matcher finds test-scenario.xml in path first then test-scenario.xml
> is parsed first and test passes because test is always reading datamodel at
> index 0 (hard coded in test) from list of datamodels and if any other xml is
> parsed first it fails because it did not get right datamodel.
> Solution is simple just make matcher scenario in test to be more specific so
> that every time test-scenario.xml is picked up. After looking at some other
> tests I found .*test_scenario.xml is used in lot of other tests which is the
> most appropriate for searching test_sceanario.xml and can be used for this
> test too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
