Skip to content

Conversation

@fjetter
Copy link
Member

@fjetter fjetter commented Mar 24, 2023

cc @wence- This is roughly what I had originally in mind (there are still a couple of problems to iron out but overall it works) regarding #7664

I'm mildly disappointed since the simple test I was trying this with didn't change in terms of performance but I haven't run our entire benchmark suite

@github-actions
Copy link
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

       25 files   -        1         25 suites   - 1   12h 59m 35s ⏱️ + 27m 34s
  3 545 tests ±       0    3 431 ✔️  -        2     105 💤 ±    0    9 +  2 
43 114 runs   - 1 711  41 162 ✔️  - 1 548  1 921 💤  - 186  31 +23 

For more details on these failures, see this check.

Results for commit 06ffb3a. ± Comparison against base commit 51ce7cf.

@wence-
Copy link
Contributor

wence- commented Mar 24, 2023

Thanks, I'll have a look through properly to compare.

@fjetter fjetter closed this Jul 10, 2025
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