- User Since
- Sep 28 2016, 11:27 PM (42 w, 4 d)
Feb 13 2017
Feb 4 2017
Feb 3 2017
In our setup (as an open source project) we often get differentials created with base commits which do not exist in upstream. As a result using arc patch often fails, even worse, in a non-recoverable way as --reject is passed to git apply. In a patch fails to cleanly apply it is hard to continue the work-flow and manually correct the merge conflicts.
Jan 31 2017
Jan 25 2017
A short comment now. Thank you for the very detailed reply.
Jan 24 2017
Jan 23 2017
OK -- I made a new ec2 instance with the phabricator marketplace image to make the install easier. Updated to the latest stable and could still reproduce this. I don't know why the commit branches are saying that it is branched because I git reset --hard origin/stable on all the branches. I repeat -- this is a 100% fresh machine with the latest stable channel fetched from the phacility repos.
I will use a completely clean build tonight and reproduce this but the code hasn't changed since 2015.
This is documented in the userguide.
Jan 14 2017
Jan 13 2017
We are still occasionally running into this problem. A queuing system which ensures some kind of fairness would be really useful for us and others in the situation where demand is much greater than the builder resources. (A similar sentiment to T11153#180635)
Dec 28 2016
Thanks for these suggestions. We only had one CI machine so these kinds of concerns about parallelism are not important for us. I enabled the options that you suggested.
Dec 23 2016
Dec 22 2016
Dec 21 2016
Dec 18 2016
Nov 23 2016
Thanks for the lightning response!