-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Dependents are no longer tested in CI #22172
Comments
I was noticing some duplication of dependents yesterday. I'll take a look and see what the cause is. Thanks |
Dependents are still not tested. see https://travis-ci.org/DefinitelyTyped/DefinitelyTyped/builds/318002459?utm_source=github_status&utm_medium=notification |
Seems like testing dependencies is back - and also unrelated fails and timeouts. see https://travis-ci.org/DefinitelyTyped/DefinitelyTyped/builds/318182029?utm_source=github_status&utm_medium=notification I ask myself why I reported this 😢 |
We're up to 4007 typings now, so we're running into timeouts again even if testing only with |
Is it somehow possible to split the test in to several jobs? |
That might be possible, but I'd like to look into improving performance as we also run all of the tests in a nightly script that is taking increasingly longer. |
@types/xxxx
package and had problems.Definitions by:
inindex.d.ts
) so they can respond.@andy-ms @RyanCavanaugh
A while ago all dependents have been tested also in CI. This was a pain for node as it resulted in timeouts and unrelated fails as it took too long to test all of them with all typescript version.
To my understanding this was improved via microsoft/types-publisher#398 to test dependents just with typescript@next.
Now it looks like that dependents are not tested at all anymore. is this intended?
See e.g. https://travis-ci.org/DefinitelyTyped/DefinitelyTyped/builds/316119572?utm_source=github_status&utm_medium=notification
The text was updated successfully, but these errors were encountered: