Skip to content

Fix "layout first" transition race condition - #4262

Merged
etpinard merged 4 commits into
masterfrom
fix-layout-first-transition-race-condition
Oct 9, 2019
Merged

Fix "layout first" transition race condition#4262
etpinard merged 4 commits into
masterfrom
fix-layout-first-transition-race-condition

Conversation

@etpinard

Copy link
Copy Markdown
Contributor

- make testing `invocationOrder` possible, along side
"did get called" vs "did not get called" checks
- adapt assertSpies calls that checked arguments from multiple calls
of a given spy, now each "expectations" item corresponds to
one function call
... to remove "jump" caused by transitionTraces()
@archmoj

Copy link
Copy Markdown
Contributor

Excellent.
💃

@etpinard

Copy link
Copy Markdown
ContributorAuthor

Thanks for the review @archmoj - note that the changes here might add some "flakiness" to the transition_test.js suite. If you notice a particular test in that suite failing intermittently in the coming days, please let me know.

@etpinard
etpinard merged commit abbd92d into masterOct 9, 2019
@etpinard
etpinard deleted the fix-layout-first-transition-race-condition branch October 9, 2019 13:21
@archmoj

Copy link
Copy Markdown
Contributor

Thanks for the review @archmoj - note that the changes here might add some "flakiness" to the transition_test.js suite. If you notice a particular test in that suite failing intermittently in the coming days, please let me know.

Yes. I noticed one test failed the first time. But then it passed the second time.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugsomething broken

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bar transition oddities

2 participants

@etpinard@archmoj