ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
* [ruby-core:90001] [Ruby trunk Misc#15336] Duplicate builds on travis-ci?
       [not found] <redmine.issue-15336.20181123090640@ruby-lang.org>
@ 2018-11-23  9:06 ` duerst
  2018-11-26  5:46 ` [ruby-core:90072] " shyouhei
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 4+ messages in thread
From: duerst @ 2018-11-23  9:06 UTC (permalink / raw)
  To: ruby-core

Issue #15336 has been reported by duerst (Martin Dürst).

----------------------------------------
Misc #15336: Duplicate builds on travis-ci?
https://bugs.ruby-lang.org/issues/15336

* Author: duerst (Martin Dürst)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
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/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ruby-core:90072] [Ruby trunk Misc#15336] Duplicate builds on travis-ci?
       [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 ` shyouhei
  2019-03-20  1:34 ` [ruby-core:91887] " hsbt
  2019-03-20 12:12 ` [ruby-core:91897] " takashikkbn
  3 siblings, 0 replies; 4+ messages in thread
From: shyouhei @ 2018-11-26  5:46 UTC (permalink / raw)
  To: ruby-core

Issue #15336 has been updated by shyouhei (Shyouhei Urabe).


I don't have answers for every questions but for the first one: we enable cron builds for Travis-CI, which run every day.  This is a handy occasion to do lots of additional tests.  Compare these two results:

- https://travis-ci.org/ruby/ruby/builds/458679372
- https://travis-ci.org/ruby/ruby/builds/458696964

You see the latter has richer amount of build configurations than the former.  This is why the total running time differ between them.  We want non-cron builds to run faster, while cron builds are sacrificing running time to cover more.

----------------------------------------
Misc #15336: Duplicate builds on travis-ci?
https://bugs.ruby-lang.org/issues/15336#change-75195

* Author: duerst (Martin Dürst)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
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/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ruby-core:91887] [Ruby trunk Misc#15336] Duplicate builds on travis-ci?
       [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 ` hsbt
  2019-03-20 12:12 ` [ruby-core:91897] " takashikkbn
  3 siblings, 0 replies; 4+ messages in thread
From: hsbt @ 2019-03-20  1:34 UTC (permalink / raw)
  To: ruby-core

Issue #15336 has been updated by hsbt (Hiroshi SHIBATA).

Assignee set to hsbt (Hiroshi SHIBATA)
Status changed from Open to Closed

I removed CRON jobs from Travis CI. 

----------------------------------------
Misc #15336: Duplicate builds on travis-ci?
https://bugs.ruby-lang.org/issues/15336#change-77210

* Author: duerst (Martin Dürst)
* Status: Closed
* 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>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ruby-core:91897] [Ruby trunk Misc#15336] Duplicate builds on travis-ci?
       [not found] <redmine.issue-15336.20181123090640@ruby-lang.org>
                   ` (2 preceding siblings ...)
  2019-03-20  1:34 ` [ruby-core:91887] " hsbt
@ 2019-03-20 12:12 ` takashikkbn
  3 siblings, 0 replies; 4+ messages in thread
From: takashikkbn @ 2019-03-20 12:12 UTC (permalink / raw)
  To: ruby-core

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>

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-03-20 12:12 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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 ` [ruby-core:91897] " takashikkbn

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