On Tue, Apr 19, 2016 at 03:53:00PM +0100, Steve McIntyre wrote:
> On Mon, Apr 18, 2016 at 05:42:22AM +0300, Dmitry V. Levin wrote:
> >On Mon, Apr 18, 2016 at 12:09:55AM +0100, Steve McIntyre wrote:
> >> On Thu, Jan 14, 2016 at 02:31:01AM +, Steve McIntyre wrote:
> >> >
> >> >Coincidentally, I'v
On Mon, Apr 18, 2016 at 05:42:22AM +0300, Dmitry V. Levin wrote:
>On Mon, Apr 18, 2016 at 12:09:55AM +0100, Steve McIntyre wrote:
>> On Thu, Jan 14, 2016 at 02:31:01AM +, Steve McIntyre wrote:
>> >
>> >Coincidentally, I've just been doing exactly that already this
>> >evening. I'm in the middle
On Mon, Apr 18, 2016 at 12:09:55AM +0100, Steve McIntyre wrote:
> On Thu, Jan 14, 2016 at 02:31:01AM +, Steve McIntyre wrote:
> >
> >Coincidentally, I've just been doing exactly that already this
> >evening. I'm in the middle of hacking on a script to run tests
> >periodically on the various De
On Thu, Jan 14, 2016 at 02:31:01AM +, Steve McIntyre wrote:
>
>Coincidentally, I've just been doing exactly that already this
>evening. I'm in the middle of hacking on a script to run tests
>periodically on the various Debian porter boxes, so should be able to
>give you some better and more tim
On Thu, Jan 14, 2016 at 02:31:01AM +, Steve McIntyre wrote:
> On Thu, Jan 14, 2016 at 05:00:30AM +0300, Dmitry V. Levin wrote:
> >On Fri, Jan 08, 2016 at 05:33:08PM +, Steve McIntyre wrote:
> >[...]
> >> Thanks, that seems to work - all the tests pass now.
> >>
> >> 4.11-1 is in Debian inc
Hi,
On Fri, Jan 15, 2016 at 02:02:56AM +, Steve McIntyre wrote:
> On Thu, Jan 14, 2016 at 02:31:01AM +, Steve McIntyre wrote:
> >On Thu, Jan 14, 2016 at 05:00:30AM +0300, Dmitry V. Levin wrote:
> >>On Fri, Jan 08, 2016 at 05:33:08PM +, Steve McIntyre wrote:
> >>[...]
> >>> Thanks, that
On Thu, Jan 14, 2016 at 02:31:01AM +, Steve McIntyre wrote:
>On Thu, Jan 14, 2016 at 05:00:30AM +0300, Dmitry V. Levin wrote:
>>On Fri, Jan 08, 2016 at 05:33:08PM +, Steve McIntyre wrote:
>>[...]
>>> Thanks, that seems to work - all the tests pass now.
>>>
>>> 4.11-1 is in Debian incoming
On Thu, Jan 14, 2016 at 05:00:30AM +0300, Dmitry V. Levin wrote:
>On Fri, Jan 08, 2016 at 05:33:08PM +, Steve McIntyre wrote:
>[...]
>> Thanks, that seems to work - all the tests pass now.
>>
>> 4.11-1 is in Debian incoming right now with this as the only code
>> change on top of what was rele
On Fri, Jan 08, 2016 at 05:33:08PM +, Steve McIntyre wrote:
[...]
> Thanks, that seems to work - all the tests pass now.
>
> 4.11-1 is in Debian incoming right now with this as the only code
> change on top of what was released in 4.11.
According to https://buildd.debian.org/status/package.ph
On Fri, Jan 08, 2016 at 05:33:08PM +, Steve McIntyre wrote:
> On Fri, Jan 08, 2016 at 12:52:56AM +0300, Dmitry V. Levin wrote:
> >On Thu, Jan 07, 2016 at 01:49:08AM +, Steve McIntyre wrote:
[...]
> 4.11-1 is in Debian incoming right now with this as the only code
> change on top of what was
On Fri, Jan 08, 2016 at 12:52:56AM +0300, Dmitry V. Levin wrote:
>Hi,
>
>On Thu, Jan 07, 2016 at 01:49:08AM +, Steve McIntyre wrote:
>> Hey folks,
>>
>> I'm seeing this both in the 4.11 tarball (which I was just hoping to
>> push into Debian) and wuth current git HEAD. Everything builds fine
>
Hi,
On Thu, Jan 07, 2016 at 01:49:08AM +, Steve McIntyre wrote:
> Hey folks,
>
> I'm seeing this both in the 4.11 tarball (which I was just hoping to
> push into Debian) and wuth current git HEAD. Everything builds fine
> for me on amd64 and tests run for 64-bit fine, but in tests-32 I get a
Hey folks,
I'm seeing this both in the 4.11 tarball (which I was just hoping to
push into Debian) and wuth current git HEAD. Everything builds fine
for me on amd64 and tests run for 64-bit fine, but in tests-32 I get a
single failure for "times":
FAIL: times
===
1c1
< times({tms_utime=24
13 matches
Mail list logo
