-
Notifications
You must be signed in to change notification settings - Fork 220
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
Internal FD browser don't close socket connect itself #63
Comments
Probably not a socket thing (munit close the test server when it's done) but likely a browser cache issue. Not sure what would be the best solution - probably appending a random value at the end of the test urls. |
I made this conclusion because sometimes I get a message about the browsers socket is busy. |
Disabling cache in IE hasn't effect. |
Can you provide the exact error you get? |
I'll try but it happens just sometimes. |
When I run munit inside FD I should relaunch FD many times.
FD browser remember data from last session and not update it.
I think it happens because connection not closes after closing the browser tab.
The text was updated successfully, but these errors were encountered: