NightStrike wrote:
On Tue, Jan 10, 2023 at 9:30 PM Jacob Bachmeyer wrote:
NightStrike wrote:
[...]
I did another little test to try to better understand your point. I
ran a linux native testsuite under a simulator that just sets SIM to "
". This resulted in extra ^M's also, although
NightStrike wrote:
[...]
I did another little test to try to better understand your point. I
ran a linux native testsuite under a simulator that just sets SIM to "
". This resulted in extra ^M's also, although many tests pass because
they're already looking for \r\n to accommodate windows. So
NightStrike wrote:
On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer wrote:
NightStrike wrote:
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
[...]
So at least we know for sure that this particular instance of extra
characters is coming from Wine. Maybe Wine can be
NightStrike wrote:
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
NightStrike wrote:
[...]
Second, the problems with extra \r's still remain, but I think we've
generally come to think that that part isn't Wine and is instead
either the testsuite or deja. So I'll keep those
NightStrike wrote:
[...]
Second, the problems with extra \r's still remain, but I think we've
generally come to think that that part isn't Wine and is instead
either the testsuite or deja. So I'll keep those replies to Jacob's
previous message.
Most likely, it is a combination of the MinGW
NightStrike wrote:
On Sun, Dec 18, 2022 at 11:29 PM Jacob Bachmeyer wrote:
NightStrike wrote:
On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote:
[...]
This is either a testsuite problem or an environment problem. The GNU
Fortran I/O module certainly has interesting
NightStrike wrote:
On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote:
[...]
This is either a testsuite problem or an environment problem. The GNU
Fortran I/O module certainly has interesting behavior here. Try setting
TERM=dumb in the environment while running the testsuite. If that
NightStrike wrote:
On Sat, Dec 17, 2022 at 5:52 AM Thomas Koenig wrote:
On 17.12.22 01:26, NightStrike wrote:
On Fri, Dec 16, 2022 at 1:44 AM Thomas Koenig wrote:
On 16.12.22 03:20, NightStrike via Fortran wrote:
When I run the testsuite under wine, I'm getting a
Gavin Smith wrote:
On Mon, Oct 03, 2022 at 08:31:06AM +0100, Jonathan Wakely wrote:
On Mon, 3 Oct 2022 at 07:01, Gavin Smith via Gcc wrote:
On Sun, Oct 02, 2022 at 09:06:06PM -0400, Richard Stallman wrote:
[...]
The gcc developers need to provide a stable, version-independent
[previous Subject: Re: dejagnu version update? [CORRECTION: not a
regression in DejaGnu; GDB testsuite bug] ]
[adding Tom Tromey to CC list per advice from Rob Savoye]
[adding main DejaGnu mailing list to CC list]
In brief for those new to this, the GDB testsuite is currently broken
when run
Jacob Bachmeyer wrote:
Maciej W. Rozycki wrote:
[...]
I ran a quick bisection and the culprit turned out to be:
ba60272a5ac6f6a7012acca03f596a6ed003f044 is the first bad commit
commit ba60272a5ac6f6a7012acca03f596a6ed003f044
Author: Jacob Bachmeyer
Date: Mon May 25 08:40:46 2020 -0600
Maciej W. Rozycki wrote:
On Tue, 26 May 2020, Rob Savoye wrote:
I'll run some RISC-V remote GCC/GDB testing and compare results for
DejaGnu 1.6/1.6.1 vs trunk. It will take several days though, as it takes
many hours to go through these testsuite runs.
That'd be great. I'd
Rob Savoye wrote:
On 5/14/20 10:08 AM, David Edelsohn wrote:
Have you approached the Linux Foundation Core Infrastructure
Initiative for funding for both DejaGNU maintenance (patch backlog)
and refactoring DejaGNU in Python efforts?
Not that team, the folks I talked to thought I was
13 matches
Mail list logo
