@epriestley: That's an awesome change, but now the list of subscribers is way more prominent than the assignee. Wouldn't it make more sense to put assignee (which is more important information IMO) before the list of subscribers?
Just a suggestion! Thanks for your awesome work 👍

Well, this sucks... But thank you for taking the time to explain the situation 😃

@epriestley Does this mean that phabricator isn't open to contributions?

I didn't even suggest dropping support, I'm merely listing the options to allow both versions to work.
We use a manually patched version of arcanist because it suits our company's use case, but it wouldn't be suitable for a merge in Phabricator's codebase in this state.

@DragonBe Backwards compatibility is broken by this fix. I'm not sure what the phabricator policy is regarding this, but I see two options:

• Creating another test engine (one for PHPUnit <= 5 and one for PHPUnit > 5)
• Parsing output differently depending on the PHPUnit version and reuse the old code where needed. This would require a little work to do things properly I guess.

Once I get an answer on how to submit it... See T12785

It would be perfect if the syntax supported in remarkup links could be used, which means that for @swisspol's example, projects/phabricator_transition/ would translate to https://temp.phacility.com/w/projects/phabricator_transition/.
And it would be even more awesome if the behavior of the displayed link in the "view" page could be the same, which means that in this case, it wouldn't display the link but the name of the Phriction page!

@cmmata here is my diff. It can probably be improved, but it works for me:

@epriestley I tried submitting a patch, but I get a Permission denied (publickey) which results in Unable to push changes to the staging area..
I added my public key and created a config rule to use it for requests to secure.phabricator.com, I'm not sure what else to do.

So, to recap:

• PhpunitTestEngine::run must be updated to use --log-junit which will output XML instead of JSON
• ArcanistPhpunitTestResultParser::parseTestResults must be updated to parse this XML file.

This seems simple enough, I will try to make it work.

Sorry, I should have led with a screenshot! I'm the biggest nitpicker, I know.

No they're not. I know it's a tiny difference, but look at this closely (left is my proposal, right is the current state):

And by doing that, I realize that I have been keeping up with master instead of stable like an (oh, there's no donkey emoji, too bad...).
So it's fixed... Sorry!

Sorry, it completely slipped my mind!

I have been updating the DB manually to set status back to 0 as a workaround for now. But you could probably see how this affects our workflow!

OK. But isn't it weird from an end-user POV to have unparsed remarkup there?
If it's a choice, you can close this issue! Thank you for your quick answer.

We tested this style (black with shadow) on our install, but the consensus is that it looks awful...
I guess a simple black text color is a little subtle, but at least it isn't confusing (like the blue color) or ugly (like the shadow).
@chad what do you think?

Thank you for the very thorough reply.
That's not a big deal and it certainly can wait!

Thank you for your quick reaction (and sorry that I didn't reply sooner). I think a black color with a 1px black text-shadow looks better. The blue is confusing (it sort of looks like a link).
So I suggest:

.phui-document-view .phabricator-remarkup .remarkup-header strong {
  color: #000000;
  text-shadow: 0 0 1px #000000;
}

Thank you for your quick reply. Indeed, this is tricky. Apparently, max-width has to be set on cells for overflow to work.