Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1569

[Apache Jenkins Server]

See 


-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] Replacing the automatic Jenkins jobs with Apache Yetus qbt

[Allen Wittenauer]

> On May 31, 2016, at 8:53 PM, Andrew Wang  wrote:
> 
> I'm in favor of something that helps unify the current mess of Jenkins
> jobs. We do something similar for our internal Hadoop repo: each branch has
> a "build.sh" and "test.sh" script that builds and then runs the tests. This
> predates Yetus, else we'd probably have used that. So +1 from me.
> 
> One thing I also find really helpful is riding over flaky tests, perhaps
> via:
> 
> http://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html
> 
> This would be great for precommit too, since right now someone has to run
> the failed tests locally to confirm they're flakes.
> 
> Even better is then feeding the success/failure into a DB so you can track
> flaky rates over time, which helps you prioritize which flaky to fix first,
> and helps you find the change which caused the flakiness.


Appy over in HBase-land has added flaky detection and the ability to 
track and ignore them to their Yetus personality.  At some point, I’m sure 
we’ll see that code float upstream in a more generalized manner as they get 
more experience with it. 
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] Replacing the automatic Jenkins jobs with Apache Yetus qbt

[Chris Nauroth]

Hi Allen,

+1 overall for the proposal.  Thank you for doing this.

A few minor notes on the content of the report:

It looks like Failed junit tests removes the "org.apache" prefix, but
Timed out junit tests does not.  If possible, it would be nice for this to
be consistent.

The naming of log files with "patch" might potentially be a source of
confusion, because this is running against the current source tree, and
there is no additional patch in play.

Since the log file paths are long, it can be hard to pick out exactly the
one you want.  I realize that we won't be able to re-create the nice HTML
tabular formatting, but is it possible to put a short name before each
link so that it's easier to scan the list?

--Chris Nauroth




On 5/31/16, 11:12 AM, "Allen Wittenauer"  wrote:

>
>Hey gang.
>
>   I¹ve been thinking a lot over the past few months about the various
>Jenkins jobs that we have that run after a commit.  Their job is to tell
>us when a commit break a unit test. They eat up an incredible amount of
>time on the build infrastructure and I¹m not really sure if they provide
>much value in their current form. I suspect most of us pretty much ignore
>those emails, however, for a variety of reasons:
>
>a) There are simply too many of them.
>b) The content of the email is hard to quickly parse/read to get useful
>information.
>c) The unit tests are almost always broken.
>
>   Worse yet: these jobs don¹t actually test everything (all of
>hadoop-tools is missing!) and skip out on some vital information.
>
>   With Apache Yetus 0.3.0, we added a mode called Œqbt¹ aka Quality Build
>Tool.  It effectively run Apache Yetus over the entire source tree and
>generates the columnar output similar to what you would see during
>precommit.  I¹ve been running this mode against Apache Hadoop on Jenkins
>for a few months now, working out the kinks, etc, and it was working well
>except for one thingŠ the generated report was still not great over email:
>
>1) Couldn¹t use HTML since the ASF mailing lists reject HTML-formatted
>mail
>2) Mail clients that used proportional fonts were still a big mess
>
>   For 0.4.0, I¹m working on a feature that adds a Œbrief¹ mode  [
>YETUS-390 ] with the (long term?) intention of replacing all of these
>emails that get generated by Jenkins.  I¹d like to hear some feedback on
>if a) I¹m just spinning my wheels and no one is actually interested in
>fixing this problem and b) the replacement email generated either needs
>more info or less info.
>
>   Here¹s the currently generated email.  Note that some subsystems have
>been told not to fail the build due to warnings (e.g., cc, javac,
>javadoc, shellcheck, whitespace, etc) but still generate a log of
>problems so that they may be investigated and used for cleanup.
>
>   Thanks!
>
> cut here =
>For more details, see https://builds.apache.org/job/hadoop-qbt/39/
>
>[Jun 1, 2016 12:41:15 AM] (kai.zheng) Revert "HADOOP-12579. Deprecate and
>remove WriteableRPCEngine.
>
>
>
>
>-1 overall
>
>
>The following subsystems reported failures:
>   findbugs unit
>
>
>The following subsystems are considered long running:
>   unit
>
>
>   FindBugs :
>
>  module:hadoop-common-project/hadoop-minikdc
>  org.apache.hadoop.minikdc.MiniKdc.stop() calls Thread.sleep() with
>a lock held At MiniKdc.java:lock held At MiniKdc.java:[line 345]
>
>   Failed junit tests :
>
>  hadoop.net.TestClusterTopology
>  hadoop.yarn.server.resourcemanager.TestAMAuthorization
>  hadoop.yarn.server.resourcemanager.TestClientRMTokens
>  hadoop.yarn.server.TestMiniYarnClusterNodeUtilization
>  hadoop.yarn.server.TestContainerManagerSecurity
>  hadoop.yarn.client.TestGetGroups
>  hadoop.yarn.client.api.impl.TestDistributedScheduling
>  hadoop.yarn.client.api.impl.TestAMRMProxy
>  hadoop.mapreduce.tools.TestCLI
>  hadoop.mapred.TestMiniMRChildTask
>
>   Timed out junit tests :
>
>  org.apache.hadoop.yarn.client.cli.TestYarnCLI
>  org.apache.hadoop.yarn.client.api.impl.TestAMRMClient
>  org.apache.hadoop.yarn.client.api.impl.TestYarnClient
>  org.apache.hadoop.yarn.client.api.impl.TestNMClient
>
>Console output: 
>   https://builds.apache.org/job/hadoop-qbt/39/console
>
>Logs:
>
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/diff-compile-cc-r
>oot.txt 
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/diff-compile-java
>c-root.txt 
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/diff-checkstyle-r
>oot.txt 
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/diff-patch-pylint
>.txt 
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/diff-patch-shellc
>heck.txt 
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/diff-patch-shelld
>ocs.txt 
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/whitespace-eol.tx
>t 
>
>https://builds.apache.org/job/hadoop-qbt/39/artifact/out/whitespace-tabs.t
>xt 
>

Re: [DISCUSS] Replacing the automatic Jenkins jobs with Apache Yetus qbt

[Allen Wittenauer]

> On Jun 1, 2016, at 10:51 AM, Chris Nauroth  wrote:
> It looks like Failed junit tests removes the "org.apache" prefix, but
> Timed out junit tests does not.  If possible, it would be nice for this to
> be consistent.

Ha. It's been that way in Yetus for a very, very long time.  I've 
opened YETUS-411 to track that.

> The naming of log files with "patch" might potentially be a source of
> confusion, because this is running against the current source tree, and
> there is no additional patch in play.

I've opened YETUS-412 to cover this one.  That's a _big_ change.


> Since the log file paths are long, it can be hard to pick out exactly the
> one you want.  I realize that we won't be able to re-create the nice HTML
> tabular formatting, but is it possible to put a short name before each
> link so that it's easier to scan the list?

I'll see what I can do, but no guarantees.

It should be noted that the report posted here had a bug, so the links 
were wrong. haha.  That has since been fixed.

Thanks for the feedback!
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] Replacing the automatic Jenkins jobs with Apache Yetus qbt

[Chris Nauroth]

Thanks again, Allen.

Just to make sure it's clear, I consider all of my feedback quite minor.
If something big can't get done right away, like changing "patch" in the
file names, then I wouldn't want it to block proceeding with rearranging
our Jenkins jobs.

--Chris Nauroth




On 6/1/16, 11:18 AM, "Allen Wittenauer"  wrote:

>
>> On Jun 1, 2016, at 10:51 AM, Chris Nauroth 
>>wrote:
>> It looks like Failed junit tests removes the "org.apache" prefix, but
>> Timed out junit tests does not.  If possible, it would be nice for this
>>to
>> be consistent.
>
>   Ha. It's been that way in Yetus for a very, very long time.  I've opened
>YETUS-411 to track that.
>
>> The naming of log files with "patch" might potentially be a source of
>> confusion, because this is running against the current source tree, and
>> there is no additional patch in play.
>
>   I've opened YETUS-412 to cover this one.  That's a _big_ change.
>
>
>> Since the log file paths are long, it can be hard to pick out exactly
>>the
>> one you want.  I realize that we won't be able to re-create the nice
>>HTML
>> tabular formatting, but is it possible to put a short name before each
>> link so that it's easier to scan the list?
>
>   I'll see what I can do, but no guarantees.
>
>   It should be noted that the report posted here had a bug, so the links
>were wrong. haha.  That has since been fixed.
>
>Thanks for the feedback!


-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-13230) s3a's use of fake empty directory blobs does not interoperate with other s3 tools

[Aaron Fabbri (JIRA)]

Aaron Fabbri created HADOOP-13230:
-

 Summary: s3a's use of fake empty directory blobs does not 
interoperate with other s3 tools
 Key: HADOOP-13230
 URL: https://issues.apache.org/jira/browse/HADOOP-13230
 Project: Hadoop Common
  Issue Type: Bug
  Components: fs/s3
Affects Versions: 2.9.0
Reporter: Aaron Fabbri


Users of s3a may not realize that, in some cases, it does not interoperate well 
with other s3 tools, such as the AWS CLI.  (See HIVE-13778, IMPALA-3558).

Specifically, if a user:

- Creates an empty directory with hadoop fs -mkdir s3a://bucket/path
- Copies data into that directory via another tool, i.e. aws cli.
- Tries to access the data in that directory with any Hadoop software.

Then the last step fails because the fake empty directory blob that s3a wrote 
in the first step, causes s3a (listStatus() etc.) to continue to treat that 
directory as empty, even though the second step was supposed to populate the 
directory with data.

I wanted to document this fact for users. We may mark this as not-fix, "by 
design".. May also be interesting to brainstorm solutions and/or a config 
option to change the behavior if folks care.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1570

[Apache Jenkins Server]

See 

Changes:

[wang] HADOOP-13228. Add delegation token to the connection in

[xgong] YARN-5088. Improve "yarn log" command-line to read the last K bytes for

--
[...truncated 5350 lines...]
Running org.apache.hadoop.cli.TestCLI
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.609 sec - in 
org.apache.hadoop.metrics2.lib.TestMutableMetrics
Running org.apache.hadoop.io.TestSortedMapWritable
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.218 sec - in 
org.apache.hadoop.net.TestStaticMapping
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.471 sec - in 
org.apache.hadoop.io.TestSortedMapWritable
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.504 sec - in 
org.apache.hadoop.cli.TestCLI
Running org.apache.hadoop.io.TestIOUtils
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.249 sec - in 
org.apache.hadoop.net.unix.TestDomainSocket
Running org.apache.hadoop.io.TestSequenceFile
Running org.apache.hadoop.io.TestEnumSetWritable
Running org.apache.hadoop.io.TestWritableName
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.966 sec - in 
org.apache.hadoop.io.TestIOUtils
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.576 sec - in 
org.apache.hadoop.io.TestWritableName
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.021 sec - in 
org.apache.hadoop.io.TestEnumSetWritable
Running org.apache.hadoop.io.TestBoundedByteArrayOutputStream
Running org.apache.hadoop.io.TestSequenceFileAppend
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.17 sec - in 
org.apache.hadoop.io.TestBoundedByteArrayOutputStream
Running org.apache.hadoop.io.TestBytesWritable
Running org.apache.hadoop.io.TestSequenceFileSerialization
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.366 sec - in 
org.apache.hadoop.io.TestBytesWritable
Running org.apache.hadoop.io.TestDataByteBuffers
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.565 sec - in 
org.apache.hadoop.io.TestSequenceFileAppend
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.56 sec - in 
org.apache.hadoop.io.TestDataByteBuffers
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.445 sec - in 
org.apache.hadoop.io.TestSequenceFileSerialization
Running org.apache.hadoop.io.file.tfile.TestTFileComparators
Running org.apache.hadoop.io.file.tfile.TestTFileSeek
Running org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsByteArrays
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.931 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsByteArrays
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.789 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileComparators
Running org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsStreams
Running org.apache.hadoop.io.file.tfile.TestTFileUnsortedByteArrays
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.262 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsStreams
Running org.apache.hadoop.io.file.tfile.TestTFileStreams
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.15 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileUnsortedByteArrays
Running org.apache.hadoop.io.file.tfile.TestTFile
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.105 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileSeek
Running 
org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsJClassComparatorByteArrays
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.612 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileStreams
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.312 sec - in 
org.apache.hadoop.io.file.tfile.TestTFile
Running org.apache.hadoop.io.file.tfile.TestTFileJClassComparatorByteArrays
Running org.apache.hadoop.io.file.tfile.TestCompression
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.115 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsJClassComparatorByteArrays
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.897 sec - in 
org.apache.hadoop.io.file.tfile.TestCompression
Running org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsStreams
Running org.apache.hadoop.io.file.tfile.TestTFileSplit
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.747 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsStreams
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.815 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileJClassComparatorByteArrays
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.169 sec - in 
org.apache.hadoop.io.TestSequenceFile
Running org.apache.hadoop.io.file.tfile.TestTFileComparator2
Running org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsByteArrays
Running org.apache.hadoop.io.file.tfile.Test

[jira] [Created] (HADOOP-13231) Isolate test path used by a few S3A tests for more reliable parallel execution.

[Chris Nauroth (JIRA)]

Chris Nauroth created HADOOP-13231:
--

 Summary: Isolate test path used by a few S3A tests for more 
reliable parallel execution.
 Key: HADOOP-13231
 URL: https://issues.apache.org/jira/browse/HADOOP-13231
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: fs/s3, test
Reporter: Chris Nauroth
Assignee: Chris Nauroth
Priority: Minor


I have noticed a few more spots in S3A tests that do not make use of the 
isolated test directory path when running in parallel mode.  While I don't have 
any evidence that this is really causing problems for parallel test runs right 
now, it would still be good practice to clean these up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1571

[Apache Jenkins Server]

See 

Changes:

[cnauroth] HADOOP-13131. Add tests to verify that S3A supports SSE-S3 
encryption.

--
[...truncated 5354 lines...]
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.537 sec - in 
org.apache.hadoop.metrics2.lib.TestMutableMetrics
Running org.apache.hadoop.cli.TestCLI
Running org.apache.hadoop.io.TestSortedMapWritable
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.29 sec - in 
org.apache.hadoop.io.TestSortedMapWritable
Running org.apache.hadoop.io.TestIOUtils
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.023 sec - in 
org.apache.hadoop.net.TestStaticMapping
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.929 sec - in 
org.apache.hadoop.cli.TestCLI
Running org.apache.hadoop.io.TestSequenceFile
Running org.apache.hadoop.io.TestEnumSetWritable
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec - in 
org.apache.hadoop.io.TestIOUtils
Running org.apache.hadoop.io.TestWritableName
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.622 sec - in 
org.apache.hadoop.io.TestEnumSetWritable
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.253 sec - in 
org.apache.hadoop.io.TestWritableName
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.154 sec - in 
org.apache.hadoop.net.unix.TestDomainSocket
Running org.apache.hadoop.io.TestBoundedByteArrayOutputStream
Running org.apache.hadoop.io.TestSequenceFileAppend
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.088 sec - in 
org.apache.hadoop.io.TestBoundedByteArrayOutputStream
Running org.apache.hadoop.io.TestBytesWritable
Running org.apache.hadoop.io.TestSequenceFileSerialization
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.282 sec - in 
org.apache.hadoop.io.TestBytesWritable
Running org.apache.hadoop.io.TestDataByteBuffers
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.452 sec - in 
org.apache.hadoop.io.TestSequenceFileAppend
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.477 sec - in 
org.apache.hadoop.io.TestDataByteBuffers
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.387 sec - in 
org.apache.hadoop.io.TestSequenceFileSerialization
Running org.apache.hadoop.io.file.tfile.TestTFileComparators
Running org.apache.hadoop.io.file.tfile.TestTFileSeek
Running org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsByteArrays
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.59 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsByteArrays
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.32 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileComparators
Running org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsStreams
Running org.apache.hadoop.io.file.tfile.TestTFileUnsortedByteArrays
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.459 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileLzoCodecsStreams
Running org.apache.hadoop.io.file.tfile.TestTFileStreams
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.996 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileUnsortedByteArrays
Running org.apache.hadoop.io.file.tfile.TestTFile
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.736 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileStreams
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.836 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileSeek
Running 
org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsJClassComparatorByteArrays
Running org.apache.hadoop.io.file.tfile.TestTFileJClassComparatorByteArrays
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.634 sec - in 
org.apache.hadoop.io.file.tfile.TestTFile
Running org.apache.hadoop.io.file.tfile.TestCompression
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.425 sec - in 
org.apache.hadoop.io.file.tfile.TestCompression
Running org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsStreams
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.567 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsJClassComparatorByteArrays
Running org.apache.hadoop.io.file.tfile.TestTFileSplit
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.8 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileJClassComparatorByteArrays
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.115 sec - in 
org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsStreams
Running org.apache.hadoop.io.file.tfile.TestTFileComparator2
Running org.apache.hadoop.io.file.tfile.TestTFileNoneCodecsByteArrays
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.874 sec - in 
org.apache.hadoop.io.TestSequenceFile
Running org.apache.hadoop.io.file.tfile.TestTFileByteArrays
Tests run: 1, Failures: 0, Errors: 0, Skipped: 

[jira] [Created] (HADOOP-13232) Typo in exception in ValueQueue.java

[Jiayi Zhou (JIRA)]

Jiayi Zhou created HADOOP-13232:
---

 Summary: Typo in exception in ValueQueue.java
 Key: HADOOP-13232
 URL: https://issues.apache.org/jira/browse/HADOOP-13232
 Project: Hadoop Common
  Issue Type: Bug
  Components: kms
Affects Versions: 3.0.0-alpha1
Reporter: Jiayi Zhou
Priority: Trivial


Typo in exception. Missing a 'c' in method getAtMost in ValueQueue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org