-
Notifications
You must be signed in to change notification settings - Fork 675
Cache recourses between tests #5888
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
Conversation
❌ Tests for the commit 8ad0410 have failed. See details: |
2 similar comments
❌ Tests for the commit 8ad0410 have failed. See details: |
❌ Tests for the commit 8ad0410 have failed. See details: |
❌ Tests for the commit 4136a8e have failed. See details: |
f27cf0c
to
7d0365e
Compare
❌ Tests for the commit 7d0365e have failed. See details: |
❌ Tests for the commit f4c0aae have failed. See details: |
❌ Tests for the commit 40d480a have failed. See details: |
❌ Tests for the commit 0c4df24 have failed. See details: |
6a44d71
to
0a71d08
Compare
FPR. The tests are green. The TestCafe build bot didn't add a necessary comment for some reason to the issue. |
Changes:
--cache
option that turn on the caching resources (script and styles) between test runs.http.Server
in tests (Keep alive connection do not get closed with server.close() nodejs/node#2642) correctly.