[
https://issues.apache.org/jira/browse/MAHOUT-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729302#comment-13729302
]
Stevo Slavic commented on MAHOUT-1302:
--------------------------------------
Looking at standard error output at
https://builds.apache.org/job/Mahout-Quality/2184/testReport/org.apache.mahout.text/SequenceFilesFromMailArchivesTest/testSequential/
I'm no longer sure my initial analysis is entirely correct. There is something
environment specific going on.
But, according to log for a failed execution like one above, processing order
is same as for successful test run e.g. on my dev env:
{noformat}
Aug 05, 2013 12:48:21 AM org.slf4j.impl.JCLLoggerAdapter info
INFO: Command line arguments: {--body=null, --bodySeparator=[
], --charset=[UTF-8], --chunkSize=[64], --endPhase=[2147483647],
--input=[/home/sslavic/svn/mahout/mahout/integration/target/test-data/mahout-SequenceFilesFromMailArchivesTest-8799937166382529536/mail-archives-in],
--keyPrefix=[TEST], --method=[sequential],
--output=[/home/sslavic/svn/mahout/mahout/integration/target/test-data/mahout-SequenceFilesFromMailArchivesTest-8799937166382529536/mail-archives-out],
--separator=[], --startPhase=[0], --subject=null, --tempDir=[temp]}
Aug 05, 2013 12:48:22 AM org.apache.hadoop.util.NativeCodeLoader <clinit>
WARNING: Unable to load native-hadoop library for your platform... using
builtin-java classes where applicable
Aug 05, 2013 12:48:22 AM org.slf4j.impl.JCLLoggerAdapter info
INFO: At
/home/sslavic/svn/mahout/mahout/integration/target/test-data/mahout-SequenceFilesFromMailArchivesTest-8799937166382529536/mail-archives-in/subdir
Aug 05, 2013 12:48:22 AM org.slf4j.impl.JCLLoggerAdapter info
INFO: At
/home/sslavic/svn/mahout/mahout/integration/target/test-data/mahout-SequenceFilesFromMailArchivesTest-8799937166382529536/mail-archives-in/subdir/subsubdir
Aug 05, 2013 12:48:22 AM org.slf4j.impl.JCLLoggerAdapter info
INFO: Parsed 2 messages from directory
/home/sslavic/svn/mahout/mahout/integration/target/test-data/mahout-SequenceFilesFromMailArchivesTest-8799937166382529536/mail-archives-in/subdir/subsubdir
Aug 05, 2013 12:48:22 AM org.slf4j.impl.JCLLoggerAdapter info
INFO: Parsed 4 messages from directory
/home/sslavic/svn/mahout/mahout/integration/target/test-data/mahout-SequenceFilesFromMailArchivesTest-8799937166382529536/mail-archives-in/subdir
Aug 05, 2013 12:48:22 AM org.slf4j.impl.JCLLoggerAdapter info
INFO: Parsed 4 messages from
/home/sslavic/svn/mahout/mahout/integration/target/test-data/mahout-SequenceFilesFromMailArchivesTest-8799937166382529536/mail-archives-in
Aug 05, 2013 12:48:22 AM org.slf4j.impl.JCLLoggerAdapter info
INFO: Conversion took 465ms
{noformat}
Still seems like environment specific issue. Guessing maybe hdfs config is
different, or local FS, or JVM vendor/version.
> SequenceFilesFromMailArchivesTest.testSequential failing
> --------------------------------------------------------
>
> Key: MAHOUT-1302
> URL: https://issues.apache.org/jira/browse/MAHOUT-1302
> Project: Mahout
> Issue Type: Bug
> Components: Integration
> Affects Versions: 0.8
> Environment: ubuntu-3 and ubuntu-6 Apache Jenkins nodes
> Reporter: Stevo Slavic
> Assignee: Suneel Marthi
> Priority: Minor
> Labels: test
> Fix For: 0.9
>
>
> SequenceFilesFromMailArchivesTest.testSequential is failing only on ubuntu3
> and ubuntu6 Jenkins nodes. Because of that, MahoutQuality and integration job
> builds either fail or are successful depending on where they get run.
> Test fails because it expects entries in chunk-0 SequenceFile to be in
> specific order, but that order is not guaranteed because of the way the
> chunk-0 is created/filled - SequenceFilesFromMailArchives traverses input
> using Java's
> File[] java.io.File.listFiles(FileFilter filter)
> which does not guarantee order of files/directories.
> Unless we want in SequenceFileIterator to guarantee order by sorting, test
> needs to be changed to verify presence of given files and their content, but
> not their exact order.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
