You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2015/02/10 19:09:12 UTC
[jira] [Created] (LUCENE-6235) smokeTestRelease.py's regex for
TestBackwardsCompatibility is brittle, breaks if user uses ant's ANT_ARGS
Hoss Man created LUCENE-6235:
--------------------------------
Summary: smokeTestRelease.py's regex for TestBackwardsCompatibility is brittle, breaks if user uses ant's ANT_ARGS
Key: LUCENE-6235
URL: https://issues.apache.org/jira/browse/LUCENE-6235
Project: Lucene - Core
Issue Type: Bug
Reporter: Hoss Man
smokeTestRelease.py has always exec'ed "ant" on source releases to smoke check the build - but the changes intorduced in LUCENE-5863 also do a regex over the output of the ant call to run TestBackwardsCompatibility.
This regex doesn't play nicely however if the user has ANT_ARGS configured to use an alternative logger - in particular i (and i'm guessing i'm not alone among the general ant using populace) have this in my shell...
{noformat}
$ env | grep ANT
ANT_HOME=/opt/ant/default/
ANT_ARGS=-logger org.apache.tools.ant.listener.AnsiColorLogger
{noformat}
The AnsiColorLogger, and the control characters it outputs to color the output lines, seems to break the regex matching for TestBackwardsCompatibility's output.
Workarround (seems to be - still testing) for smoke testers to force their environment to specify the DefaultLogger...
{noformat}
$ ANT_ARGS='-logger org.apache.tools.ant.DefaultLogger' python3.2 dev-tools/scripts/smokeTestRelease.py http://people.apache.org/~anshum/staging_area/lucene-solr-5.0.0-RC2-rev1658469
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org