From: Johannes Schindelin <Johannes.Schindelin@gmx.de> To: "Randall S. Becker" <email@example.com> Cc: 'Junio C Hamano' <firstname.lastname@example.org>, email@example.com, 'Linux Kernel' <firstname.lastname@example.org>, email@example.com Subject: RE: [ANNOUNCE] Git v2.22.0 Date: Mon, 10 Jun 2019 20:42:08 +0200 (CEST) [thread overview] Message-ID: <nycvar.QRO.126.96.36.1996102032450.789@QRFXGBC-DHN364S.ybpnyqbznva> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Randall, On Mon, 10 Jun 2019, Randall S. Becker wrote: > On Friday, June 7, 2019 5:31 PM, Junio C Hamano wrote: > > The latest feature release Git v2.22.0 is now available at the > > usual places. It is comprised of 745 non-merge commits since > > v2.21.0, contributed by 74 people, 18 of which are new faces. > > Report from NonStop tests: > t7519 subtest 25 still fails on first execution but not on second. As mentioned previously: known issue. The patch to fix that is in `next` (1aa850bc59 (Merge branch 'js/fsmonitor-unflake' into next, 2019-05-30). > t9001 subtests 33, 82, 118, 119, 146 fail. We have no normal sendmail on platform. Maybe you should craft a patch series that adds a new prereq that verifies that sendmail works, and contribute a patch that marks those test cases with that prereq. > t9020, t9600, t9601, t9602 all fail - we have no SVN. I may be able to > handle exclusions for the next release. The question is why they fail even if the correspondig prereq should have triggered. Another opportunity for you to contribute a patch series! (By my analysis, you rank #277 in the `git shortlog -nse --no-merges` statistics, and just 17 patches would improve your rank to #150 or better...) > So essentially, no change from previous releases other than t7519 being > wonky. This is a pass. Thanks for all hard work from the team. Yes, t7519 became "more wonky" as a consequence of a bug fix of mine that made that particular bug a lot more prominent. So prominent, in fact, that I contributed two patches that will improve my rank ;-) Ciao, Johannes
prev parent reply other threads:[~2019-06-10 18:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-07 21:31 Junio C Hamano 2019-06-07 22:48 ` Bhaskar Chowdhury 2019-06-10 13:27 ` Randall S. Becker 2019-06-10 18:42 ` Johannes Schindelin [this message]
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=nycvar.QRO.188.8.131.526102032450.789@QRFXGBC-DHN364S.ybpnyqbznva \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='RE: [ANNOUNCE] Git v2.22.0' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).