Skip to content
This repository has been archived by the owner on Sep 21, 2024. It is now read-only.

nextest should bail after several SLOW runs #706

Closed
jsantell opened this issue Nov 1, 2023 · 2 comments · Fixed by #777
Closed

nextest should bail after several SLOW runs #706

jsantell opened this issue Nov 1, 2023 · 2 comments · Fixed by #777
Labels
Chore Non-user-facing feature Enhancement New user-facing feature

Comments

@jsantell
Copy link
Contributor

jsantell commented Nov 1, 2023

Currently, SLOW runs on nextest are retried with a longer timeout, with seemingly no termination clause (e.g. after 10 retries), and will run until we manually terminate the job. We should see if we can limit this to a number of explicit attempts.

TRY 1 SLOW [> 60.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>120.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>180.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>240.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>300.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>360.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>420.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>480.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>540.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>600.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>660.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>720.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>780.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>840.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>900.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>960.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1020.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1080.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1140.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1200.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1260.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1320.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1380.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1440.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1500.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1560.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1620.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1680.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1740.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1800.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1860.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1920.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>1980.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2040.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2100.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2160.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2220.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2280.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2340.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2400.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2460.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
  TRY 1 SLOW [>2520.000s] noosphere::distributed_stress latency::clients_can_sync_when_there_is_a_lot_of_content
@jsantell jsantell added Enhancement New user-facing feature Chore Non-user-facing feature labels Nov 1, 2023
@jsantell
Copy link
Contributor Author

jsantell commented Nov 3, 2023

Looks like we can set terminating after X tries for slow tests: https://nexte.st/book/slow-tests.html

@jsantell
Copy link
Contributor Author

jsantell commented Jan 9, 2024

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Chore Non-user-facing feature Enhancement New user-facing feature
Projects
None yet
1 participant