Skip to content

Conversation

@fjetter
Copy link
Member

@fjetter fjetter commented Apr 29, 2022

This reworks the control flow for missing tasks which should get rid of all assert ts.who_has issues. The essence is that all _to_fetch transitions will check on who_has and transition to missing instead. Combined with the check in the exception handler of gather_dep AND the guard in ensure_communicating, this should plug all holes where this could be introduced 🤞

It also includes #6248

Locally, the test_chaos_rechunk hasn't failed in 100 tries (running concurrently) (This already includes the fail_hard decorator)

I would like to get my other PRs merged that modify the state machine and revisit this afterwards

@github-actions
Copy link
Contributor

Unit Test Results

       16 files  ±  0         16 suites  ±0   7h 13m 50s ⏱️ - 9m 33s
  2 745 tests +  2    2 662 ✔️ +  3       80 💤  - 1  3 ±0 
21 861 runs  +16  20 812 ✔️ +20  1 043 💤  - 5  6 +1 

For more details on these failures, see this check.

Results for commit 9682b97. ± Comparison against base commit 70e1fca.

@mrocklin
Copy link
Member

mrocklin commented Oct 11, 2022 via email

@fjetter
Copy link
Member Author

fjetter commented Oct 18, 2022

For reference, on my computer test_chaos_rechunk would fail every ~20
iterations.

We're going to need to find a way to amp up the chaos soon.

Can you provide a traceback or smth like that?

@mrocklin
Copy link
Member

About a week ago a bunch of messages were sent out from my account to ancient issues. I think that github was having some issue at the time. If there are messages from me at around that time that seem oddly timed then please ignore.

@fjetter fjetter closed this Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants