-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clean up liveslots tests #10739
base: master
Are you sure you want to change the base?
clean up liveslots tests #10739
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
fe9c874
to
9b64cca
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I very much like switching to worker threads (if we're compatible) and the test cleanup, I'm a less convinced by the individual switch of a single package to ava@6. I'd prefer if we kept that for #9083
It is regrettable but in exploring #9081 it's going to be a while until we adopt it. Even when we can get green CI, there are some UX regressions that may require upstream contributions. Meanwhile we have a flakey GC test, which is a more severe technical debt than packages having different versions. |
This pull request has been removed from the queue for the following reason: The pull request can't be updated You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. If you want to requeue this pull request, you need to post a comment with the text: |
Sure, I just don't understand how a new version of ava is expected to fix the flakey aspect. It seems we're shooting in the dark here, and it feels that the workerThreads change is a lot more likely to have an effect than a newer version. Unless there is something specific with newer ava that is expected to help, but I don't see anything mentioned in the description. |
refs: #5575
Description
I read #5575 (comment) and thought it would be good to be on the latest version of Ava and default configuration before reworking the tests more.
This does that and also changes the four
test.failing
to usetest
that are confirmed to be the correct behavior. Since the test is of test failures, it uses a new spy instead.Security Considerations
none
Scaling Considerations
none
Documentation Considerations
This is one package of the monorepo on Ava 6. I tried bumping them all before but ran into problems. We should tackle them all eventually,
Testing Considerations
This might solve #5575 but we won't know for a while since it's intermittent. Still it reduces variables in solving that problem.
Upgrade Considerations
none