From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH 0/8] Further testsuite fixes
Date: Tue, 10 Jan 2023 16:37:01 +0000 [thread overview]
Message-ID: <20230110163709.16265-1-jon.turney@dronecode.org.uk> (raw)
This gets us from:
> FAIL: cygload (execute)
> FAIL: devdsp.c (execute)
> FAIL: ltp/access05.c (execute)
> FAIL: ltp/fcntl07.c (execute)
> FAIL: ltp/fcntl07B.c (execute)
> FAIL: ltp/fork09.c (execute)
> FAIL: ltp/link04.c (execute)
> FAIL: ltp/symlink03.c (execute)
> FAIL: msgtest.c (execute)
> FAIL: pthread/cancel11.c (execute)
> FAIL: pthread/cancel3.c (execute)
> FAIL: pthread/cancel5.c (execute)
> FAIL: pthread/inherit1.c (execute)
> FAIL: pthread/mutex5.c (execute)
> FAIL: pthread/mutex7.c (execute)
> FAIL: pthread/mutex7d.c (execute)
> FAIL: pthread/mutex7n.c (execute)
> FAIL: pthread/priority1.c (execute)
> FAIL: pthread/priority2.c (execute)
> FAIL: pthread/rwlock6.c (execute)
> FAIL: semtest.c (execute)
> FAIL: shmtest.c (execute)
> FAIL: systemcall.c (execute)
>
> === winsup Summary ===
>
> # of expected passes 255
> # of unexpected failures 23
> # of expected failures 6
to:
> FAIL: cygload
> FAIL: devdsp.c
> FAIL: ltp/access05.c
> FAIL: ltp/fcntl07.c
> FAIL: ltp/fork09.c
> FAIL: ltp/symlink01.c
> FAIL: ltp/symlink03.c
> FAIL: ltp/umask03.c
> FAIL: pthread/cancel11.c
> FAIL: pthread/cancel3.c
> FAIL: pthread/cancel5.c
> FAIL: pthread/inherit1.c
> FAIL: pthread/priority1.c
> FAIL: pthread/priority2.c
> FAIL: systemcall.c
>
> === winsup Summary ===
>
> # of expected passes 263
> # of unexpected failures 15
> # of expected failures 5
which is almost manageable!
Jon Turney (8):
Cygwin: testsuite: automake doesn't define objdir
Cygwin: testsuite: Build testcases using automake
Cygwin: testsuite: Fix compilation warnings
Cygwin: testsuite: 64-bit fixes in pthread testcases
Cygwin: testsuite: Update mutex tests for changed default mutex type
Cygwin: testsuite: Update pthread tests for default SCHED_FIFO
Cygwin: testsuite: Drop appending 'ntsec' to CYGWIN in cygrun wrapper
Cygwin: CI: Run cygserver for tests
.github/workflows/cygwin.yml | 16 +-
winsup/configure.ac | 2 +-
winsup/testsuite/Makefile.am | 309 +++++++++++++++++-
winsup/testsuite/README | 2 +-
winsup/testsuite/cygrun.c | 16 -
winsup/testsuite/libltp/include/usctest.h | 2 +-
.../testsuite/{cygrun => mingw}/Makefile.am | 11 +-
winsup/testsuite/winsup.api/cygload.exp | 32 +-
winsup/testsuite/winsup.api/ltp/execv01.c | 2 +-
winsup/testsuite/winsup.api/ltp/execve01.c | 2 +-
winsup/testsuite/winsup.api/ltp/execvp01.c | 2 +-
winsup/testsuite/winsup.api/ltp/mmap02.c | 10 +-
winsup/testsuite/winsup.api/ltp/mmap03.c | 10 +-
winsup/testsuite/winsup.api/ltp/mmap04.c | 10 +-
winsup/testsuite/winsup.api/ltp/mmap05.c | 10 +-
winsup/testsuite/winsup.api/ltp/mmap06.c | 8 +-
winsup/testsuite/winsup.api/ltp/mmap07.c | 8 +-
winsup/testsuite/winsup.api/ltp/mmap08.c | 8 +-
winsup/testsuite/winsup.api/mmaptest03.c | 2 +-
winsup/testsuite/winsup.api/pthread/cancel2.c | 10 +-
winsup/testsuite/winsup.api/pthread/cancel3.c | 10 +-
winsup/testsuite/winsup.api/pthread/cancel4.c | 10 +-
winsup/testsuite/winsup.api/pthread/cancel5.c | 12 +-
.../testsuite/winsup.api/pthread/cleanup2.c | 10 +-
.../testsuite/winsup.api/pthread/cleanup3.c | 8 +-
.../testsuite/winsup.api/pthread/condvar2_1.c | 12 +-
.../testsuite/winsup.api/pthread/condvar3_1.c | 12 +-
.../testsuite/winsup.api/pthread/condvar3_2.c | 14 +-
winsup/testsuite/winsup.api/pthread/exit3.c | 2 +-
.../testsuite/winsup.api/pthread/inherit1.c | 12 +-
winsup/testsuite/winsup.api/pthread/join1.c | 10 +-
winsup/testsuite/winsup.api/pthread/join2.c | 8 +-
winsup/testsuite/winsup.api/pthread/mutex4.c | 2 +-
winsup/testsuite/winsup.api/pthread/mutex5.c | 2 +-
winsup/testsuite/winsup.api/pthread/mutex7.c | 3 +-
winsup/testsuite/winsup.api/pthread/mutex7d.c | 3 +-
winsup/testsuite/winsup.api/pthread/mutex7n.c | 1 -
.../testsuite/winsup.api/pthread/priority1.c | 10 +-
.../testsuite/winsup.api/pthread/priority2.c | 12 +-
winsup/testsuite/winsup.api/pthread/rwlock6.c | 22 +-
.../winsup.api/samples/sample-miscompile.c | 1 -
winsup/testsuite/winsup.api/systemcall.c | 2 +-
winsup/testsuite/winsup.api/user_malloc.c | 4 +-
winsup/testsuite/winsup.api/winsup.exp | 37 +--
44 files changed, 470 insertions(+), 221 deletions(-)
rename winsup/testsuite/{cygrun => mingw}/Makefile.am (58%)
delete mode 100644 winsup/testsuite/winsup.api/samples/sample-miscompile.c
--
2.39.0
next reply other threads:[~2023-01-10 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 16:37 Jon Turney [this message]
2023-01-10 16:37 ` [PATCH 1/8] Cygwin: testsuite: automake doesn't define objdir Jon Turney
2023-01-10 16:37 ` [PATCH 2/8] Cygwin: testsuite: Build testcases using automake Jon Turney
2023-01-10 16:37 ` [PATCH 3/8] Cygwin: testsuite: Fix compilation warnings Jon Turney
2023-01-10 16:37 ` [PATCH 4/8] Cygwin: testsuite: 64-bit fixes in pthread testcases Jon Turney
2023-01-10 16:37 ` [PATCH 5/8] Cygwin: testsuite: Update mutex tests for changed default mutex type Jon Turney
2023-01-10 16:37 ` [PATCH 6/8] Cygwin: testsuite: Update pthread tests for default SCHED_FIFO Jon Turney
2023-01-10 16:37 ` [PATCH 7/8] Cygwin: testsuite: Drop appending 'ntsec' to CYGWIN in cygrun wrapper Jon Turney
2023-01-10 16:37 ` [PATCH 8/8] Cygwin: CI: Run cygserver for tests Jon Turney
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=20230110163709.16265-1-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-patches@cygwin.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).