From: NightStrike <nightstrike@gmail.com>
To: Jacek Caban <jacek@codeweavers.com>
Cc: jcb62281@gmail.com, Eric Pouech <eric.pouech@orange.fr>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
DejaGnu mailing list <dejagnu@gnu.org>
Subject: Re: testsuite under wine
Date: Sat, 14 Jan 2023 18:36:26 -0500 [thread overview]
Message-ID: <CAF1jjLuvDBp-z_GgLQohv2tm66R2Vz=xNE7MUVEgYGvdX4RcKA@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLtM6QDKrauOr=ypNT+vc0u_OBzZwKk5Y8-RbYyzuuNL2Q@mail.gmail.com>
On Wed, Jan 11, 2023 at 1:41 PM NightStrike <nightstrike@gmail.com> wrote:
>
>
>
> On Tue, Jan 10, 2023, 04:19 NightStrike <nightstrike@gmail.com> wrote:
>>
>> On Mon, Jan 9, 2023 at 11:05 AM Jacek Caban <jacek@codeweavers.com> wrote:
>> > Sure, I'd be interested how well my latest patch works for NightStrike.
>> > It should give us overview about how much conhost interferes with test
>> > results in practice when we get easy stuff out of the way.
>>
>> Generally, more tests run and pass, but most still fail for different
>> reasons. IOW, the cursor hiding escapes are gone, but the EOLs still
>> don't match until we modify the tests themselves.
>
>
> Quick update that I found more tests that fail with what I assume are Wine escape codes, K and C. (Ie ^[[K). I can't figure out under what context they appear, and I don't know what they are for.
With Jacek's latest patch:
__________________________________________________
/ PASS FAIL ?PASS ?FAIL UNSUP UNRES UNTEST
|--------------------------------------------------
acats | 0 0 0 0 0 0 0
gcc | 164293 1652 6 1150 3213 810 0 !E! !W!
gdc | 4167 1658 0 0 1553 121 0
gfortran | 66811 210 8 257 247 0 0 !W!
gm2 | 1168 6673 0 0 0 2065 0
gnat | 3360 24 0 23 14 0 0 !W!
g++ | 226182 1314 4 2346 10900 89 0 !E! !W!
libatomic | 53 1 0 0 0 0 0 !W!
libstdc++ | 14563 50 26 74 835 1 0 !W!
obj-c++ | 1502 8 1 1 79 0 0 !W!
objc | 1882 9 0 6 70 10 0 !E!
rust | 4148 432 0 39 0 0 0 !W!
|--------------------------------------------------
| 488129 12031 45 3896 16911 3096 0
\__________________________________________________
We're making good progress here!
(Note that the numbers above for rust are for the gcc master branch,
but every line ending failure is fixed on the rust dev branch, leaving
only 1 actual bug)
next prev parent reply other threads:[~2023-01-14 23:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 2:20 NightStrike
2022-12-16 6:44 ` Thomas Koenig
2022-12-17 0:26 ` NightStrike
2022-12-17 10:52 ` Thomas Koenig
2022-12-17 23:24 ` NightStrike
2022-12-18 3:44 ` Jacob Bachmeyer
2022-12-18 21:13 ` NightStrike
2022-12-19 4:29 ` Jacob Bachmeyer
2022-12-19 10:43 ` Torbjorn SVENSSON
2022-12-19 11:00 ` NightStrike
2022-12-19 11:13 ` NightStrike
2022-12-20 3:51 ` Jacob Bachmeyer
2022-12-21 17:37 ` Jacek Caban
2022-12-22 1:01 ` NightStrike
2022-12-22 4:37 ` Jacob Bachmeyer
2022-12-23 10:36 ` NightStrike
2022-12-23 12:43 ` Eric Pouech
2022-12-24 4:00 ` Jacob Bachmeyer
2022-12-24 11:05 ` Mark Wielaard
2023-01-05 2:50 ` NightStrike
2023-01-06 3:33 ` Jacob Bachmeyer
2023-01-06 3:44 ` Jerry D
2023-01-08 7:12 ` NightStrike
2023-01-11 2:30 ` Jacob Bachmeyer
2023-01-11 9:33 ` NightStrike
2023-01-12 4:11 ` Jacob Bachmeyer
2023-01-06 3:41 ` Jerry D
2022-12-22 4:16 ` Jacob Bachmeyer
2022-12-22 8:40 ` Eric Pouech
2022-12-23 3:51 ` Jacob Bachmeyer
2022-12-23 23:32 ` Jacek Caban
2022-12-24 5:33 ` Jacob Bachmeyer
2023-01-07 1:45 ` Jacek Caban
2023-01-07 3:58 ` Jacob Bachmeyer
2023-01-09 16:03 ` Jacek Caban
2023-01-10 9:19 ` NightStrike
2023-01-11 9:10 ` NightStrike
2023-01-11 18:41 ` NightStrike
2023-01-14 23:36 ` NightStrike [this message]
2023-01-11 2:44 ` Jacob Bachmeyer
2023-01-08 6:47 ` NightStrike
2023-01-04 15:21 ` Pedro Alves
2023-01-04 15:45 ` Eric Pouech
2023-01-04 15:52 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF1jjLuvDBp-z_GgLQohv2tm66R2Vz=xNE7MUVEgYGvdX4RcKA@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=dejagnu@gnu.org \
--cc=eric.pouech@orange.fr \
--cc=fortran@gcc.gnu.org \
--cc=jacek@codeweavers.com \
--cc=jcb62281@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).