From: joaotavora@gmail.com (João Távora)
To: Glenn Morris <rgm@gnu.org>
Cc: 29187@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#29187: flymake ruby and perl tests fail on rhel7.4
Date: Tue, 07 Nov 2017 22:58:35 +0000 [thread overview]
Message-ID: <87zi7xofvo.fsf@gmail.com> (raw)
In-Reply-To: <bxtvy5syio.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 07 Nov 2017 14:02:23 -0500")
Glenn Morris <rgm@gnu.org> writes:
> João Távora wrote:
>
>> This is bizarre, because I did manage to reproduce and fix, on a
>> separate Ubuntu machine I have access to, one of the errors that you
>> had, Glenn, and that was indeed due to the extra diagnostic line
>> produced by your perl.
>>
>> But I don't get any differences between interactive and non-interactive
>> cases and I can't understand how your test run could possibly have
>> succeeded interactively since it produces that same extra line.
>
> There's no difference between the interactive and non-interactive case
> for me with the Perl test (I don't think I said there was?).
Well, you did write "same here" after Dmitry said there was a
difference.
>> Dmitry Gutov <dgutov@yandex.ru> writes:
>[...]
>>> It also fails here via 'make check' (with Ruby 1.9.3) but succeeds
>>> interactively.
>Same here.
^^^^^^^^^
>> and non-interactively (make check also works, obviuosly)
>>
>> $ src/emacs -Q --eval "(setq load-prefer-newer t)" -l test/lisp/progmodes/flymake-tests.el --batch --eval "(ert-run-tests-batch-and-exit \"\")"
>
> This is not equivalent to make check, which sets HOME=/nonexistent.
> Indeed that is the cause of the issue for me:
>
> HOME=/nonexistent ruby -wc test/lisp/progmodes/flymake-resources/test.rb
>
> fails with a ruby error:
>
> /usr/share/rubygems/rubygems/path_support.rb:68:in `path=': undefined
> method `+' for nil:NilClass (NoMethodError)
> from /usr/share/rubygems/rubygems/path_support.rb:30:in `initialize'
>
> I don't use ruby and have no idea if this is normal.
Wow, subtle stuff. My ruby (2.3) doesn't crash. Does yours also fail if
you use a absolute path after -wc instead of a relative one?
>
> It does, thanks.
So I guess all that's missing is a fix to the ruby case. If the absolute
path doesn't fix it, I think we can fake a dummy HOME
next prev parent reply other threads:[~2017-11-07 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 23:44 bug#29187: flymake ruby and perl tests fail on rhel7.4 Glenn Morris
2017-11-07 0:25 ` Dmitry Gutov
2017-11-07 0:45 ` João Távora
2017-11-07 1:35 ` Glenn Morris
2017-11-07 15:57 ` João Távora
2017-11-07 17:22 ` Dmitry Gutov
2017-11-07 19:02 ` Glenn Morris
2017-11-07 19:08 ` Glenn Morris
2017-11-07 22:58 ` João Távora [this message]
2017-11-08 1:42 ` Glenn Morris
2017-11-08 11:35 ` João Távora
2017-11-08 19:35 ` Glenn Morris
2017-11-09 20:21 ` João Távora
2017-11-07 10:21 ` Dmitry Gutov
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=87zi7xofvo.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=29187@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=rgm@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.