Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-16567

Fix test testCompoundPartitionKey - org.apache.cassandra.cql3.ViewTest

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Correctness - Test Failure
    • Normal
    • Normal
    • Unit Test
    • All
    • None
    • Hide

      The PR includes a new test that consistently creates the scenario that I think is making testCompoundPartitionKey fail in rare occasions.

      Show
      The PR includes a new test that consistently creates the scenario that I think is making testCompoundPartitionKey fail in rare occasions.

    Description

      https://app.circleci.com/pipelines/github/dcapwell/cassandra/874/workflows/0b0a1e36-107a-43c7-815f-bf8e61d3028d/jobs/5227/tests

      junit.framework.AssertionFailedError: Got more rows than expected. Expected 0 but got 1.
      	at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1185)
      	at org.apache.cassandra.cql3.ViewTest.testCompoundPartitionKey(ViewTest.java:817)
      

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            adelapena Andres de la Peña Assign to me
            dcapwell David Capwell
            Andres de la Peña
            Ekaterina Dimitrova
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 4h 40m
                4h 40m

                Slack

                  Issue deployment