Rico Wind

Results 5 comments of Rico Wind

Running the persistent compiler twice on the same code will give good warnings only the first time

also @sigurdm @karlklose may know something about this

Running the persistent compiler twice on the same code will give good warnings only the first time

I have "incremental_mode": "none" in my .fletch-settings file in my checkout, but I still see this error

Running the persistent compiler twice on the same code will give good warnings only the first time

ok, so that prints: ``` ~/src/fletch/fletch/out/DebugX64/fletch show log [local: 2015-12-17 12:49:40.712 created session with settings Settings(packages: file:///usr/local/google/home/ricow/src/fletch/fletch/.packages, options: [], constants: {}, device_address: null, device_type: DeviceType.mobile, incremental_mode: IncrementalMode.production)] [local: 2015-12-17 12:49:43.182...

Add unit test to verify fletch quit's graceful shutdown works.

If we made the driver capable of taking something similar to chrome/drt --user-data-dir then we could test all kind of stuff regarding the persistent process/driver shutdown sequence/failure scenarios (maybe this...

Add unit test to verify fletch quit's graceful shutdown works.

That should work as well, we then just need to cat /proc/PID/environ in the taskkill script to make sure that we know that file for a process that we kill...