From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
Subject: [ruby-core:112028] [Ruby master Feature#16012] Add a (small) test-install suite?
Date: Wed, 25 Jan 2023 09:11:32 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-101462.20230125091132.11129@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16012.20190719142756.11129@ruby-lang.org
Issue #16012 has been updated by hsbt (Hiroshi SHIBATA).
I'm considering this request again. I'll add small check into https://github.com/ruby/chkbuild.
----------------------------------------
Feature #16012: Add a (small) test-install suite?
https://bugs.ruby-lang.org/issues/16012#change-101462
* Author: MSP-Greg (Greg L)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
At various times there has been discussion about whether testing should require `make install`. Although I prefer to do testing using install (vs build), I see it as a choice, and not a requirement.
From time to time various issues have arisen that cannot be found with 'build' testing. Often, these issues cause CI test failure with master/trunk/ruby-head in external repos. Sometimes people blame 'Core', other times Travis, or rvm. Regardless, it doesn't look good.
So, might a small set of tests that check install functionality be added? It may need to be two separate (but equivalent) scripts. One for *nix, one for Windows.
In ruby-loco, I'm using a ps1 script to check that CLI bin files work. As soon as the update is pushed here, I'll add a test for nested bundler commands...
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2023-01-25 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16012.20190719142756.11129@ruby-lang.org>
2023-01-25 9:11 ` hsbt (Hiroshi SHIBATA) via ruby-core [this message]
2023-01-25 12:49 ` [ruby-core:112031] [Ruby master Feature#16012] Add a (small) test-install suite? Eregon (Benoit Daloze) via ruby-core
2023-01-25 12:50 ` [ruby-core:112032] " Eregon (Benoit Daloze) via ruby-core
2024-04-02 6:34 ` [ruby-core:117405] " hsbt (Hiroshi SHIBATA) via ruby-core
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-101462.20230125091132.11129@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.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.
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).