Andy Nicholson

Results 4 comments of Andy Nicholson

Confirming this behaviour is still present in `3.16.0` after standing up a development rack based off #748.

This bit me today, too. I wondered why my tasks weren't launching and I'm pretty sure this is the reason. EDIT: Yep, confirmed that the provider created an x86 task...