Conversation
Deploying agoric-sdk with
|
| Latest commit: |
af03497
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://49a16dfe.agoric-sdk.pages.dev |
| Branch Preview URL: | https://ta-ava-6.agoric-sdk.pages.dev |
a8ac83e to
844cedd
Compare
149982a to
a2ab680
Compare
refs: #5575 ## Description As needed for Ava 6, - #9083 It has different exception behavior that breaks the intentional `.failing` hack. This changes the four`test.failing` to use `test` 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](#9081) but ran into problems. We should tackle them all eventually,~ (DEFERRED) ### Testing Considerations per se ### Upgrade Considerations none
|
@copilot get this branch to green. It updates Ava which is causing some tests to fail. Keep track of the status of all packages and which tests are failing in a Markdown file. Fix one package at a time. When you've fixed a package, make a conventional commit ("test:") with the changes indicating that it's now compatible with Ava 6. If the problem is tracking unhandled rejections, consider using |
|
|
|
Reviewers, there may be a flake in the Update: a re-run of the failing test passed. It's probably just an existing flake |
This comment was marked as resolved.
This comment was marked as resolved.
|
@Mergifyio refresh |
✅ Pull request refreshed |
mhofman
left a comment
There was a problem hiding this comment.
Some questions I'd prefer to be addressed before merging.
| --- a/lib/reporters/tap.js | ||
| +++ b/lib/reporters/tap.js |
There was a problem hiding this comment.
Any reason to remove the tap reporting patch ? Are we no longer using the duration?
There was a problem hiding this comment.
Any reason to remove the tap reporting patch ?
Like for any patch removal, to reduce maintenance costs.
Are we no longer using the duration?
That's my understanding. It was added for Datadog CI that we stopped a while ago. Even when we had it we didn't do much with it.
| }); | ||
|
|
||
| test.serial.failing('test durable first-crank hazard 3', async t => { | ||
| test.serial.skip('test durable first-crank hazard 3', async t => { |
There was a problem hiding this comment.
Why switch from failing to skip ?
There was a problem hiding this comment.
I don't recall the specifics but I'm sure it's because it caused the job to fail. Reading the v6 changes I bet it's this one:
When tests finish, worker threads or child processes are no longer exited through proces.exit(). If your test file does not exit on its own, the test run will time out
scripts/packing/postpack-package.mjs
Outdated
| console.log(' → cleaning generated files'); | ||
| try { | ||
| execSync("git clean -f '*.d.ts' '*.d.ts.map' '*.js'", { | ||
| execSync("git clean -f '*.d.ts' '*.d.ts.map' '*.js' '*.mts'", { |
There was a problem hiding this comment.
Curious why this change is in the PR?
There was a problem hiding this comment.
The commit preceding it adds an .mjs file which results in an .mts file being built by prepack that must then be cleaned in postpack to get back to a clean checkout for the porcelain check
There was a problem hiding this comment.
Oh it's an .d.mts that gets generated. I'm surprised it even needs the m modifier, that whole package has type: module already.
Skip test demonstrating bug #9377 that causes unhandled rejection with Ava 6 Co-authored-by: turadg <21505+turadg@users.noreply.github.com>
Properly await and assert on the rejected promise in paramGovernance test Co-authored-by: turadg <21505+turadg@users.noreply.github.com>
Ava 6 requires tests to exit cleanly or they will timeout. Added test.after.always hook to call shutdown. Co-authored-by: turadg <21505+turadg@users.noreply.github.com>
Was consistently timing out in CI on Node 22.21.1 (passing on Node 20)
The test intentionally creates unhandled rejections to validate promise watcher behavior. Added handler to prevent Ava 6 from killing the process when these expected unhandled rejections occur. Co-authored-by: turadg <21505+turadg@users.noreply.github.com>
This removes the disabling in all package.json
Drop Node.js 18 and 21, explicitly support 24
closes: #9083
Description
Breaking changes in v6: https://github.com/avajs/ava/releases/tag/v6.0.0
Relevant subset:
When tests finish, worker threads or child processes are no longer exited through proces.exit(). If your test file does not exit on its own, the test run will time out. Don't force-exit after tests have completed avajs/ava#3260
Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. Make assertions throw avajs/ava#3246
Only native errors are now considered errors by the t.throws() and t.throwsAsync() assertions. Object.create(Error.prototype) is not a native error. Only treat native errors as errors avajs/ava#3229
This removes our local patches of Ava
Security Considerations
none, no runtime change
Scaling Considerations
none, no runtime change
Documentation Considerations
none
Testing Considerations
CI
Upgrade Considerations
none, no runtime change