GNU bug report logs - #71624
dejagnu-1.6.3 test failure

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 71624 in the body.
You can then email your comments to 71624 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gordon Steemson <gsteemso <at> gmail.com>
To: bug-dejagnu <at> gnu.org
Subject: Re: dejagnu-1.6.3 test failure
Date: Mon, 17 Jun 2024 14:26:33 -0700

I have tried Adam Sampson's patch for Expect 5.45.4, but unfortunately it did not solve this problem for me.  Neither did building in a different directory -- whether a subdirectory of the source directory or outside it entirely, on my system it always fails the report-card tests with these same sorts of unexpectedly closed subprocess files.

Message #8 received at 71624 <at> debbugs.gnu.org (full text, mbox):

From: Jacob Bachmeyer <jcb62281 <at> gmail.com>
To: Gordon Steemson <gsteemso <at> gmail.com>
Cc: 71624 <at> debbugs.gnu.org
Subject: Re: bug#71624: dejagnu-1.6.3 test failure
Date: Tue, 18 Jun 2024 21:09:17 -0500

Gordon Steemson wrote:
> I have tried Adam Sampson's patch for Expect 5.45.4, but unfortunately it did not solve this problem for me.  Neither did building in a different directory -- whether a subdirectory of the source directory or outside it entirely, on my system it always fails the report-card tests with these same sorts of unexpectedly closed subprocess files.
>   

This is a different issue than the Expect bug that patch is intended to 
fix.  The spurious EOF bug in Expect only affects the internal DejaGnu 
unit tests, which are run in a child expect process.

The report-card tests should not be affected by that issue, however, 
this report contains insufficient information to evaluate.  Please 
attach the report-card.log produced by a failing test run and describe 
the system that you are using.  What distribution is exhibiting this issue?


-- Jacob

Message #11 received at 71624 <at> debbugs.gnu.org (full text, mbox):

From: Gordon Steemson <gsteemso <at> gmail.com>
To: jcb62281 <at> gmail.com
Cc: 71624 <at> debbugs.gnu.org
Subject: Re: bug#71624: dejagnu-1.6.3 test failure
Date: Wed, 19 Jun 2024 14:48:41 -0700

[Message part 1 (text/plain, inline)]

On Tue, 18 Jun 2024 at 19:09, Jacob Bachmeyer <jcb62281 <at> gmail.com> wrote:
> Gordon Steemson wrote:
> > I have tried Adam Sampson's patch for Expect 5.45.4, but unfortunately it did not solve this problem for me.  Neither did building in a different directory -- whether a subdirectory of the source directory or outside it entirely, on my system it always fails the report-card tests with these same sorts of unexpectedly closed subprocess files.
>
> This is a different issue than the Expect bug that patch is intended to
> fix.  The spurious EOF bug in Expect only affects the internal DejaGnu
> unit tests, which are run in a child expect process.

Oh. I must have mis-read that part. My apologies.

> The report-card tests should not be affected by that issue, however,
> this report contains insufficient information to evaluate.  Please
> attach the report-card.log produced by a failing test run and describe
> the system that you are using.  What distribution is exhibiting this issue?

The test log should be attached to this message; hopefully it does not
get stripped off.

The build was performed on an obsolete platform – specifically, Mac OS
X 10.5.8 “Leopard” running on a dual-processor Power Mac G5 – so I
don’t know if anyone else will care that it failed.  I’d still like to
know why it is failing.

Gordon S.

[report-card.log (application/octet-stream, attachment)]

Message #14 received at 71624 <at> debbugs.gnu.org (full text, mbox):

From: Jacob Bachmeyer <jcb62281 <at> gmail.com>
To: Gordon Steemson <gsteemso <at> gmail.com>
Cc: 71624 <at> debbugs.gnu.org
Subject: Re: bug#71624: dejagnu-1.6.3 test failure
Date: Wed, 19 Jun 2024 22:00:49 -0500

Gordon Steemson wrote:
> On Tue, 18 Jun 2024 at 19:09, Jacob Bachmeyer <jcb62281 <at> gmail.com> wrote:
>   
> [...]
>> The report-card tests should not be affected by that issue, however,
>> this report contains insufficient information to evaluate.  Please
>> attach the report-card.log produced by a failing test run and describe
>> the system that you are using.  What distribution is exhibiting this issue?
>>     
>
> The test log should be attached to this message; hopefully it does not
> get stripped off.
>
> The build was performed on an obsolete platform – specifically, Mac OS
> X 10.5.8 “Leopard” running on a dual-processor Power Mac G5 – so I
> don’t know if anyone else will care that it failed.  I’d still like to
> know why it is failing.
>   

