Hmmm ... 5.x nightly failed again ... this time it was DistributedMLTComponentTest ... this test doesn't have anything to do with the SocketProxy and partitions of the usual suspects ... passes locally so the failure seems transient?
ant test -Dtestcase=DistributedMLTComponentTest -Dtests.method=test -Dtests.seed=18D4ED128EC399FC -Dtests.multiplier=2 -Dtests.nightly=true -Dtests.slow=true -Dtests.linedocsfile=/home/jenkins/lucene-data/enwiki.random.lines.txt -Dtests.locale=uk_UA -Dtests.timezone=Etc/GMT-2 -Dtests.asserts=true -Dtests.file.encoding=US-ASCII So do I do another RC or should we wait until we have a passing build for 5.1 on Jenkins? On Wed, Apr 8, 2015 at 11:00 AM, Mark Miller <[email protected]> wrote: > To clarify, two JIRA issues, but one commit. As to why the bug became > consistent on 5x, it seems other changes that were backported made this > issue much more prominent. Normally, you might say, well a bug fix didn't > make the release, it has not come back from 6x to 5x yet, but in this case, > other changes exasperated that bug and these nightly fails were not picked > up on (probably because there are so many non nightly fails consistently - > another problem altogether). > > - Mark > > On Wed, Apr 8, 2015 at 12:45 PM Mark Miller <[email protected]> wrote: >> >> Those JIRA issues were still open - sometimes you put them in trunk for a >> while and if all goes well you back port them a while later. I just have >> been busy and lost track of them from last month to now. >> >> >> - Mark >> >> On Wed, Apr 8, 2015 at 12:03 PM Michael McCandless >> <[email protected]> wrote: >>> >>> On Wed, Apr 8, 2015 at 11:50 AM, Mark Miller <[email protected]> >>> wrote: >>> > I've resolved the hdfs failures on 5.1. There were two bug JIRA's that >>> > were >>> > in 6x but not yet 5x or 5.1. >>> >>> Hmm how/why did this happen? When we fix bugs on trunk we should >>> always backport to 5.x, in general? Is there something we can learn >>> here...? >>> >>> Mike McCandless >>> >>> http://blog.mikemccandless.com >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
