That's sensible to me. Was just an unexpected side effect of improving the arc land workflow for git and thought I'd mention it.
Dec 3 2015
Dec 2 2015
On this issue, it would be great to tune the behavior regarding "Author date" vs "Commit date" for git. With our current CI tool, current build and previous build are determined in "Commit date" order not "Author Date', which can result in confusing links.
Dec 1 2015
Nov 12 2014
Oct 16 2014
Sep 15 2014
Aug 27 2014
I think I run this Test Plan at least daily, minus the unit tests
Aug 23 2014
I missed this little bit when moving to local disk file storage, which has write permissions for the user running the web server (www-data) and then the GarbageCollectorDaemon emitted:
errors, even though I had read this page, and found and set the phd.user setting to www-data on my own.
Aug 22 2014
Awesome. Here's trace output without --dry-run https://secure.phabricator.com/P1246
looks like this will help, test ran with ./bin/files compact --all --dry-run --trace
Aug 21 2014
Can confirm D10333 fixes for me
Also seeing this on a different, private repo. It is on windows.
Aug 20 2014
Aug 19 2014
Aug 14 2014
Aug 13 2014
Awesome! Can you arc patch D9375 locally and see if:
- rendering looks reasonable
I can test Outlook (Windows) rendering
Jun 27 2014
This sometimes works for me. It seems like sometimes commits get hung importing so revisions are never closed for those commits. Especially seems to be the case with encoding issues.
Jun 26 2014
just to followup: differential.generated-paths works great.
I'm in a similar scenario, t4 templates for codegen in visual studio often have <auto-generated /> somewhere in them. It'd be nice to have this string configurable so we don't need to have comments like this everywhere:
// <auto-generated /> // @generated
Jun 11 2014
Tested and works for me on the changeset that was displaying this issue. It did prompt to mark 2 of the files in the diff as binary, but allowed the revision to be posted.