Conversation
2935e5b to
9a0e9b2
Compare
132eb79 to
190d1b4
Compare
d7e4008 to
43be771
Compare
|
@jschwe Updated it. |
12d90b7 to
e131c93
Compare
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
For all action run links you provided, I did not see any output like before in scenario tests, and all finish in 1 sec:
Here is a sample before your PR:
https://github.com/servo/servo/actions/runs/21271461325/job/61222532498
e131c93 to
dc035b2
Compare
This comment was marked as outdated.
This comment was marked as outdated.
dc035b2 to
f3a6318
Compare
5e9c080 to
cc11e85
Compare
Signed-off-by: Narfinger <[email protected]>
Signed-off-by: Narfinger <[email protected]>
Signed-off-by: Narfinger <[email protected]>
|
I would have assumed that too but I don't know why. |
This has a couple of changes to use mitmproxy in the ohos benchmarking CI. - We include an easy script to create a mitmproxy dump (etc/ci/scenario/update-mitmproxy-dump.py). - We set the port forwarding in the common_function_for_servo_test (with a refactor of the code). - We added the use of mitmproxy to scenario test and bencher runs. This currently runs in strictly forwarding mode. But because we skip the wifi connection and use a wired connection, this should defeat jitter a bit. - This does _not_ include the smoketest and hitrace-bench. Signed-off-by: Narfinger <[email protected]> Testing: https://github.com/Narfinger/servo/actions/runs/21630846381/job/62343433828 In the future we will add smoketest and hitrace-bench to use mitmproxy and finally switch mitmproxy to record and replay mode. --------- Signed-off-by: Narfinger <[email protected]>
How to use this? Can you write a guide? Also explain a bit how the dump works. Maybe also some URL to introduce mitmproxy too. Thanks! |
|
Do you have a good idea where to write this? There is already a guide on mitmproxy in the servo book. |
Ah nice. Can you put in PR description at least? I think you are talking about https://book.servo.org/contributing/profiling.html?highlight=mitmproxy#webpage-snapshots Also, maybe write at the top of |
Signed-off-by: Narfinger <[email protected]>
Signed-off-by: Narfinger <[email protected]>
Co-authored-by: Euclid Ye <[email protected]> Signed-off-by: Narfinger <[email protected]>
|
@Narfinger |
Signed-off-by: Narfinger <[email protected]>
This has a couple of changes to use mitmproxy (see more https://book.servo.org/contributing/profiling.html?highlight=mitmproxy#webpage-snapshots) in the ohos benchmarking CI.
Signed-off-by: Narfinger [email protected]
Testing: https://github.com/Narfinger/servo/actions/runs/21630846381/job/62343433828
In the future we will add smoketest and hitrace-bench to use mitmproxy and finally switch mitmproxy to record and replay mode.