git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.16.0-rc2 - breakages in t1308 and 1404
Date: Fri, 12 Jan 2018 14:42:21 -0500	[thread overview]
Message-ID: <004b01d38bdd$7a11da60$6e358f20$@nexbridge.com> (raw)

On January 11, 2018 11:11 PM, Junio C Hamano wrote:
> A release candidate Git v2.16.0-rc2 is now available for testing at the usual
> places.  It is comprised of 483 non-merge commits since v2.15.0, contributed
> by 80 people, 23 of which are new faces.
<snip>

Please forgive my not knowing the proper way to report this ... we have a few breakages on the NonStop port (which has finally caught up to 2.16, yay!). The test run takes a very long time to run, so this is preliminary. I'm also not sure who should try to resolve these.

For 1308:

Value not found for "foo.bar"
not ok 23 - proper error on directory "files"
#
#               echo "Error (-1) reading configuration file a-directory." >expect &&
#               mkdir a-directory &&
#               test_expect_code 2 test-config configset_get_value foo.bar a-directory 2>output &&
#               grep "^warning:" output &&
#               grep "^Error" output >actual &&
#               test_cmp expect actual
test_expect_code: command exited with 1, we wanted 2 test-config configset_get_value foo.bar a-directory

It looks like the exit code is coming back as 1 not 2. There is also a file except vs expect.
./trash directory.t1308-config-set: ls
a-directory  actual  config2  except  expect  output  result

For 1404: It looks like the error was detected, but the test case was not structured to handle where the detection occurred. Here's what I see:

not ok 52 - delete fails cleanly if packed-refs file is locked
#
#               prefix=refs/locked-packed-refs &&
#               # Set up a reference with differing loose and packed versions:
#               git update-ref $prefix/foo $C &&
#               git pack-refs --all &&
#               git update-ref $prefix/foo $D &&
#               git for-each-ref $prefix >unchanged &&
#               # Now try to delete it while the `packed-refs` lock is held:
#               : >.git/packed-refs.lock &&
#               test_when_finished "rm -f .git/packed-refs.lock" &&
#               test_must_fail git update-ref -d $prefix/foo >out 2>err &&
#               git for-each-ref $prefix >actual &&
#               test_i18ngrep "Unable to create $Q.*packed-refs.lock$Q: File exists" err &&
#               test_cmp unchanged actual
#

# failed 1 among 52 test(s)
1..52
./trash directory.t1404-update-ref-errors: ls
actual       commands  expected      expected-refs  out         unchanged
actual-refs  err       expected-err  input          output.err
./trash directory.t1404-update-ref-errors: cat err
error: Unable to create '/home/git/git/t/trash directory.t1404-update-ref-errors/.git/packed-refs.lock': File already exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.
./trash directory.t1404-update-ref-errors: cat out

Sincerely,
Randall

-- Brief whoami:
 NonStop developer since approximately 211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.




             reply	other threads:[~2018-01-12 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 19:42 Randall S. Becker [this message]
2018-01-12 22:07 ` [ANNOUNCE] Git v2.16.0-rc2 - breakages in t1308 and 1404 Junio C Hamano
2018-01-12 23:10   ` Randall S. Becker
2018-01-12 23:27     ` Junio C Hamano
2018-01-13  2:51       ` Tanay Abhra
2018-01-16 18:19         ` Junio C Hamano

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='004b01d38bdd$7a11da60$6e358f20$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public 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).