You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't seen issues with the recently added FileClient tests on our CI but I experience consistently failing tests on my windows box
Not sure if it is related to my setup
File Client Implementation
√ should be able to write and read files using URI scheme file:/// with Content-Type application/json
√ should be able to write and read files using URI scheme file:/// with no Content-Type
1) should be able to write and read files using URI scheme file:/// with Content-Type text/plain
√ should be able to write and read files using URI scheme file:// with Content-Type application/json
√ should be able to write and read files using URI scheme file:// with no Content-Type
2) should be able to write and read files using URI scheme file:// with Content-Type text/plain
4 passing (20ms)
2 failing
1) File Client Implementation
should be able to write and read files using URI scheme file:/// with Content-Type text/plain:
AssertionError: expected '' to deeply equal 'Lorem ipsum dolor sit amet.'
...
2) File Client Implementation
should be able to write and read files using URI scheme file:// with Content-Type text/plain:
AssertionError: expected '' to deeply equal 'Lorem ipsum dolor sit amet.'
@relu91 since you are on Windows also. Do you have issues on your machine as well?
The text was updated successfully, but these errors were encountered:
The test also fail for me sometimes (I am currently using a Mac), so this is a general problem :/ I will try to come up with a fix for the issue, sorry for the inconvenience this causes :/
I haven't seen issues with the recently added FileClient tests on our CI but I experience consistently failing tests on my windows box
Not sure if it is related to my setup
@relu91 since you are on Windows also. Do you have issues on your machine as well?
The text was updated successfully, but these errors were encountered: