Verify Sponge record in test push |
||
Issue descriptionLab recently had a long period of missing Sponge results due to several bugs (tracked in bug 701948). It's critical to verify Sponge results can be successfully created in the lab. Test push run could be a good place to verify Sponge is still working after push.
,
Apr 4 2017
To check if the sponge record is created. We store the sponge record url in tko_test_attributes. So the verify code only need to retrieve that url and try to see if it can be resolved. One trick is that Sponge is on google3, might need sso to access it. A workaround for that can be using Sponge HTTP API (go/sponge-http-api). Some sample code can be found in project chromeos/autotest-private-utils (https://chrome-internal.googlesource.com/chromeos/autotest-private-utils/+/master). We can add a method in sponge/upload_utils.py like find_record(id), and test push can use that to check if a record exists.
,
Mar 14 2018
This bug is very old, is Untriaged, and has no owner. If it is still relevant, reopen as Untriaged or open a new bug |
||
►
Sign in to add a comment |
||
Comment 1 by aut...@google.com
, Apr 4 2017