From: takashikkbn@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91897] [Ruby trunk Misc#15336] Duplicate builds on travis-ci?
Date: Wed, 20 Mar 2019 12:12:00 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-77223.20190320121159.2b8690cbd20d6a65@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15336.20181123090640@ruby-lang.org
Issue #15336 has been updated by k0kubun (Takashi Kokubun).
Status changed from Closed to Rejected
Well, as @shyouhei described, daily builds are testing wider range of environments which we do not want for every commit. As the original title "Duplicate builds on travis-ci?" and the description "This seems unnecessary" were wrong, I resurrected the daily cron. Please clean up the cron-specific jobs as well if you really intend to drop the cron-specific builds.
----------------------------------------
Misc #15336: Duplicate builds on travis-ci?
https://bugs.ruby-lang.org/issues/15336#change-77223
* Author: duerst (Martin Dürst)
* Status: Rejected
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
When I did a commit today, I was checking https://travis-ci.org/ruby/ruby/builds to make sure there were no errors.
I noticed a few somewhat strange things:
```
trunk CRON prepare for Unicode 11.0.0 update
duerst #28798 passed 2d5b57d 1 hr 37 min 7 sec 30 minutes ago
trunk prepare for Unicode 11.0.0 update
matzbot #28797 passed 2d5b57d 55 min 28 sec about 2 hours ago
```
It looks as if the same commit ("prepare for Unicode 11.0.0 update") is run twice, the second time run by CRON. This seems unnecessary, I hope we can avoid it.
Also, the first time (starting just after the commit), the committer's name for some reason is not me, but 'matzbot', but in the later run, the name of the committer ("duerst") is correct.
While I'm at it, the run times for the builds ("1 hr 37 min 7 sec" and "55 min 28 sec") are also weird; while I didn't measure the exact times, the builds were done much faster (probably somewhere around 10 min) than what is shown. But I guess this is a travis-ci problem, not ours.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
prev parent reply other threads:[~2019-03-20 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15336.20181123090640@ruby-lang.org>
2018-11-23 9:06 ` [ruby-core:90001] [Ruby trunk Misc#15336] Duplicate builds on travis-ci? duerst
2018-11-26 5:46 ` [ruby-core:90072] " shyouhei
2019-03-20 1:34 ` [ruby-core:91887] " hsbt
2019-03-20 12:12 ` takashikkbn [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-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-77223.20190320121159.2b8690cbd20d6a65@ruby-lang.org \
--to=ruby-core@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).