Can you please enhance the scheduling server/test executor to prevent compile time collision.

I've run into a situation where I have a test executor that runs tests frequently, so it is compiling the pages.g.cs file each time.  Well I sometimes go in and request for a test to be run remotely against that same executor - expecting that it knows when its busy and will get to my request when it can.  ...and boom.  The requests crash into each other and the executor gets a compile error in the pages.g.cs file.

Frustrating.  You should see about enhancing this so that the executor taking commands from multiple points (the scheduler, or the developer's box) don't collide.