user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <>
Subject: git.t test failing in master
Date: Fri, 18 Jan 2019 12:20:56 -0500	[thread overview]
Message-ID: <20190118172056.GB5108@pure.paranoia.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]


I'm working to get to the latest master, but it would
appear "make test" is not completing correctly:

t/git.t .................... 1/? Modification of a read-only value attempted at /.../blib/lib/PublicInbox/ line 31.
# Tests were run but no plan was declared and done_testing() was not seen.
t/git.t .................... Dubious, test returned 255 (wstat 65280, 0xff00)

And, at the end:

Test Summary Report
t/git.t                  (Wstat: 65280 Tests: 34 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=67, Tests=2062, 37 wallclock secs ( 0.26 usr  0.07 sys + 16.95 cusr  9.63 csys = 26.91 CPU)
Result: FAIL
Failed 1/67 test programs. 0/2062 subtests failed.
make: *** [test_dynamic] Error 255

This is probably fairly benign from the looks of it, but I'd like your
opinion on whether this is something to worry about before deploying.

Perl: v5.16.3
Git: 2.16.5
Tree: d66aa534a4a7506cfc5cfab49d1e09f8db8be3dd


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2019-01-18 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 17:20 Konstantin Ryabitsev [this message]
2019-01-18 19:47 ` [PATCH] t/git.t: avoid passing read-only value to git_unquote Eric Wong
2019-01-18 20:07   ` Konstantin Ryabitsev

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190118172056.GB5108@pure.paranoia.local \ \ \

* 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

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).