btw, another improvement would be precise time information, i.e. incl. the
time zone.
Also they should be consistent. It seems to me like
http://d.puremagic.com/test-results/pulls.ghtml uses a different time than
a single result like
http://d.puremagic.com/test-results/pull.ghtml?runid=4722
On 1/29/2012 10:13 PM, Daniel Murphy wrote:
> "Brad Roberts" wrote in message
> news:mailman.182.1327902075.25230.digitalmar...@puremagic.com...
>> Yes. It's a way for request to be prioritized higher. A pull that's
>> receiving comments is much more likely to be
>> pulled than one that isn't,
"Brad Roberts" wrote in message
news:mailman.182.1327902075.25230.digitalmar...@puremagic.com...
> Yes. It's a way for request to be prioritized higher. A pull that's
> receiving comments is much more likely to be
> pulled than one that isn't, so might as well test it sooner.
Makes sense.
Th
On 1/29/2012 8:32 PM, Daniel Murphy wrote:
> On as side note, the pull tester sorts by what time the pull request was
> modified, not when the most recent commit was. Is this intentional?
>
Yes. It's a way for request to be prioritized higher. A pull that's receiving
comments is much more l
On as side note, the pull tester sorts by what time the pull request was
modified, not when the most recent commit was. Is this intentional?
My current thinking is that I'll first write a
greasemonkey script that integrates the tester results into github so
that there's visibility of the current state
along-side the pull itself.
Sounds promising.
It's a security measure to avoid building just any random bit of code
that happens
On 1/29/2012 7:00 PM, Trass3r wrote:
> http://d.puremagic.com/test-results/pulls.ghtml
>
> I've seen several suggestions in an older thread to improve the tester like
> posting notifications about failing tests to
> the corresponding pull request.
> Any plans for that?
Plans, yes. I haven't dec
http://d.puremagic.com/test-results/pulls.ghtml
I've seen several suggestions in an older thread to improve the tester
like posting notifications about failing tests to the corresponding pull
request.
Any plans for that?
Also why aren't all pull requests tested there?
