5482e85112
The vm build is incremental, and on bleeding edge the revision number is part of the version number. So if a cl lands that triggers a rebuild of the api docs - but not of the vm, the check for vmVersion.startsWith(version) will report false. This is exactly what happened here: http://build.chromium.org/p/client.dart/builders/analyzer_experimental-linux-release-be/builds/400 The change from sgjesse@ : https://code.google.com/p/dart/source/detail?r=41821 Triggered a rebuild of the api docs, but the vm remained unchanged with a version of: 1.8.0-edge.41820 The version of the build was: 1.8.0-edge.41821 Review URL: https://codereview.chromium.org//736923002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@41824 260f80e4-7a28-3924-810f-c04153c831b5