http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=85999003
https://uberchromegw.corp.google.com/i/chromeos/builders/peppy-release/builds/2062

It appears that client targets are being run as server targets.  Failures also found on leon-release:

http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=86000271
leon-release/R56-8996.0.0/bvt-inline/build_RootFilesystemSize_SERVER_JOB

http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=85999003
peppy-release/R56-8996.0.0/bvt-inline/security_SandboxedServices_SERVER_JOB

The failed test for the OP Is http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=85999192

The server job that failed is https://uberchromeos-server38.corp.google.com/new_tko/#tab_id=test_detail_view&object_id=382258572


The failure log http://shortn/_cxH8G7cb5a is from the autoserv process that stages the test artifacts on the devserver and copies them onto the DUT so that the test can run on the DUT. This autoserv process runs for all tests (server/client).

This indeed looks like an infra failure. devserver replied with a corrupt message. I may not what's happening here.

The exact comment that failed was:
ssh 100.115.219.133 'curl "http://100.115.219.133:8082/stage?artifacts=autotest_packages&files=&async=True&archive_url=gs://chromeos-image-archive/peppy-release/R56-8996.0.0"'

I SSH'ed into that devserver and verified that this now works.
This was likely an short-term failures because I was updating the devserver (by mistake...).

Down to P2 to monitor any other fallout. To be closed tomorrow.

Observation time expired. I expect this to have disappeared.