Seems like this happens when you have multiple layers of dependent diffs.

I think this test engine solves a real problem

Any changes in this vein need to wait for T5568 and be reframed on top of that.

Since many engines support common output formats (I think?) like XUnit (I think?) separating parsing might be valuable here, while it's not very useful for lint.

It looks like this is probably not a bug then, and D12211 is a fairly reasonable fix.

I think this is the reason: http://stackoverflow.com/a/9014547/90297

@epriestley - I was able to narrow it down to this:

This looks like a bug in Firefox to me, but I imagine reducing it to a test case is quite involved.

We don't provide support alpha/beta browsers. All bug reports should be against stable browsers and HEAD.

Windows 8.1 EN with Firefox Aurora 38. That said I've had this issue for the last 2-3 versions so it should happen on latest stable Firefox too. I can verify if you want.

Here: https://secure.phabricator.com/D12210#1753cdf4

This has been driving me and one of my colleagues crazy for a while now and he came with the following Stylish rule to get rid of it:

For our case, we use both arc lint and arc unit. We have a somewhat "smart" unit test engine that tries to run only affected tests up to a degree so test times are not a huge concern to us. Also the team I work with is ~10 people so there's no way we can go as high as 30 commits/hour, at least in the near future. We have a smooth CI system that is running tests both for each diff revision and every commit on master.

Any updates?

Apparently this is not gonna happen so abandoning.

@joshuaspence - it does accept input from stdin but it was not working for me for some reason and I was too quick to read the code missing the actual part that passed the input. Apparently it is something related to my own system. Thanks for the heads up tho :)

Ah, damn I missed $future->write($this->getEngine()->loadData($path)); and got confused. Welp then this is definitely not the correct change yeah.

I need to convince myself this is the best approach before I accept this. To do that, I need to research the answers to a lot of questions that I'm not very familiar with (like "Why doesn't node install binaries on Windows?"), reproduce the issue, etc.

Hello?

The UI shows skipped. Instead, it should just be omitted or show tailored messages that this is an update from the VCS. This is easy and just a display issue.