Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 1 user
Status: Archived
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment
devserver(s?) responding with corrupt messages for staging request in case of success
Project Member Reported by skau@chromium.org, Nov 17 2016 Back to list
peppy-release seems to be trying to run client tests as server tests.  I'm investigating.

peppy-release/R56-8996.0.0/bvt-inline/login_RetrieveActiveSessions_SERVER_JOB	FAIL	1	staging artifacts=autotest_packages files= for peppy-release/R56-8996.0.0 failed;HTTP OK not accompanied by 'Success'.
peppy-release/R56-8996.0.0/bvt-inline/security_Minijail0_SERVER_JOB	FAIL	1	staging artifacts=autotest_packages files= for peppy-release/R56-8996.0.0 failed;HTTP OK not accompanied by 'Success'.
peppy-release/R56-8996.0.0/bvt-inline/security_mprotect_SERVER_JOB	FAIL	1	staging artifacts=autotest_packages files= for peppy-release/R56-8996.0.0 failed;HTTP OK not accompanied by 'Success'.
peppy-release/R56-8996.0.0/bvt-inline/security_SandboxedServices_SERVER_JOB	FAIL	1	staging artifacts=autotest_packages files= for peppy-release/R56-8996.0.0 failed;HTTP OK not accompanied by 'Success'.
 
Comment 2 by skau@chromium.org, Nov 17 2016
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
Comment 3 by skau@chromium.org, Nov 17 2016
Cc: pprabhu@chromium.org
Cc: -pprabhu@chromium.org
Labels: -Pri-3 Pri-1
Owner: pprabhu@chromium.org
Status: Started
Summary: devserver(s?) responding with corrupt messages for staging request in case of success (was: peppy-release running client tests as server tests)
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.
Labels: -Pri-1 Pri-2
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.
Components: Infra>Client>Chrome
Status: Fixed
Observation time expired. I expect this to have disappeared.
Comment 8 by dchan@google.com, Mar 4 2017
Labels: VerifyIn-58
Labels: VerifyIn-59
Labels: VerifyIn-60
Labels: VerifyIn-61
Comment 12 by dchan@chromium.org, Oct 14 (3 days ago)
Status: Archived
Sign in to add a comment