From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.11.0-0.1
Date: Fri, 10 Aug 2018 16:01:00 -0000 [thread overview]
Message-ID: <33525860-8acf-21fc-e4c6-1c62aa5bfac2@gmail.com> (raw)
In-Reply-To: <announce.20180809202604.GN4180@calimero.vinschen.de>
Am 09.08.2018 um 22:26 schrieb Corinna Vinschen:
> Hi folks,
>
>
> I uploaded a new Cygwin test release 2.11.0-0.1
>
> I'm planning for a release end of August. Please test.
>
> =======================================================================
>
> What's new:
> -----------
>
> - New APIs: clearenv, pthread_tryjoin_np, pthread_timedjoin_np,
> sched_getcpu.
>
> - New APIs: aio_cancel, aio_error, aio_fsync, aio_read, aio_return,
> aio_suspend, aio_write, lio_listio.
> New header: <aio.h>.
>
>
> What changed:
> -------------
>
> - SO_RCVTIMEO and SO_SNDTIMEO socket options are now honored.
>
> - /proc/cpuinfo now reports L3 cache size on Intel CPUs.
>
>
> Bug Fixes
> ---------
>
> - Fix utils path handling in case cygdrive path is just '/'.
> Addresses: https://cygwin.com/ml/cygwin/2018-02/msg00174.html
>
> - Fix a potential SIGFPE in strtod, if FE_INVALID exceptions are
> enabled.
> Addresses: https://cygwin.com/ml/cygwin/2018-04/msg00055.html
>
> - Fix a CPU affinity problem when creating /proc/cpuinfo output.
> Addresses: https://cygwin.com/ml/cygwin/2018-04/msg00118.html
>
> - Fix a buffer underrun problem in Win32 path normalization.
> Addresses: https://cygwin.com/ml/cygwin/2018-05//msg00017.html
>
> - Fix a stack alignment problem which may lead to spurious crashes after
> fork.
> Addresses: https://cygwin.com/ml/cygwin-patches/2018-q2/msg00016.html
>
> - Fix a g++ compilation problem with -std=c++14 or -std=c++17.
> Addresses: https://cygwin.com/ml/cygwin/2018-05/msg00316.html
>
> - Fix FPE flag handling for division by zero conditions
> Addresses: https://cygwin.com/ml/cygwin/2018-06/msg00281.html
>
> - Fix Unicode table.
> Addresses: https://cygwin.com/ml/cygwin/2018-06/msg00248.html
>
> - Handle a non-standard return value from some tape drives to
> report a "no-media" error.
> Addresses: https://cygwin.com/ml/cygwin/2018-06/msg00245.html
>
> - Fix duration handling in sigtimedwait
> Addresses: https://cygwin.com/ml/cygwin-patches/2018-q3/msg00018.html
>
> - Make FP environment symbols available on x86_64.
> Addresses: https://cygwin.com/ml/cygwin/2018-07/msg00183.html
>
> - Fix fegetenv behaviour.
> Addresses: https://cygwin.com/ml/cygwin/2018-08/msg00000.html
>
> =======================================================================
>
>
> Have fun,
> Corinna
>
testing libuv, I see a large number of new failures
not ok 217 - tcp6_ping_pong
# timeout
# Output from process `tcp6_ping_pong`: (no output)
# PING
not ok 218 - tcp6_ping_pong_vec
# timeout
# Output from process `tcp6_ping_pong_vec`: (no output)
# PING
not ok 219 - tcp_alloc_cb_fail
# timeout
# Output from process `tcp_alloc_cb_fail`: (no output)
not ok 234 - tcp_close_accept
# timeout
# Output from process `tcp_close_accept`: (no output)
not ok 235 - tcp_close_while_connecting
# timeout
# Output from process `tcp_close_while_connecting`: (no output)
not ok 238 - tcp_connect_timeout
# timeout
# Output from process `tcp_connect_timeout`: (no out
not ok 245 - tcp_oob
# timeout
# Output from process `tcp_oob`: (no output)
not ok 246 - tcp_open
# timeout
# Output from process `tcp_open`: (no output)
not ok 248 - tcp_open_connected
# timeout
# Output from process `tcp_open_connected`: (no output)
not ok 250 - tcp_ping_pong
# timeout
# Output from process `tcp_ping_pong`: (no output)
# PING
not ok 251 - tcp_ping_pong_vec
# timeout
# Output from process `tcp_ping_pong_vec`: (no output)
# PING
not ok 259 - tcp_try_write
# timeout
# Output from process `tcp_try_write`: (no output)
not ok 260 - tcp_unexpected_read
# timeout
# Output from process `tcp_unexpected_read`: (no output)
not ok 263 - tcp_write_queue_order
# timeout
# Output from process `tcp_write_queue_order`: (no output)
not ok 264 - tcp_write_to_half_open_connection
# timeout
# Output from process `tcp_write_to_half_open_connection`: (no output)
not ok 265 - tcp_writealot
# timeout
# Output from process `tcp_writealot`: (no output)
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-08-10 16:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 20:27 Corinna Vinschen
2018-08-10 0:05 ` Andrey Repin
2018-08-10 11:05 ` Houder
2018-08-10 11:43 ` Corinna Vinschen
2018-08-10 12:43 ` Houder
2018-08-13 7:47 ` Corinna Vinschen
2018-08-13 8:03 ` Houder
2018-08-13 8:23 ` Corinna Vinschen
2018-08-13 21:29 ` Houder
2018-08-13 22:16 ` Eric Blake
2018-08-13 22:26 ` Houder
2018-08-14 6:09 ` john doe
2018-08-13 22:16 ` Houder
2018-08-14 9:50 ` Corinna Vinschen
2018-08-14 11:38 ` Houder
2018-08-13 20:27 ` Achim Gratz
2018-08-10 16:01 ` Marco Atzeri [this message]
2018-08-13 7:48 ` Corinna Vinschen
2018-08-13 8:36 ` Thomas Wolff
2018-08-13 11:25 ` Corinna Vinschen
2018-08-16 21:33 ` Achim Gratz
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=33525860-8acf-21fc-e4c6-1c62aa5bfac2@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).