Which port produces this build output?

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Which port produces this build output?

Christian Weisgerber
I see this splashed on my dpb window.  Apparently a port writes to
/dev/tty during the build.  Any idea which one?

 476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
 381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
  93 loops;       5s;   27261 Kstmts; 4778 Kst/sec

--
Christian "naddy" Weisgerber                          [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Jonathan Gray-11
On Fri, May 04, 2018 at 12:30:27PM +0200, Christian Weisgerber wrote:
> I see this splashed on my dpb window.  Apparently a port writes to
> /dev/tty during the build.  Any idea which one?
>
>  476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
>  381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
>   93 loops;       5s;   27261 Kstmts; 4778 Kst/sec

lang/snobol4 has

snobol4-2.0/test/bench.sno

OUTPUT(.TTY, IO_FINDUNIT(),, '/dev/tty')

...

        TTY = LPAD(LOOPS,4) ' loops; '
+               LPAD(TDISP,8) '; ' LPAD(st / 1000,7) ' Kstmts; '
+               SS  ' Kst/sec'

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Stuart Henderson
In reply to this post by Christian Weisgerber
On 2018/05/04 12:30, Christian Weisgerber wrote:

> I see this splashed on my dpb window.  Apparently a port writes to
> /dev/tty during the build.  Any idea which one?
>
>  476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
>  381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
>   93 loops;       5s;   27261 Kstmts; 4778 Kst/sec
>
> --
> Christian "naddy" Weisgerber                          [hidden email]
>

Probably snobol4.

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Solene Rapenne
In reply to this post by Christian Weisgerber

Christian Weisgerber writes:

> I see this splashed on my dpb window.  Apparently a port writes to
> /dev/tty during the build.  Any idea which one?
>
>  476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
>  381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
>   93 loops;       5s;   27261 Kstmts; 4778 Kst/sec

it's lang/snobol4

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Brian Callahan-3

On 05/04/18 06:45, Solene Rapenne wrote:

> Christian Weisgerber writes:
>
>> I see this splashed on my dpb window.  Apparently a port writes to
>> /dev/tty during the build.  Any idea which one?
>>
>>   476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
>>   381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
>>    93 loops;       5s;   27261 Kstmts; 4778 Kst/sec
> it's lang/snobol4
>
Fix looks like the attached.

~Brian


snobol4.diff (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Stuart Henderson
On 2018/05/04 11:09, Brian Callahan wrote:

>
> On 05/04/18 06:45, Solene Rapenne wrote:
> > Christian Weisgerber writes:
> >
> > > I see this splashed on my dpb window.  Apparently a port writes to
> > > /dev/tty during the build.  Any idea which one?
> > >
> > >   476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
> > >   381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
> > >    93 loops;       5s;   27261 Kstmts; 4778 Kst/sec
> > it's lang/snobol4
> >
>
> Fix looks like the attached.

Rather than patching build infra to avoid the test, would it be simpler
to use e.g. /dev/stderr instead of /dev/tty?

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Brian Callahan-3

On 05/04/18 12:46, Stuart Henderson wrote:

> On 2018/05/04 11:09, Brian Callahan wrote:
>> On 05/04/18 06:45, Solene Rapenne wrote:
>>> Christian Weisgerber writes:
>>>
>>>> I see this splashed on my dpb window.  Apparently a port writes to
>>>> /dev/tty during the build.  Any idea which one?
>>>>
>>>>    476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
>>>>    381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
>>>>     93 loops;       5s;   27261 Kstmts; 4778 Kst/sec
>>> it's lang/snobol4
>>>
>> Fix looks like the attached.
> Rather than patching build infra to avoid the test, would it be simpler
> to use e.g. /dev/stderr instead of /dev/tty?

In this case, I think no. There's no reason to run the tests during the
build. It just adds a forced minute of time to every build of snobol4.
We can still patch the test to use /dev/stderr instead of /dev/tty of
course.

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

John Long-4
On Fri, 2018-05-04 at 12:49 -0400, Brian Callahan wrote:

> On 05/04/18 12:46, Stuart Henderson wrote:
> > On 2018/05/04 11:09, Brian Callahan wrote:
> > > On 05/04/18 06:45, Solene Rapenne wrote:
> > > > Christian Weisgerber writes:
> > > >
> > > > > I see this splashed on my dpb window.  Apparently a port
> > > > > writes to
> > > > > /dev/tty during the build.  Any idea which one?
> > > > >
> > > > >    476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
> > > > >    381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
> > > > >     93 loops;       5s;   27261 Kstmts; 4778 Kst/sec
> > > >
> > > > it's lang/snobol4
> > > >
> > >
> > > Fix looks like the attached.
> >
> > Rather than patching build infra to avoid the test, would it be
> > simpler
> > to use e.g. /dev/stderr instead of /dev/tty?
>
> In this case, I think no. There's no reason to run the tests during
> the
> build. It just adds a forced minute of time to every build of
> snobol4.
> We can still patch the test to use /dev/stderr instead of /dev/tty
> of
> course.
>

The guy who wrote SNOBOL4 for *NIX collects timing reports from various
boxes and OS. So the timing report *can* be somewhat useful.

/jl

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Brian Callahan-3


On 5/5/2018 4:47 PM, John Long wrote:

> On Fri, 2018-05-04 at 12:49 -0400, Brian Callahan wrote:
>> On 05/04/18 12:46, Stuart Henderson wrote:
>>> On 2018/05/04 11:09, Brian Callahan wrote:
>>>> On 05/04/18 06:45, Solene Rapenne wrote:
>>>>> Christian Weisgerber writes:
>>>>>
>>>>>> I see this splashed on my dpb window.  Apparently a port
>>>>>> writes to
>>>>>> /dev/tty during the build.  Any idea which one?
>>>>>>
>>>>>>    476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
>>>>>>    381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
>>>>>>     93 loops;       5s;   27261 Kstmts; 4778 Kst/sec
>>>>> it's lang/snobol4
>>>>>
>>>> Fix looks like the attached.
>>> Rather than patching build infra to avoid the test, would it be
>>> simpler
>>> to use e.g. /dev/stderr instead of /dev/tty?
>> In this case, I think no. There's no reason to run the tests during
>> the
>> build. It just adds a forced minute of time to every build of
>> snobol4.
>> We can still patch the test to use /dev/stderr instead of /dev/tty
>> of
>> course.
>>
> The guy who wrote SNOBOL4 for *NIX collects timing reports from various
> boxes and OS. So the timing report *can* be somewhat useful.
>
> /jl
>

Yes I know. I've communicated with upstream and provided timing reports.
My crappy little netbook holds the world record for slowest amd64
machine he has a report for.

However, there's no point in having the package build machines run a
timing report each and every time they make new packages. If a user
wants to do it, fine. That's what `make test` is for.

~Brian

Reply | Threaded
Open this post in threaded view
|

Re: Which port produces this build output?

Stuart Henderson
On 2018/05/06 01:08, Brian Callahan wrote:

>
>
> On 5/5/2018 4:47 PM, John Long wrote:
> > On Fri, 2018-05-04 at 12:49 -0400, Brian Callahan wrote:
> >> On 05/04/18 12:46, Stuart Henderson wrote:
> >>> On 2018/05/04 11:09, Brian Callahan wrote:
> >>>> On 05/04/18 06:45, Solene Rapenne wrote:
> >>>>> Christian Weisgerber writes:
> >>>>>
> >>>>>> I see this splashed on my dpb window.  Apparently a port
> >>>>>> writes to
> >>>>>> /dev/tty during the build.  Any idea which one?
> >>>>>>
> >>>>>>    476 loops;      25s;  139520 Kstmts; 4894 Kst/sec
> >>>>>>    381 loops;      20s;  111675 Kstmts; 4891 Kst/sec
> >>>>>>     93 loops;       5s;   27261 Kstmts; 4778 Kst/sec
> >>>>> it's lang/snobol4
> >>>>>
> >>>> Fix looks like the attached.
> >>> Rather than patching build infra to avoid the test, would it be
> >>> simpler
> >>> to use e.g. /dev/stderr instead of /dev/tty?
> >> In this case, I think no. There's no reason to run the tests during
> >> the
> >> build. It just adds a forced minute of time to every build of
> >> snobol4.
> >> We can still patch the test to use /dev/stderr instead of /dev/tty
> >> of
> >> course.
> >>
> > The guy who wrote SNOBOL4 for *NIX collects timing reports from various
> > boxes and OS. So the timing report *can* be somewhat useful.
> >
> > /jl
> >
>
> Yes I know. I've communicated with upstream and provided timing reports.
> My crappy little netbook holds the world record for slowest amd64
> machine he has a report for.
>
> However, there's no point in having the package build machines run a
> timing report each and every time they make new packages. If a user
> wants to do it, fine. That's what `make test` is for.
>
> ~Brian
>

It might not be useful to do the timing run as part of a normal build,
but this is quite an intrusive patch to carry.. Do you think upstream
might accept something like that themselves? With the xsnobol4 target
it's clear there is meant to be a way to build without running tests so
perhaps it's an oversight that the install target depends on timing.out?