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
Interrupting wptrunner as manifest is regenerated causes MANIFEST.json to be corrupted #7142
Comments
Originally posted as w3c/wptrunner#256 (comment) by @gsnedders on 01 Aug 2017, 14:42 UTC:
|
Earlier, interrupting the manifest-update could end up causing errors due to the non-atomicity of the process. Used tempfile to ensure that the file is written correctly.
Earlier, interrupting the manifest-update could end up causing errors due to the non-atomicity of the process. Used tempfile to ensure that the file is written correctly.
Earlier, interrupting the manifest-update could end up causing errors due to the non-atomicity of the process. Used tempfile to ensure that the file is written correctly.
Earlier, interrupting the manifest-update could end up causing errors due to the non-atomicity of the process. Used tempfile to ensure that the file is written correctly.
Earlier, interrupting the manifest-update could end up causing errors due to the non-atomicity of the process. Used tempfile to ensure that the file is written correctly.
Earlier, interrupting the manifest-update could end up causing errors due to the non-atomicity of the process. Used tempfile to ensure that the file is written correctly.
Reopening the issue because the fix caused a bug and was reverted. |
Looking at #9736, there is a way to open a file while still allowing replacement: https://stackoverflow.com/a/18169890
|
This was fixed by #24032. |
Originally posted as w3c/wptrunner#256 by @andreastt on 31 Jul 2017, 13:51 UTC:
The text was updated successfully, but these errors were encountered: