You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Binglin Chang (JIRA)" <ji...@apache.org> on 2012/10/15 22:33:04 UTC
[jira] [Created] (HDFS-4055) TestAuditLogs has some chances to
fail.
Binglin Chang created HDFS-4055:
-----------------------------------
Summary: TestAuditLogs has some chances to fail.
Key: HDFS-4055
URL: https://issues.apache.org/jira/browse/HDFS-4055
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Binglin Chang
{code}
InputStream istream = webfs.open(file);
int val = istream.read();
istream.close();
verifyAuditLogsRepeat(true, 3);
assertTrue("failed to read from file", val >= 0);
{code}
{code}
byte[] toWrite = new byte[bufferLen];
Random rb = new Random(seed);
long bytesToWrite = fileLen;
while (bytesToWrite>0) {
rb.nextBytes(toWrite);
{code}
InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Commented] (HDFS-4055) TestAuditLogs has some chances to
fail.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476518#comment-13476518 ]
Hadoop QA commented on HDFS-4055:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12549203/HDFS-4055-TestAuditLogs-bug.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.datanode.TestHSync
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3334//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3334//console
This message is automatically generated.
> TestAuditLogs has some chances to fail.
> ---------------------------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Commented] (HDFS-4055) TestAuditLogs is flaky
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477864#comment-13477864 ]
Hudson commented on HDFS-4055:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1228 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1228/])
HDFS-4055. TestAuditLogs is flaky. Contributed by Binglin Chang (Revision 1399093)
Result = FAILURE
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1399093
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestAuditLogs.java
> TestAuditLogs is flaky
> ----------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Fix For: 2.0.3-alpha
>
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Commented] (HDFS-4055) TestAuditLogs has some chances to
fail.
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476673#comment-13476673 ]
Eli Collins commented on HDFS-4055:
-----------------------------------
+1 the test failure is unrelated, I filed HDFS-4060 for it.
> TestAuditLogs has some chances to fail.
> ---------------------------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Updated] (HDFS-4055) TestAuditLogs has some chances to
fail.
Posted by "Binglin Chang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binglin Chang updated HDFS-4055:
--------------------------------
Attachment: HDFS-4055-TestAuditLogs-bug.patch
> TestAuditLogs has some chances to fail.
> ---------------------------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Commented] (HDFS-4055) TestAuditLogs is flaky
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477767#comment-13477767 ]
Hudson commented on HDFS-4055:
------------------------------
Integrated in Hadoop-Yarn-trunk #6 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/6/])
HDFS-4055. TestAuditLogs is flaky. Contributed by Binglin Chang (Revision 1399093)
Result = FAILURE
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1399093
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestAuditLogs.java
> TestAuditLogs is flaky
> ----------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Fix For: 2.0.3-alpha
>
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Updated] (HDFS-4055) TestAuditLogs is flaky
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HDFS-4055:
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.3-alpha
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I've committed this. Thanks Binglin!
> TestAuditLogs is flaky
> ----------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Fix For: 2.0.3-alpha
>
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Updated] (HDFS-4055) TestAuditLogs has some chances to
fail.
Posted by "Binglin Chang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binglin Chang updated HDFS-4055:
--------------------------------
Assignee: Binglin Chang
Status: Patch Available (was: Open)
> TestAuditLogs has some chances to fail.
> ---------------------------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Commented] (HDFS-4055) TestAuditLogs is flaky
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477836#comment-13477836 ]
Hudson commented on HDFS-4055:
------------------------------
Integrated in Hadoop-Hdfs-trunk #1198 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1198/])
HDFS-4055. TestAuditLogs is flaky. Contributed by Binglin Chang (Revision 1399093)
Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1399093
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestAuditLogs.java
> TestAuditLogs is flaky
> ----------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Fix For: 2.0.3-alpha
>
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Commented] (HDFS-4055) TestAuditLogs is flaky
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477596#comment-13477596 ]
Hudson commented on HDFS-4055:
------------------------------
Integrated in Hadoop-trunk-Commit #2879 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/2879/])
HDFS-4055. TestAuditLogs is flaky. Contributed by Binglin Chang (Revision 1399093)
Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1399093
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestAuditLogs.java
> TestAuditLogs is flaky
> ----------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Fix For: 2.0.3-alpha
>
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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
[jira] [Updated] (HDFS-4055) TestAuditLogs is flaky
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HDFS-4055:
------------------------------
Summary: TestAuditLogs is flaky (was: TestAuditLogs has some chances to fail.)
> TestAuditLogs is flaky
> ----------------------
>
> Key: HDFS-4055
> URL: https://issues.apache.org/jira/browse/HDFS-4055
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Binglin Chang
> Assignee: Binglin Chang
> Attachments: HDFS-4055-TestAuditLogs-bug.patch
>
>
> {code}
> InputStream istream = webfs.open(file);
> int val = istream.read();
> istream.close();
> verifyAuditLogsRepeat(true, 3);
> assertTrue("failed to read from file", val >= 0);
> {code}
> {code}
> byte[] toWrite = new byte[bufferLen];
> Random rb = new Random(seed);
> long bytesToWrite = fileLen;
> while (bytesToWrite>0) {
> rb.nextBytes(toWrite);
> {code}
> InputStream.read() return the first byte of the file, the bytes in the file is generated in using Random.nextBytes(), so you get 1/256 chance the first byte is 0, so some times it may fail.
--
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