cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-6414) BlacklistingCompactionsTest fails in trunk
Date Thu, 16 Jan 2014 09:27:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872558#comment-13872558
] 

Michael Shuler edited comment on CASSANDRA-6414 at 1/16/14 9:26 AM:
--------------------------------------------------------------------

Multiple git bisections for purely BUILD SUCCESSFUL / FAILED arrive at the above commit as
the first bad commit.  When I am on commit f3dc188 and revert it (ending up on 6164a83), 'ant
clean jar && ant test -Dtest.name=BlacklistingCompactionsTest' gives me BUILD SUCCESSFUL.
 Reverting f3dc188 from current trunk also fixes this test for me.

That said, I *do* have tons of traceback output, even when successful at that point.  I'm
going to see if there is a common initial trace message (maybe "org.apache.cassandra.io.sstable.CorruptSSTableException:
java.io.EOFException") and see if I can find where those are starting.

git bisect run script:
{code}
#!/bin/bash
ant realclean
ant jar || exit 125
for i in {1..3}; do
  ant test -Dtest.name=BlacklistingCompactionsTest
  RET=$?
  if [ "$RET" -eq "0" ]; then
    break
  fi
done
exit $RET
{code}

consistently arrives at:

{noformat}
# bad: [63c490af9cbe392ba025f15854173eb4f7fbbfad] encapsulate SecondaryIndex.estimateResultRows
patch by Miguel Angel Fernandez Diaz; reviewed by Sam Tunnicliffe for CASSANDRA-6498
# good: [7514e61b48e9456cf6591abaf6dbf17b52217883] update changes
git bisect start 'trunk' 'cassandra-2.0'
# good: [6c379343561766724e48d1d7cf98e282e8ec91dd] Merge branch 'cassandra-2.0' into trunk
git bisect good 6c379343561766724e48d1d7cf98e282e8ec91dd
# skip: [a13c6dcbb7a6ba74b27e50eef4bfd0f80eaea121] Merge branch 'cassandra-2.0' into trunk
git bisect skip a13c6dcbb7a6ba74b27e50eef4bfd0f80eaea121
# bad: [351d49b06bd6887447eecb149b3cdf1697ab41ac] validate directory permissions on startup
Patch by Lyuben Todorov and Koray Sariteke; reviewed by Mikhail Stepura for CASSANDRA-5818
git bisect bad 351d49b06bd6887447eecb149b3cdf1697ab41ac
# good: [5c21711e76731a6f48d67ca956ea865fda4574b4] merge from 2.0
git bisect good 5c21711e76731a6f48d67ca956ea865fda4574b4
# good: [52cc7efb2bcd47285148da85c089d796cb20734a] Merge branch 'cassandra-2.0' into trunk
git bisect good 52cc7efb2bcd47285148da85c089d796cb20734a
# good: [40598efa6344333d4d4deee2c1ec3e71bd931066] Merge branch 'cassandra-2.0' into trunk
git bisect good 40598efa6344333d4d4deee2c1ec3e71bd931066
# skip: [1bfd062fdc9daa35fbabcebb3ac31e726504f1ff] Merge branch 'cassandra-2.0' into trunk
git bisect skip 1bfd062fdc9daa35fbabcebb3ac31e726504f1ff
# bad: [7ea5b40b7172ec9f3fdecca533e19d8a165de7df] don't leave replaced SSTRs around to break
other tests patch by Tyler Hobbs
git bisect bad 7ea5b40b7172ec9f3fdecca533e19d8a165de7df
# bad: [9f3a7f8a698aaaa9be44bed01aaf526567df8aca] simple naming fixes
git bisect bad 9f3a7f8a698aaaa9be44bed01aaf526567df8aca
# bad: [8732fe938659232b3f0c63933b125131fa50fd2e] Merge branch 'cassandra-2.0' into trunk
git bisect bad 8732fe938659232b3f0c63933b125131fa50fd2e
# good: [87b39c8af3477c3b80f124da23b46de350a259e7] Merge branch 'cassandra-2.0' into trunk
git bisect good 87b39c8af3477c3b80f124da23b46de350a259e7
# good: [a10150542c662a4cc69ce1b88f48636d1e6884f7] merge from 2.0
git bisect good a10150542c662a4cc69ce1b88f48636d1e6884f7
# bad: [f3dc188e203b3db980ee81df05390968043cb601] move setting lastCompactedKey to before
the return-if-nothing-added
git bisect bad f3dc188e203b3db980ee81df05390968043cb601
{noformat}


was (Author: mshuler):
Multiple git bisections for purely BUILD SUCCESSFUL / FAILED arrive at the above commit as
the first bad commit.  When I am on commit f3dc188 and revert it (ending up on 6164a83), 'ant
clean jar && ant test -Dtest.name=BlacklistingCompactionsTest' gives me BUILD SUCCESSFUL.

That said, I *do* have tons of traceback output, even when successful at that point.  I'm
going to see if there is a common initial trace message (maybe "org.apache.cassandra.io.sstable.CorruptSSTableException:
java.io.EOFException") and see if I can find where those are starting.

git bisect run script:
{code}
#!/bin/bash
ant realclean
ant jar || exit 125
for i in {1..3}; do
  ant test -Dtest.name=BlacklistingCompactionsTest
  RET=$?
  if [ "$RET" -eq "0" ]; then
    break
  fi
done
exit $RET
{code}

consistently arrives at:

{noformat}
# bad: [63c490af9cbe392ba025f15854173eb4f7fbbfad] encapsulate SecondaryIndex.estimateResultRows
patch by Miguel Angel Fernandez Diaz; reviewed by Sam Tunnicliffe for CASSANDRA-6498
# good: [7514e61b48e9456cf6591abaf6dbf17b52217883] update changes
git bisect start 'trunk' 'cassandra-2.0'
# good: [6c379343561766724e48d1d7cf98e282e8ec91dd] Merge branch 'cassandra-2.0' into trunk
git bisect good 6c379343561766724e48d1d7cf98e282e8ec91dd
# skip: [a13c6dcbb7a6ba74b27e50eef4bfd0f80eaea121] Merge branch 'cassandra-2.0' into trunk
git bisect skip a13c6dcbb7a6ba74b27e50eef4bfd0f80eaea121
# bad: [351d49b06bd6887447eecb149b3cdf1697ab41ac] validate directory permissions on startup
Patch by Lyuben Todorov and Koray Sariteke; reviewed by Mikhail Stepura for CASSANDRA-5818
git bisect bad 351d49b06bd6887447eecb149b3cdf1697ab41ac
# good: [5c21711e76731a6f48d67ca956ea865fda4574b4] merge from 2.0
git bisect good 5c21711e76731a6f48d67ca956ea865fda4574b4
# good: [52cc7efb2bcd47285148da85c089d796cb20734a] Merge branch 'cassandra-2.0' into trunk
git bisect good 52cc7efb2bcd47285148da85c089d796cb20734a
# good: [40598efa6344333d4d4deee2c1ec3e71bd931066] Merge branch 'cassandra-2.0' into trunk
git bisect good 40598efa6344333d4d4deee2c1ec3e71bd931066
# skip: [1bfd062fdc9daa35fbabcebb3ac31e726504f1ff] Merge branch 'cassandra-2.0' into trunk
git bisect skip 1bfd062fdc9daa35fbabcebb3ac31e726504f1ff
# bad: [7ea5b40b7172ec9f3fdecca533e19d8a165de7df] don't leave replaced SSTRs around to break
other tests patch by Tyler Hobbs
git bisect bad 7ea5b40b7172ec9f3fdecca533e19d8a165de7df
# bad: [9f3a7f8a698aaaa9be44bed01aaf526567df8aca] simple naming fixes
git bisect bad 9f3a7f8a698aaaa9be44bed01aaf526567df8aca
# bad: [8732fe938659232b3f0c63933b125131fa50fd2e] Merge branch 'cassandra-2.0' into trunk
git bisect bad 8732fe938659232b3f0c63933b125131fa50fd2e
# good: [87b39c8af3477c3b80f124da23b46de350a259e7] Merge branch 'cassandra-2.0' into trunk
git bisect good 87b39c8af3477c3b80f124da23b46de350a259e7
# good: [a10150542c662a4cc69ce1b88f48636d1e6884f7] merge from 2.0
git bisect good a10150542c662a4cc69ce1b88f48636d1e6884f7
# bad: [f3dc188e203b3db980ee81df05390968043cb601] move setting lastCompactedKey to before
the return-if-nothing-added
git bisect bad f3dc188e203b3db980ee81df05390968043cb601
{noformat}

> BlacklistingCompactionsTest fails in trunk
> ------------------------------------------
>
>                 Key: CASSANDRA-6414
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6414
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>             Fix For: 2.1
>
>         Attachments: 6414_out.txt
>
>
> Passes in 2.0 HEAD.  Bisect should be relatively easy.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message