Raising the importance of this-

We've slowed down the integration of Blink rolls as we switch to being based on the beta branch. We should have a way to stay on top of dev/canary.

Added this to the M7 milestone.
Removed Priority-Unassigned label.
Added Priority-High label.

I think we should go in another direction.

I think we should tests dart2js on something more stable, i.e., chrome beta, and I think we should test it in browser, not using content shell. I still see the need for this (and for testing dart2js on dartium)

Here is my proposal:
Main waterfall dart2js drt builders are exchanged with chrome beta builders
On fyi we have
  dart2js running on dartium TOT
  dart2js running on chrome dev channel, with autoupdate enabled.
 

+1 on chrome dev channel. It'd be nice if a switch to a new dev version showed up as a separate line on the Dart build bot, so we can easily see whether breakage was due to upstream changes. Is that doable?

dartium TOT will be behind chrome dev and beta, so it won't add much value to run dart2js tests there. Or are you suggesting for its content shell?

Any reason the dart2js chrome dev channel on FYI?

I do like having some main bots on dev channel as it lets us see what is coming before it's too late (assuming many of our developers are on beta channel).

I have not seen much difference between content_shell and chrome other than test execution speed (and a few things such as rAF). I definitely prefer content_shell for local testing but either should be sufficient on the bots.

The reason for dart2js chrome dev channel should go to FYI is this:
If we have it auto update it will show up an error on a random persons commit.

We do have a way to eliminate this, but that require us to roll chrome manually (which is probably fine). If that is the case we can have dev channel on the main waterfall.

We can script up the rolling. Basically we would store the binaries in gcs and fetch them based on a config file that we keep in the dart repo - to roll: upload the new version to gsc and update the config file in the dart repo. There is no easy way for us to get separate lines in the waterfall without doing it this way.

Removed this from the M7 milestone.
Added this to the Later milestone.
Removed Priority-High, Area-Test labels.
Added Priority-Low, Area-Infrastructure labels.

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

Removed Oldschool-Milestone-Later label.

We are no longer using content shell.