From: takashikkbn@... Date: 2019-03-20T12:12:00+00:00 Subject: [ruby-core:91897] [Ruby trunk Misc#15336] Duplicate builds on travis-ci? 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: