Config
Log for #openttdcoop.devzone on 15th February 2014:
Times are UTC Toggle Colours
01:55:43  *** gelignite_ has joined #openttdcoop.devzone
02:02:59  *** gelignite has quit IRC
02:20:11  *** yorick has quit IRC
04:23:12  *** gelignite_ has quit IRC
08:40:55  *** Alberth has joined #openttdcoop.devzone
09:29:15  *** Elyon has quit IRC
11:04:17  *** andythenorth has joined #openttdcoop.devzone
11:23:41  *** skyem123 has joined #openttdcoop.devzone
11:25:38  *** Elyon has joined #openttdcoop.devzone
11:39:59  *** andythenorth has quit IRC
11:56:18  *** frosch123 has joined #openttdcoop.devzone
12:22:44  *** gelignite has joined #openttdcoop.devzone
12:30:55  *** Supercheese is now known as Guest118
12:31:00  *** Supercheese has joined #openttdcoop.devzone
12:34:15  *** Elyon has quit IRC
12:36:10  *** Guest118 has quit IRC
12:49:32  *** yorick has joined #openttdcoop.devzone
13:05:14  *** oskari89 has joined #openttdcoop.devzone
13:23:22  *** skyem123 has quit IRC
14:20:01  *** Elyon has joined #openttdcoop.devzone
14:43:15  *** andythenorth has joined #openttdcoop.devzone
15:21:50  *** andythenorth has quit IRC
15:44:52  *** andythenorth has joined #openttdcoop.devzone
16:04:19  *** andythenorth has quit IRC
16:20:43  <DevZone> Project opengfx-mars build #25-test: SUCCESS in 2 min 20 sec: https://jenkins.openttdcoop.org/job/opengfx-mars/25/
16:20:51  <DevZone> Project Townnames - German build #11-test: SUCCESS in 7.8 sec: https://jenkins.openttdcoop.org/job/german-townnames/11/
16:20:58  <DevZone> Project NML - NewGRF Meta Language build #252-nightlies: SUCCESS in 3 min 12 sec: https://jenkins.openttdcoop.org/job/nml/252/
16:33:38  *** andythenorth has joined #openttdcoop.devzone
16:39:52  *** andythenorth has quit IRC
16:48:15  <DevZone> Project 2ccts build #28-push: SUCCESS in 29 sec: https://jenkins.openttdcoop.org/job/2ccts/28/
16:48:39  <DevZone> Project Dutch Trainset build #82-push: SUCCESS in 1 min 9 sec: https://jenkins.openttdcoop.org/job/dutchtrains/82/
16:54:39  <DevZone> Project ISR Industrial Station Renewal build #109-push: SUCCESS in 24 sec: https://jenkins.openttdcoop.org/job/isr/109/
17:03:25  *** Zuu has joined #openttdcoop.devzone
17:22:02  <DevZone> Project Japanese Buildings build #112-nightlies: SUCCESS in 16 sec: https://jenkins.openttdcoop.org/job/jpbuild/112/
17:23:06  *** andythenorth has joined #openttdcoop.devzone
17:34:07  <DevZone> Project Finnish Rail Infrastructure - Rails build #226-nightlies: SUCCESS in 8 min 21 sec: https://jenkins.openttdcoop.org/job/frissrails/226/
17:37:53  *** andythenorth has quit IRC
17:48:10  <DevZone> Project Iron Horse build #673-nightlies: SUCCESS in 1 min 22 sec: https://jenkins.openttdcoop.org/job/iron-horse/673/
18:06:23  <DevZone> Yippee, build fixed!
18:06:24  <DevZone> Project xussrset - Trains from Russia build #228-push: FIXED in 2 min 45 sec: https://jenkins.openttdcoop.org/job/xussrset/228/
18:25:05  <planetmaker> Taede, maybe let's brainstorm it here. If you're interested :)
18:27:40  <Taede> could make a dedicated script for that
18:28:02  <planetmaker> that was basically my question, yes
18:28:36  <planetmaker> I would then want to call that script dunno, every week or maybe every night and have it run one game for N years with 15 random AIs - and put the results somewhat in a table
18:28:46  <planetmaker> so that we can gather over time some statistics on AIs
18:29:00  <planetmaker> And give AI authors something to toy with / write for :)
18:30:01  <Taede> need to work out what ai-data i get over adminport
18:30:16  <planetmaker> I think it needs not many AI data other than name
18:30:43  <planetmaker> but well, yes
18:31:48  <Taede> well, crash reports
18:31:56  <Taede> and a way to find out first line n such
18:32:05  <planetmaker> they usually go to console output when you run openttd from console
18:32:12  <planetmaker> similar to other debug messages
18:32:49  <planetmaker> but, if that is not done via soap, we can probably get that differently, too. Directly from console
18:33:08  <planetmaker> if we run it through jenkins, we basically run openttd as 'compilation step'
18:33:15  <planetmaker> so we would get the whole output
18:34:20  <Taede> could run the script, which stays attached to the openttd while testing (like ap+, except the data still runs via adminport)
18:35:13  <planetmaker> wouldn't even need a script. We get all output https://jenkins.openttdcoop.org/job/2ccts/28/console
18:35:39  <planetmaker> but would be nicer to extract them to present them better
18:37:19  <planetmaker> hm... actually... we can grep that output in the post-processing step right there
18:38:50  *** Zuu has quit IRC
18:43:26  *** yorick has quit IRC
18:56:04  <DevZone> Project ISR Industrial Station Renewal build #110-push: SUCCESS in 22 sec: https://jenkins.openttdcoop.org/job/isr/110/
19:09:52  <planetmaker> so we have in beta4 some desync not related to 2ccTS.... I enabled desync debugging on stable server again
20:00:29  *** Alberth has left #openttdcoop.devzone
20:29:23  *** Elyon has quit IRC
21:05:23  *** ODM has joined #openttdcoop.devzone
21:54:53  *** ODM has quit IRC
22:09:50  *** frosch123 has quit IRC
22:19:02  *** oskari89 has quit IRC
23:52:18  *** yorick has joined #openttdcoop.devzone

Powered by YARRSTE version: svn-trunk