<div><div dir="auto">Excellent. When can we expect a new package to test?</div></div><div dir="auto"><br></div><div dir="auto">/Frank</div><div dir="auto"><br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes.<br>
<br>
Ingela reacted quickly and did great work with a PR fixing the issue at <br>
<a href="https://github.com/erlang/otp/pull/2224" rel="noreferrer" target="_blank">https://github.com/erlang/otp/pull/2224</a><br>
<br>
Cheers,<br>
<br>
On 08/05/2019 13:19, Frank Muller wrote:<br>
> So? Did we regress?<br>
> <br>
> /Frank<br>
> <br>
> Hello,<br>
> <br>
> Warning! Something's wrong with this release:<br>
> <br>
> <a href="https://bugs.erlang.org/browse/ERL-938" rel="noreferrer" target="_blank">https://bugs.erlang.org/browse/ERL-938</a><br>
> <br>
> On 07/05/2019 10:55, Erlang/OTP wrote:<br>
> > Patch Package: OTP 21.3.8<br>
> > Git Tag: OTP-21.3.8<br>
> > Date: 2019-05-07<br>
> > Trouble Report Id: OTP-14746, OTP-15295, OTP-15717, OTP-15758,<br>
> > OTP-15781, OTP-15785, OTP-15793, OTP-15802<br>
> > Seq num: ERIERL-143, ERIERL-334, ERIERL-337,<br>
> > ERIERL-342, ERIERL-356, ERL-893, ERL-929,<br>
> > ERL-934<br>
> > System: OTP<br>
> > Release: 21<br>
> > Application: common_test-1.17.2, eldap-1.2.7,<br>
> > erl_interface-3.11.3, erts-10.3.5,<br>
> > public_key-1.6.6, ssl-9.2.3, stdlib-3.8.2<br>
> > Predecessor: OTP 21.3.7<br>
> ><br>
> > Check out the git tag OTP-21.3.8, and build a full OTP system<br>
> > including documentation. Apply one or more applications from this<br>
> > build as patches to your installation using the 'otp_patch_apply'<br>
> > tool. For information on install requirements, see descriptions for<br>
> > each application version below.<br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- POTENTIAL INCOMPATIBILITIES<br>
> -------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > OTP-15717 Application(s): common_test<br>
> > Related Id(s): ERIERL-334<br>
> ><br>
> > The test result when a hook function fails is in<br>
> > general the same as if the function that the hook is<br>
> > associated with fails. For example, if<br>
> > post_init_per_testcase fails the result is that the<br>
> > test case is skipped, as is the case when<br>
> > init_per_testcase fails.This, however, was<br>
> earlier not<br>
> > true for timetrap timeouts or other error situations<br>
> > where the process running the hook function was<br>
> killed.<br>
> > This is now corrected, so the error handling<br>
> should be<br>
> > the same no matter how the hook function fails.<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- common_test-1.17.2<br>
> ----------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > The common_test-1.17.2 application can be applied independently of<br>
> > other applications on a full OTP 21 installation.<br>
> ><br>
> > --- Fixed Bugs and Malfunctions ---<br>
> ><br>
> > OTP-15717 Application(s): common_test<br>
> > Related Id(s): ERIERL-334<br>
> ><br>
> > *** POTENTIAL INCOMPATIBILITY ***<br>
> ><br>
> > The test result when a hook function fails is in<br>
> > general the same as if the function that the hook is<br>
> > associated with fails. For example, if<br>
> > post_init_per_testcase fails the result is that the<br>
> > test case is skipped, as is the case when<br>
> > init_per_testcase fails.This, however, was<br>
> earlier not<br>
> > true for timetrap timeouts or other error situations<br>
> > where the process running the hook function was<br>
> killed.<br>
> > This is now corrected, so the error handling<br>
> should be<br>
> > the same no matter how the hook function fails.<br>
> ><br>
> ><br>
> > OTP-15758 Application(s): common_test<br>
> > Related Id(s): ERIERL-342<br>
> ><br>
> > In some rare cases, when two common_test nodes<br>
> used the<br>
> > same log directory, a timing problem could occur<br>
> which<br>
> > caused common_test to crash because it's log<br>
> cache file<br>
> > was unexpectedly empty. This is now corrected.<br>
> ><br>
> ><br>
> > --- Improvements and New Features ---<br>
> ><br>
> > OTP-14746 Application(s): common_test<br>
> > Related Id(s): ERIERL-143<br>
> ><br>
> > Two new common_test hook functions are introduced:<br>
> ><br>
> > post_groups/2, which is called after Suite:groups/0<br>
> > post_all/3, which is called after Suite:all/0<br>
> ><br>
> > These functions allow modifying the return values<br>
> from<br>
> > the groups/0 and all/0 functions, respectively.<br>
> ><br>
> > A new term, {testcase,TestCase,RepeatProperties}<br>
> is now<br>
> > also allowed in the return from all/0. This can<br>
> be used<br>
> > for repeating a single test case a specific number of<br>
> > times, or until it fails or succeeds once.<br>
> ><br>
> ><br>
> > Full runtime dependencies of common_test-1.17.2: compiler-6.0,<br>
> > crypto-3.6, debugger-4.1, erts-7.0, ftp-1.0.0, inets-6.0,<br>
> kernel-4.0,<br>
> > observer-2.1, runtime_tools-1.8.16, sasl-2.4.2, snmp-5.1.2,<br>
> ssh-4.0,<br>
> > stdlib-3.5, syntax_tools-1.7, tools-2.8, xmerl-1.3.8<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- eldap-1.2.7<br>
> -----------------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > The eldap-1.2.7 application can be applied independently of other<br>
> > applications on a full OTP 21 installation.<br>
> ><br>
> > --- Improvements and New Features ---<br>
> ><br>
> > OTP-15785 Application(s): eldap, public_key, ssl<br>
> > Related Id(s): ERL-893, ERL-929, PR-2215<br>
> ><br>
> > Back port of bug fix ERL-893 from OTP-22 and document<br>
> > enhancements that will solve dialyzer warnings for<br>
> > users of the ssl application.<br>
> ><br>
> > This change also affects public_key, eldap (and inet<br>
> > doc).<br>
> ><br>
> ><br>
> > Full runtime dependencies of eldap-1.2.7: asn1-3.0, erts-6.0,<br>
> > kernel-3.0, ssl-5.3.4, stdlib-2.0<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- erl_interface-3.11.3<br>
> --------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > The erl_interface-3.11.3 application can be applied<br>
> independently of<br>
> > other applications on a full OTP 21 installation.<br>
> ><br>
> > --- Fixed Bugs and Malfunctions ---<br>
> ><br>
> > OTP-15781 Application(s): erl_interface<br>
> > Related Id(s): ERIERL-356<br>
> ><br>
> > erl_interface/ei refused to use node names with an<br>
> > alive name (the part of the node name preceding the @<br>
> > sign) longer than 63 characters and a host name<br>
> longer<br>
> > than 64 characters. The total amount of characters<br>
> > allowed in a node name (alivename@hostname) was thus<br>
> > limited to 128 characters. These limits applied<br>
> both to<br>
> > the own node name as well as node names of other<br>
> nodes.<br>
> > Ordinary Erlang nodes limit the node name length<br>
> to 256<br>
> > characters, which meant that you could not<br>
> communicate<br>
> > with certain Erlang nodes due to their node name<br>
> used.<br>
> ><br>
> > erl_interface/ei now allow the total amount of<br>
> > characters in a node name to be up to 256 characters.<br>
> > These characters may be distributed between alive<br>
> name<br>
> > and host name in whatever way needed. That is, the<br>
> > maximum amount of characters in the alive name may be<br>
> > 254 and the maximum amount of characters in the host<br>
> > name may be 254, but in total the node name must not<br>
> > exceed 256 characters.<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- erts-10.3.5<br>
> -----------------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > Note! The erts-10.3.5 application *cannot* be applied independently<br>
> > of other applications on an arbitrary OTP 21 installation.<br>
> ><br>
> > On a full OTP 21 installation, also the following runtime<br>
> > dependencies have to be satisfied:<br>
> > -- kernel-6.1 (first satisfied in OTP 21.1)<br>
> > -- sasl-3.3 (first satisfied in OTP 21.2)<br>
> ><br>
> ><br>
> > --- Fixed Bugs and Malfunctions ---<br>
> ><br>
> > OTP-15793 Application(s): erts<br>
> > Related Id(s): ERIERL-337, OTP-15709<br>
> ><br>
> > Fixed more bugs in process_info(reductions)<br>
> causing it<br>
> > to sometimes behave non-monotonic. That is, a<br>
> > subsequent call toward the same process could<br>
> return a<br>
> > lower reduction value.<br>
> ><br>
> ><br>
> > Full runtime dependencies of erts-10.3.5: kernel-6.1, sasl-3.3,<br>
> > stdlib-3.5<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- public_key-1.6.6<br>
> ------------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > The public_key-1.6.6 application can be applied independently of<br>
> > other applications on a full OTP 21 installation.<br>
> ><br>
> > --- Improvements and New Features ---<br>
> ><br>
> > OTP-15785 Application(s): eldap, public_key, ssl<br>
> > Related Id(s): ERL-893, ERL-929, PR-2215<br>
> ><br>
> > Back port of bug fix ERL-893 from OTP-22 and document<br>
> > enhancements that will solve dialyzer warnings for<br>
> > users of the ssl application.<br>
> ><br>
> > This change also affects public_key, eldap (and inet<br>
> > doc).<br>
> ><br>
> ><br>
> > Full runtime dependencies of public_key-1.6.6: asn1-3.0,<br>
> crypto-3.8,<br>
> > erts-6.0, kernel-3.0, stdlib-3.5<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- ssl-9.2.3<br>
> -------------------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > The ssl-9.2.3 application can be applied independently of other<br>
> > applications on a full OTP 21 installation.<br>
> ><br>
> > --- Fixed Bugs and Malfunctions ---<br>
> ><br>
> > OTP-15802 Application(s): ssl<br>
> > Related Id(s): ERL-934<br>
> ><br>
> > Missing check of size of user_data_buffer made<br>
> internal<br>
> > socket behave as an active socket instead of<br>
> active N.<br>
> > This could cause memory problems.<br>
> ><br>
> ><br>
> > --- Improvements and New Features ---<br>
> ><br>
> > OTP-15785 Application(s): eldap, public_key, ssl<br>
> > Related Id(s): ERL-893, ERL-929, PR-2215<br>
> ><br>
> > Back port of bug fix ERL-893 from OTP-22 and document<br>
> > enhancements that will solve dialyzer warnings for<br>
> > users of the ssl application.<br>
> ><br>
> > This change also affects public_key, eldap (and inet<br>
> > doc).<br>
> ><br>
> ><br>
> > Full runtime dependencies of ssl-9.2.3: crypto-4.2, erts-10.0,<br>
> > inets-5.10.7, kernel-6.0, public_key-1.5, stdlib-3.5<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > --- stdlib-3.8.2<br>
> ----------------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > The stdlib-3.8.2 application can be applied independently of other<br>
> > applications on a full OTP 21 installation.<br>
> ><br>
> > --- Fixed Bugs and Malfunctions ---<br>
> ><br>
> > OTP-15295 Application(s): stdlib<br>
> ><br>
> > A bug in gen_statem has been fixed where the internal<br>
> > timeout message could arrive as an info to the<br>
> callback<br>
> > module during high load due to incorrect use of<br>
> > asynchronous timer cancel.<br>
> ><br>
> ><br>
> > Full runtime dependencies of stdlib-3.8.2: compiler-5.0,<br>
> crypto-3.3,<br>
> > erts-10.0, kernel-6.0, sasl-3.0<br>
> ><br>
> ><br>
> > <br>
> ---------------------------------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> > <br>
> ---------------------------------------------------------------------<br>
> ><br>
> > _______________________________________________<br>
> > erlang-questions mailing list<br>
> > <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a>><br>
> > <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> ><br>
> <br>
> -- <br>
> Loïc Hoguin<br>
> <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a>><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> <br>
<br>
-- <br>
Loïc Hoguin<br>
<a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
</blockquote></div></div>