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
[infra] Replace lerna run with top-level wireit scripts #3098
Conversation
🦋 Changeset detectedLatest commit: 9843932 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📊 Tachometer Benchmark ResultsSummarynop-update
render
update
update-reflect
Resultslit-element-list
render
update
update-reflect
lit-html-kitchen-sink
render
update
nop-update
lit-html-repeat
render
update
lit-html-template-heavy
render
update
reactive-element-list
render
update
update-reflect
|
@@ -226,7 +226,7 @@ const config: TestRunnerConfig = { | |||
// enough so that blocked tests have time to wait for all previous test files | |||
// to run to completion. | |||
testsStartTimeout: 60000 * 10, // default 120000 | |||
testsFinishTimeout: 120000, // default 20000 | |||
testsFinishTimeout: 180000, // default 20000 |
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.
why would this change require a longer timeout?
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.
See PR description. I think it's because both tests:test
and labs/ssr:test
are now running in parallel, so there must be some resource starvation that causes the test to take longer. It seemed to particularly affect Firefox.
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.
I bumped it even higher, to make it pass reliably. I think this is just a contention thing. But the good news is that overall test time seems lower: latest full run of the test step was 7m28s, compared to 9m58s on the most recent commit on main.
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.
This is great!
Also added these items:
|
Oh and also:
|
Oops, did not mean to close. |
47fd60f
to
9843932
Compare
@augustjk I also included some tweaks to the new |
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.
Thanks for fixing the labs/testing wireit configs!
Replaces all
lerna run
scripts withwireit
scripts.Benefits
Increased parallelism during build/test.
We'll now only be using Lerna for bootstrapping, so we can replace it with npm workspaces in a followup PR.
It's now easier to figure out which packages failed, because the log statements will say e.g.
[packages/lit-html:build] Failed ...
instead of[build] Failed
.Enumerated packages
This does include some long enumerations of packages. Once we have google/wireit#23, we could replace this with something like:
However, we currently exclude some packages, e.g. we don't run
lit-html
/lit-element
package tests, because they are subsumed by thetests
package. Previously we excluded them with Lerna--ignore
flags. Now they are just not in the list.Maybe once we have the above Wireit feature, we could add
test:ci
scripts, which would not be present in the case of packages whose tests we don't want to run in CI.Also
Fixes an incorrect virtualizer output path.
Fixes an output issue where the lit-html
build:version-stability-test
config was emittingpolyfill-support.js
, which collided with the same file emitted bybuild:rollup
.Bumps the wtr tests finished timeout. Running both the SSR and main browser tests in parallel makes tests take longer. I guess because of resource starvation.
Added some additional dependencies to the new
testing
package.Fixes #2724
Part of #3093