[jira] [Updated] (CASSANDRA-6177) remove all sleeps in the dtests

2019-05-30 Thread Vincent Yang (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vincent Yang updated CASSANDRA-6177:

Labels:   (was: Testx)

> remove all sleeps in the dtests
> ---
>
> Key: CASSANDRA-6177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6177
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Test/dtest
>Reporter: Brandon Williams
>Priority: Normal
>
> The dtests use a ton of sleep calls for various things, most of which is 
> guessing if Cassandra has finished doing something or not.  Guessing is 
> problematic and shouldn't be necessary -- a prime example of this is creating 
> a ks or cf.  When done over cql, we sleep and hope it's done propagating, but 
> when done over thrift we actually check for schema agreement.  We should be 
> able to eliminate the sleeps and reliably detect when it's time for the next 
> step programmatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-6177) remove all sleeps in the dtests

2019-05-30 Thread Vincent Yang (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vincent Yang updated CASSANDRA-6177:

Labels: Testx  (was: )

> remove all sleeps in the dtests
> ---
>
> Key: CASSANDRA-6177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6177
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Test/dtest
>Reporter: Brandon Williams
>Priority: Normal
>  Labels: Testx
>
> The dtests use a ton of sleep calls for various things, most of which is 
> guessing if Cassandra has finished doing something or not.  Guessing is 
> problematic and shouldn't be necessary -- a prime example of this is creating 
> a ks or cf.  When done over cql, we sleep and hope it's done propagating, but 
> when done over thrift we actually check for schema agreement.  We should be 
> able to eliminate the sleeps and reliably detect when it's time for the next 
> step programmatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-6177) remove all sleeps in the dtests

2018-11-18 Thread C. Scott Andreas (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

C. Scott Andreas updated CASSANDRA-6177:

Component/s: Testing

> remove all sleeps in the dtests
> ---
>
> Key: CASSANDRA-6177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6177
> Project: Cassandra
>  Issue Type: Test
>  Components: Testing
>Reporter: Brandon Williams
>Priority: Major
>
> The dtests use a ton of sleep calls for various things, most of which is 
> guessing if Cassandra has finished doing something or not.  Guessing is 
> problematic and shouldn't be necessary -- a prime example of this is creating 
> a ks or cf.  When done over cql, we sleep and hope it's done propagating, but 
> when done over thrift we actually check for schema agreement.  We should be 
> able to eliminate the sleeps and reliably detect when it's time for the next 
> step programmatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-6177) remove all sleeps in the dtests

2016-05-23 Thread Philip Thompson (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Thompson updated CASSANDRA-6177:
---
Assignee: (was: Steve Wang)

> remove all sleeps in the dtests
> ---
>
> Key: CASSANDRA-6177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6177
> Project: Cassandra
>  Issue Type: Test
>Reporter: Brandon Williams
>
> The dtests use a ton of sleep calls for various things, most of which is 
> guessing if Cassandra has finished doing something or not.  Guessing is 
> problematic and shouldn't be necessary -- a prime example of this is creating 
> a ks or cf.  When done over cql, we sleep and hope it's done propagating, but 
> when done over thrift we actually check for schema agreement.  We should be 
> able to eliminate the sleeps and reliably detect when it's time for the next 
> step programmatically.



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


[jira] [Updated] (CASSANDRA-6177) remove all sleeps in the dtests

2015-06-18 Thread Philip Thompson (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Thompson updated CASSANDRA-6177:
---
Assignee: Steve Wang  (was: Philip Thompson)

 remove all sleeps in the dtests
 ---

 Key: CASSANDRA-6177
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6177
 Project: Cassandra
  Issue Type: Test
Reporter: Brandon Williams
Assignee: Steve Wang

 The dtests use a ton of sleep calls for various things, most of which is 
 guessing if Cassandra has finished doing something or not.  Guessing is 
 problematic and shouldn't be necessary -- a prime example of this is creating 
 a ks or cf.  When done over cql, we sleep and hope it's done propagating, but 
 when done over thrift we actually check for schema agreement.  We should be 
 able to eliminate the sleeps and reliably detect when it's time for the next 
 step programmatically.



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


[jira] [Updated] (CASSANDRA-6177) remove all sleeps in the dtests

2013-11-06 Thread Cathy Daw (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cathy Daw updated CASSANDRA-6177:
-

Assignee: (was: Daniel Meyer)

 remove all sleeps in the dtests
 ---

 Key: CASSANDRA-6177
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6177
 Project: Cassandra
  Issue Type: Test
Reporter: Brandon Williams

 The dtests use a ton of sleep calls for various things, most of which is 
 guessing if Cassandra has finished doing something or not.  Guessing is 
 problematic and shouldn't be necessary -- a prime example of this is creating 
 a ks or cf.  When done over cql, we sleep and hope it's done propagating, but 
 when done over thrift we actually check for schema agreement.  We should be 
 able to eliminate the sleeps and reliably detect when it's time for the next 
 step programmatically.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (CASSANDRA-6177) remove all sleeps in the dtests

2013-10-09 Thread Brandon Williams (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-6177:


Description: The dtests use a ton of sleep calls for various things, most 
of which is guessing if Cassandra has finished doing something or not.  
Guessing is problematic and shouldn't be necessary -- a prime example of this 
is creating a ks or cf.  When done over cql, we sleep and hope it's done 
propagating, but when done over thrift we actually check for schema agreement.  
We should be able to eliminate the sleeps and reliably detect when it's time 
for the next step programmatically.  (was: The dtests use a ton of sleep calls 
for various things, most of which is guessing if Cassandra has finished doing 
something or not.  Guessing is problematic and shouldn't be necessary -- a 
prime example of this is creating a ks or cf.  When done over cql, we have to 
sleep and hope it's done propagating, but when done over thrift we actually 
check for schema agreement.)

 remove all sleeps in the dtests
 ---

 Key: CASSANDRA-6177
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6177
 Project: Cassandra
  Issue Type: Test
Reporter: Brandon Williams
Assignee: Ryan McGuire

 The dtests use a ton of sleep calls for various things, most of which is 
 guessing if Cassandra has finished doing something or not.  Guessing is 
 problematic and shouldn't be necessary -- a prime example of this is creating 
 a ks or cf.  When done over cql, we sleep and hope it's done propagating, but 
 when done over thrift we actually check for schema agreement.  We should be 
 able to eliminate the sleeps and reliably detect when it's time for the next 
 step programmatically.



--
This message was sent by Atlassian JIRA
(v6.1#6144)