Issue metadata
Sign in to add a comment
|
speedometer2-future consistently timed out on Win Dbg |
||||||||||||||||||||||
Issue descriptionThis is blocking enabling telemetry_perf_unittest test suite on Win 7 Dbg. Since this is a consistent failure, it should be easy to reproduce. Reassign to hablich@ to triage fixing this. If this is not resolved in 2 weeks, I will have to disable speedometer2-future on Win platform. Swarming Log: https://chromium-swarm.appspot.com/task?id=3a513ffbb2b74110&refresh=10
,
Dec 12 2017
I tried to follow the instructions on the bot page, but I'm unable to download the files on my win10 box. python isolateserver.py download -I https://isolateserver.appspot.com --namespace default-gzip -s 4733816f48d584ba233966163127b88dec0e68b4 --target foo I'm a bit overwhelmed by the raw bot output, I miss the information we usually find on the V8 bots: - what gn args were used to build chrome - what is the command to run the tests (I don't see where (run_telemetry_as_googletest.py would get the chrome binary from) As a V8 engineer I'm used to running such tests locally and instrument the binary. Not sure what the way is or what the output is I miss, but it would be nice to maybe have this more prominently listed somewhere.
,
Dec 12 2017
#3: The command to run the test is in the log: Command: c:\infra-system\bin\python.exe ..\..\testing\scripts\run_telemetry_as_googletest.py ../../tools/perf/run_tests -v --isolated-script-test-output=e:\b\s\w\iol9ln4b\output.json --isolated-script-test-perf-output=e:\b\s\w\iol9ln4b\perftest-output.json +Ben Pastene for the issue about downloading the isolate offline. "python isolateserver.py download -I https://isolateserver.appspot.com --namespace default-gzip -s 4733816f48d584ba233966163127b88dec0e68b4 --target foo" should work. What was the output that you saw?
,
Dec 12 2017
Here's the build where it failed: https://ci.chromium.org/buildbot/tryserver.chromium.win/win_chromium_dbg_ng/2690 Here's that build's gn args: https://logs.chromium.org/v/?s=chromium%2Fbb%2Ftryserver.chromium.win%2Fwin_chromium_dbg_ng%2F2690%2F%2B%2Frecipes%2Fsteps%2Fgenerate_build_files__with_patch_%2F0%2Fstdout
,
Dec 13 2017
,
Dec 14 2017
,
Dec 14 2017
Re #3: I have the same problem. I am currently waiting on my Windows machine to be reimaged. The bots are very, very chatty. The instructions regarding for reproing are also not very clear or correct. I had similar problems yesterday when trying to repro another problem with the perf unit tests. @Ned: With whom do we need to talk to in order to get the workflow for reproductions streamlined?
,
Dec 14 2017
1st step: you should be able to fetch the isolate to you local machine with the command in the swarming log: python swarming.py collect -S chromium-swarm.appspot.com --task-output-dir=foo 3a513ffbb2b74110 swarming.py is located in //src/tools/swarming_client/swarming.py 2nd step: Once you fetched those file in the foo directory, go to the directory & run the test command from there: ./tools/perf/run_tests --browser=debug speedometer2-future Let me know if you have any problem following those 2 steps. Please post the results of your console log if the command fails.
,
Dec 25 2017
The NextAction date has arrived: 2017-12-25
,
Mar 1 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nedngu...@google.com
, Dec 11 2017