Great. Actually there is a latent bug in there we hit yesterday, when
there is a platform set but it doesn't start with "remote-" (we assume the
match result has a first matched group and blow up). I'll submit a patch
that both fixes that up and strips out the darwin ones. I think the rerun
logi
Hi,
I have removed all of our expected timeouts from dosep.py (there are
still some freebsd and darwin ones left, but I don't know If anyone is
looking at those), so I think we're not using any part of the old test
runner at the moment. All clear for removal on our part.
pl
On 14 December 2015
Oh yeah, that's fine. I won't take that code out.
Hmm at least some of the builds went through this weekend, I made a number
of changes Saturday morning (US Pacific time) that I saw go through the
Ubuntu 14.04 cmake bot.
On Mon, Dec 14, 2015 at 6:29 AM, Pavel Labath wrote:
> Hi,
>
> we've had
Hi,
we've had an unrelated breaking change, so the buildbots were red over
the weekend. I've fixed it now, and it seems to be turning green.
We've also had power outage during the weekend and not all of the
buildbots are back up yet, as we need to wait for MTV to wake up. I'd
like to give this at
Hey Pavel and/or Tamas,
Let me know when we're definitely all clear on the expected timeout support
I added to the (now once again) newer default test results.
As soon as we don't need the legacy summary results anymore, I'm going to
strip out the code that manages it. It is quite messy and dupl
I went ahead and added the expected timeout support in r255363.
I'm going to turn back on the new BasicResultsFormatter as the default. We
can flip this back off if it is still not doing everything we need, but I
*think* we cover the issue you saw now.
-Todd
On Fri, Dec 11, 2015 at 10:14 AM, To
