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] Fix flaky ts-starter-kit tests #3157
Conversation
🦋 Changeset detectedLatest commit: a56cdc4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
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
|
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.
You legend!
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 am totally on board with this to make our pipeline smoother and have excitedly approved, a tiny reservation about this is that the starter kits are also meant as templates for users to potentially replicate for their own projects. Setting a config purely based on our workflow seems less ideal. Though a longer timeout setting is pretty innocuous, and we're also considering revamping these hopefully soon so I don't think we need to worry so much about it. Alternative way to deflake would be to run the starter kit tests independently, either in serial or a separate job, with the similar idea as we have separate build steps for those already in our monorepo. |
Good point. Done. |
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.
Thank you!!!
I think the flakes we have been seeing from the starter kit test were just timeouts. Since things are running in parallel, it sometimes takes longer for browser tests to start. The starter kits now run separately, after the other tests, so that they have less resource contention. We could also bump the
browserStartTimeout
, but since it's a user template repo, that seems weird.Also: