-
Notifications
You must be signed in to change notification settings - Fork 306
Move binary recordings to a single file instead of a directory #765
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
f34a77c to
8d63c65
Compare
|
I read through it, looks great! |
|
Looks like there is still a compile error on CI? |
|
Yes - working on it, I think I pushed the wrong branch. Checking on laptop
shortly
|
5226c10 to
13d6aba
Compare
|
@kvark OK, The CI errors are resolved, if you have time to re-look at this. |
|
☔ The latest upstream changes (presumably #775) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Thanks @vvuk, the code is great, and the changes are much welcome! |
|
@bors-servo delegate+ |
|
✌️ @vvuk can now approve this pull request |
13d6aba to
1df751b
Compare
|
@bors-servo r+ |
|
📌 Commit 1df751b has been approved by |
Move binary recordings to a single file instead of a directory No reason to use separate files. In the future, we could even gzip as we stream out (on a different thread maybe). This also cleans up the recording code to just have a single unified path instead of separate detour stuff. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/765) <!-- Reviewable:end -->
|
☀️ Test successful - status-travis |
No reason to use separate files. In the future, we could even gzip as we stream out (on a different thread maybe). This also cleans up the recording code to just have a single unified path instead of separate detour stuff.
This change is