Linux Tryserver in Catapult CQ appears to be consistently failing with:
Starting WCT: ['/b/s/w/ir/kitchen-workdir/packages/wct', '-chrome', u'/b/s/w/ir/kitchen-workdir/catapult/common/py_utils/py_utils/bin/reference_build/chrome_stable_linux_x86_64_aab60e4a4ee4f3d638aa6a33e52ffb6423fa7080/chrome-linux64/chrome', '-dir', '/b/s/w/ir/tmp/t/tmpAvnla2', '-base', '/b/s/w/ir/kitchen-workdir/catapult/dashboard', '-dep', '/b/s/w/ir/kitchen-workdir/catapult/third_party/polymer2', '-dep', '/b/s/w/ir/kitchen-workdir/catapult/third_party/redux', '-dep', '/b/s/w/ir/kitchen-workdir/catapult/tracing/third_party', '-dep', '/b/s/w/ir/kitchen-workdir/catapult/tracing/third_party/gl-matrix/dist', '-dep', '/b/s/w/ir/kitchen-workdir/catapult/tracing']
flag provided but not defined: -dep
Usage of /b/s/w/ir/kitchen-workdir/packages/wct:
-base string
location of elements to test (default "./")
-bower string
location of bower compoenents (default "bower_components/")
-chrome string
location of chrome binary
-debug-port string
chrome debugger port (default "9222")
-dir string
user directory (default "/tmp/")
-persist
keep server running
-prefix string
path prefix for test runner URL (default "/test/")
-timeout int
timeout seconds (default 60)
step returned non-zero exit code: 2
https://logs.chromium.org/logs/catapult/buildbucket/cr-buildbucket.appspot.com/8934154768256773360/+/steps/Dashboard_WCT_Tests/0/stdout
Any clue why is that?
I set the infra/testing/wct CIPD package to the new build with this command yesterday:
cipd set-ref infra/testing/wct/linux-amd64 -version BoHf5DkpKDor0wSIEUTjZ2VZFqMWtM0Q7wPOYsqgLCYC -ref prod
I'll roll it back to the previous version 6afc3c447c5ca107369306896fd4334fe263e79e and see if that fixes the build for now.
bjhayden@: It looks like a recipe or recipe module needs to be updated for catapult before we can roll the CIPD package forward again.
Sorry for the breakage!
I just ran
cipd set-ref infra/testing/wct/linux-amd64 -version 0bJ1imIfx8FkbL53wCZYcczd8ZY-CKewX3X00v5i-T8C -ref prod
With a fresh build of wct.go, in case it was an older build I pushed previously. Will watch infra and catapult builders for a bit and roll back if necessary.
The issue on Infra WCT Tester looks like it's probably how it's interpreting the --base flag:
xvfb-run -a /b/s/w/ir/kitchen-workdir/packages/wct --base /b/s/w/ir/kitchen-workdir/infra/crdx/chopsui [yadda yadda...]
leads to:
[{"method":"Log.entryAdded","params":{"entry":{"source":"network","level":"error","text":"Failed to load resource: the server responded with a status of 404 (Not Found)","timestamp":1538498227271.72,"url":"http://127.0.0.1:34583/b/s/w/ir/kitchen-workdir/infra/crdx/chopsui/test/chops-bug-input_test.html?wct=go"
When it should be looking for http://127.0.0.1:34583/test/chops-bug-input_test.html?wct=go instead.
Repro for local debugging here: https://chromium-review.googlesource.com/c/infra/infra/+/1258583
Comment 1 by benjhayden@chromium.org
, Aug 24