Switching branches in the engine invalidates builds (RBE?) about flutter HOT 7 OPEN

Hmm this is an interesting one.

Can I assume this used to WAI with pre-et workflows?

from flutter.

Pre-et for me was goma. This is possibly an rbe vs goma thing. I wanted to mention it since I saw it on the chance there was something that rang a bell for people familiar with the et codebase.

from flutter.

If you try --no-rbe, what happens?

from flutter.

If you try --no-rbe, what happens?

That would take a long time to try =T.

I'm not even sure how one would get this behavior since RBE and et should know nothing about the reset. Maybe the modification time on the files is getting changed when switching branches? So even though I ended up in the same state, the files modification time was updated which triggered them to have to be recompiled.

I think if there is nothing in et that is caching some git internals or file timestamps we can close this. I'm not sure if it will come up a lot, but we can reopen it if we do see it. If it is the timestamp problem, there's nothing we could do to fix it =T

from flutter.

I think this is worth re-opening, in the context of improving the engine (even if the fix is not in et).

from flutter.

@zanderso Is it worth tracking RBE-specific productivity issues under engine-tool? Is e: rbe a thing?

from flutter.

There's no e: rbe right now afaik, but we can add one.

from flutter.