Three devservers fail to curl the android artifact when push finished |
|||
Issue descriptionThree devservers are: chromeos1-infra-devserver4.cros.corp.google.com, chromeos1-infra-devserver5.cros.corp.google.com, chromeos1-infra-devserver7.cros.corp.google.com Example: chromeos-test@chromeos1-infra-devserver5:~$ curl "http://localhost:8082/stage?build_id=2457013&files=&target=shamu-userdebug&artifacts=bootloader_image,zip_images,test_zip&branch=git_mnc-release&os_type=android" The command just hangs there forever
,
Feb 14 2018
Who owns? I actually don't know which devserver we own?
,
Feb 14 2018
I tried your commands and it works for me chromeos-test@chromeos1-infra-devserver5:/var/log/devserver$ time curl "http://localhost:8082/stage?build_id=2457013&files=&target=shamu-userdebug&artifacts=bootloader_image,zip_images,test_zip&branch=git_mnc-release&os_type=android" Success real 0m0.058s user 0m0.000s sys 0m0.004s
,
Feb 14 2018
hmm, interesting, maybe the time I ran the command the devserver was experiencing some issues?
,
Feb 20 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dgarr...@chromium.org
, Feb 14 2018