Issue metadata
Sign in to add a comment
|
Archiving recorded .wav file for WebRTC Chrome Audio Quality tests |
||||||||||||||||||||||||
Issue descriptionTracking bug for adding a buildbot step to run after the browser_tests test in https://cs.chromium.org/chromium/src/chrome/browser/media/webrtc/webrtc_audio_quality_browsertest.cc that will upload the .wav file to Google storage (chromium-webrtc bucket). In a per master-builder-build# directory. Then it can provide a display link in the waterfall view, similar to the one for logcat_dump step: https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/chromium_android/api.py?rcl=0&l=963 In order to know the name and location of the recorded file, the code at https://cs.chromium.org/chromium/src/chrome/browser/media/webrtc/webrtc_audio_quality_browsertest.cc?rcl=0&l=487 will need to be updated.
,
Oct 18 2017
,
Nov 13 2017
,
Nov 20 2017
Assigning to phoglund for further triage.
,
Nov 20 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Sep 8 2017Status: Untriaged (was: Available)