It is most likely failing because Mac OS X 10.5.8 does not conform to 
POSIX:  the log shows an error from stty(1) rejecting the -onlret 
option, which POSIX defines---it is /not/ a GNU extension.

That said, my copy of stty(P) suggests that onlret does not do anything 
useful here, so a patch has been pushed to the "PR71624" branch at 
Savannah.  Please try it and indicate if it solves this problem.  If so, 
I will merge it to master and consider the issue resolved.


-- Jacob

Message #17 received at 71624 <at> debbugs.gnu.org (full text, mbox):

From: Gordon Steemson <gsteemso <at> gmail.com>
To: jcb62281 <at> gmail.com
Cc: 71624 <at> debbugs.gnu.org
Subject: Re: bug#71624: dejagnu-1.6.3 test failure
Date: Thu, 20 Jun 2024 22:04:39 -0700

Hello,

> On Jun 19, 2024, at 8:00 PM, Jacob Bachmeyer <jcb62281 <at> gmail.com> wrote:
> 
> Gordon Steemson wrote:
>> On Tue, 18 Jun 2024 at 19:09, Jacob Bachmeyer <jcb62281 <at> gmail.com> wrote:
>>  [...]
>>> The report-card tests should not be affected by that issue, however,
>>> this report contains insufficient information to evaluate.  Please
>>> attach the report-card.log produced by a failing test run and describe
>>> the system that you are using.  What distribution is exhibiting this issue?
>>>    
>> 
>> The test log should be attached to this message; hopefully it does not
>> get stripped off.
>> 
>> The build was performed on an obsolete platform – specifically, Mac OS
>> X 10.5.8 “Leopard” running on a dual-processor Power Mac G5 – so I
>> don’t know if anyone else will care that it failed.  I’d still like to
>> know why it is failing.
>>  
> 
> It is most likely failing because Mac OS X 10.5.8 does not conform to POSIX:  the log shows an error from stty(1) rejecting the -onlret option, which POSIX defines---it is /not/ a GNU extension.
> 
> That said, my copy of stty(P) suggests that onlret does not do anything useful here, so a patch has been pushed to the "PR71624" branch at Savannah.  Please try it and indicate if it solves this problem.  If so, I will merge it to master and consider the issue resolved.

That did indeed fix it!  I thank you most sincerely for taking the time to look into this.

With gratitude,
Gordon S.

Message #22 received at 71624-done <at> debbugs.gnu.org (full text, mbox):

From: Jacob Bachmeyer <jcb62281 <at> gmail.com>
To: Gordon Steemson <gsteemso <at> gmail.com>
Cc: 71624-done <at> debbugs.gnu.org
Subject: Re: bug#71624: dejagnu-1.6.3 test failure
Date: Fri, 21 Jun 2024 21:48:19 -0500

Gordon Steemson wrote:
> Hello,
>
>   
>> On Jun 19, 2024, at 8:00 PM, Jacob Bachmeyer <jcb62281 <at> gmail.com> wrote:
>>
>> Gordon Steemson wrote:
>>     
>>> On Tue, 18 Jun 2024 at 19:09, Jacob Bachmeyer <jcb62281 <at> gmail.com> wrote:
>>>  [...]
>>>       
>>>> The report-card tests should not be affected by that issue, however,
>>>> this report contains insufficient information to evaluate.  Please
>>>> attach the report-card.log produced by a failing test run and describe
>>>> the system that you are using.  What distribution is exhibiting this issue?
>>>>    
>>>>         
>>> The test log should be attached to this message; hopefully it does not
>>> get stripped off.
>>>
>>> The build was performed on an obsolete platform – specifically, Mac OS
>>> X 10.5.8 “Leopard” running on a dual-processor Power Mac G5 – so I
>>> don’t know if anyone else will care that it failed.  I’d still like to
>>> know why it is failing.
>>>  
>>>       
>> It is most likely failing because Mac OS X 10.5.8 does not conform to POSIX:  the log shows an error from stty(1) rejecting the -onlret option, which POSIX defines---it is /not/ a GNU extension.
>>
>> That said, my copy of stty(P) suggests that onlret does not do anything useful here, so a patch has been pushed to the "PR71624" branch at Savannah.  Please try it and indicate if it solves this problem.  If so, I will merge it to master and consider the issue resolved.
>>     
>
> That did indeed fix it!  I thank you most sincerely for taking the time to look into this.
>
> With gratitude,
> Gordon S.
>   

Thank you for the quick response.

-- Jacob

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.