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, DejaGnu mailing list <dejagnu@gnu.org>
Subject: Re: testsuite under wine
Date: Tue, 10 Jan 2023 04:19:00 -0500 [thread overview]
Message-ID: <CAF1jjLv_tnGNWw4iFuxmx0eYAu_ui6fYU4d8-=3qj0VQG0VAzA@mail.gmail.com> (raw)
In-Reply-To: <3b3bea69-9b71-c1e5-71cd-4e5e588178b4@codeweavers.com>
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. Here are the result
summaries, full logs available to anyone who wants them.
Unmodified Wine 7.20:
=== gcc Summary ===
# of expected passes 166686
# of unexpected failures 1865
# of unexpected successes 12
# of expected failures 1226
# of unresolved testcases 787
# of unsupported tests 3111
=== gfortran Summary ===
# of expected passes 66391
# of unexpected failures 637
# of unexpected successes 8
# of expected failures 257
# of unresolved testcases 6
# of unsupported tests 247
=== g++ Summary ===
# of expected passes 218092
# of unexpected failures 1410
# of unexpected successes 4
# of expected failures 2149
# of unresolved testcases 63
# of unsupported tests 11318
=== gm2 Summary ===
# of expected passes 7126
# of unexpected failures 2563
# of unresolved testcases 2065
=== libatomic Summary ===
# of expected passes 53
# of unexpected failures 1
=== libstdc++ Summary ===
# of expected passes 14139
# of unexpected failures 474
# of unexpected successes 2
# of expected failures 98
# of unresolved testcases 1
# of unsupported tests 835
=== rust Summary ===
# of expected passes 4565
# of unexpected failures 403
# of expected failures 39
Modified Wine 7.20 using your latest one liner patch:
=== gcc Summary ===
# of expected passes 168207
# of unexpected failures 1867
# of unexpected successes 12
# of expected failures 1235
# of unresolved testcases 760
# of unsupported tests 3118
=== gfortran Summary ===
# of expected passes 66409
# of unexpected failures 619
# of unexpected successes 8
# of expected failures 257
# of unresolved testcases 6
# of unsupported tests 247
=== g++ Summary ===
# of expected passes 220403
# of unexpected failures 1116
# of unexpected successes 4
# of expected failures 2063
# of unresolved testcases 47
# of unsupported tests 10978
=== gm2 Summary ===
# of expected passes 7126
# of unexpected failures 2563
# of unresolved testcases 2065
=== libatomic Summary ===
# of expected passes 53
# of unexpected failures 1
runtest completed at Tue Jan 10 00:05:49 2023
=== libstdc++ Summary ===
# of expected passes 14139
# of unexpected failures 474
# of unexpected successes 2
# of expected failures 98
# of unresolved testcases 1
# of unsupported tests 835
=== rust Summary ===
# of expected passes 4568
# of unexpected failures 394
# of expected failures 39
next prev parent reply other threads:[~2023-01-10 9:19 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 [this message]
2023-01-11 9:10 ` NightStrike
2023-01-11 18:41 ` NightStrike
2023-01-14 23:36 ` NightStrike
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='CAF1jjLv_tnGNWw4iFuxmx0eYAu_ui6fYU4d8-=3qj0VQG0VAzA@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).