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
The test suit does not inspect what happens on failed IO operation, neither does the task say anything about it. My suggestion would be that we say that we say that you should only log on sucsessful operations.
The text was updated successfully, but these errors were encountered:
meltinglava
changed the title
PaaS I/O test suit unsutable.
PaaS I/O test suit does not account for failing io opperations.
Oct 29, 2020
I can add the documentation, but the tests does not reflect this. I saw examples of people completing the task with incrementing the amount of reads counters first, then read the bytes, then check for failures and then check update the amount of bytes read. There needs to be a test that makes sure that when an operation fails, the counter and the amounts of bytes read/written as well as the amunts of reads/writs are unchanged.
That's sensible. That test, plus documentation, would be even better than just the documentation.
ghost
changed the title
PaaS I/O test suit does not account for failing io opperations.
PaaS I/O test suit does not account for failing io operations.
Mar 17, 2021
The test suit does not inspect what happens on failed IO operation, neither does the task say anything about it. My suggestion would be that we say that we say that you should only log on sucsessful operations.
The text was updated successfully, but these errors were encountered: