nyan_blaze-release hasn't succeeded since May 5 and always fails with the dummy_PassServer test. The logs look somewhat like this:

05/12 04:57:09.361 DEBUG|    connectionpool:0362| "POST /cautotest/container_create HTTP/1.1" 201 114
05/12 04:57:09.361 INFO |              base:0063| POST http://172.25.66.62:9800/cautotest/container_create [status:201 request:0.018s]
05/12 04:57:09.361 DEBUG|              base:0065| > {"drone": "chromeos-server42.cbf.corp.google.com", "job_id": 117088206, "success": false, "time_recorded": 1494590229.343078}
05/12 04:57:09.361 DEBUG|              base:0066| < {"_index":"cautotest_2016_09","_type":"container_create","_id":"AVv8hQtipdQHjru4eWBU","_version":1,"created":true}
05/12 04:57:09.363 INFO |        server_job:0184| FAIL	----	----	timestamp=1494590229	localtime=May 12 04:57:09	Failed to setup container for test: Command <sudo lxc-start -P /usr/local/autotest/containers -n test_117088206_1494590191_26285 -d> failed, rc=1, Command returned non-zero exit status
  * Command: 
      sudo lxc-start -P /usr/local/autotest/containers -n
      test_117088206_1494590191_26285 -d
  Exit status: 1
  Duration: 5.77087211609
  
  stderr:
  lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.. Check logs in ssp_logs folder for more details.

(This *is* the log from ssp_logs, so that's all the details we have, apparently.) This test seems to be related to some lab infra feature called "server side packaging". I've asked a couple of kernel engineers working on containers over lunch and they all said that lxc is essentially cancer and should never be used by anyone, much less on a nyan_blaze. So no idea what this is trying to do here and why.

The last successful run (http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=116017548) doesn't seem to run dummy_PassServer at all anymore, but the only patch in the diff between that (9526.0.0) and the first failed run (9527.0.0) is https://chromium-review.googlesource.com/c/497907/ which seems to be unrelated. I have no idea how this test magically appeared in this suite.