Hmm, not sure where to move this. Slapping somewhat related components on.

(And it looks like cros' current_reldate has now jumped to 12/08/17)

There appears to be a parsing exception when fetching the cros version data (although I think the exception must be getting swallowed somewhere in the code, because I don't see any obvious errors in the project console). CL on the way.

This is a longstanding issue at the moment. The problem is that cros-omahaproxy is serving invalid CSV.

Internal discussion: https://groups.google.com/a/google.com/forum/#!topic/chrome-pmo/yTV7h6j3EKE

Ah, thanks, I wasn't aware of that discussion, but came to the same conclusion after adding some tests for the cros version code. Sent you a CL.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/7c3389ed0179f8a2b04a8f8eab1d45847f5d3aba

commit 7c3389ed0179f8a2b04a8f8eab1d45847f5d3aba
Author: Michael Moss <mmoss@google.com>
Date: Thu Jan 25 22:13:05 2018

It looks better now:

os	channel	current_version	previous_version	current_reldate
cros	dev	65.0.3325.9	64.0.3282.11	01/25/18
cros	beta	64.0.3282.110	63.0.3239.70	01/25/18
cros	stable	63.0.3239.140	62.0.3202.97	01/25/18