Config
Log for #openttdcoop.devzone on 5th November 2014:
Times are UTC Toggle Colours
01:18:42  *** Supercheese has joined #openttdcoop.devzone
02:13:38  *** George has quit IRC
07:01:22  *** LSky` has joined #openttdcoop.devzone
07:42:28  *** George has joined #openttdcoop.devzone
09:04:47  <DevZone> Project xussrset - Trains from Russia build #524-push: SUCCESS in 3 min 48 sec: https://jenkins.openttdcoop.org/job/xussrset/524/
10:30:35  <DevZone> Project xussrset - Trains from Russia build #525-push: SUCCESS in 3 min 37 sec: https://jenkins.openttdcoop.org/job/xussrset/525/
11:34:45  <DevZone> Project xussrset - Trains from Russia build #526-push: SUCCESS in 3 min 31 sec: https://jenkins.openttdcoop.org/job/xussrset/526/
12:37:27  *** Supercheese has quit IRC
13:51:32  *** frosch123 has joined #openttdcoop.devzone
16:45:47  *** Alberth has joined #openttdcoop.devzone
16:52:23  <DevZone> Project xussrset - Trains from Russia build #527-push: SUCCESS in 4 min 52 sec: https://jenkins.openttdcoop.org/job/xussrset/527/
16:54:50  <DevZone> Project FISH is ships build #341-push: SUCCESS in 2 min 27 sec: https://jenkins.openttdcoop.org/job/fish/341/
17:07:47  <DevZone> Project World Airliner Set build #539-push: FAILURE in 43 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/539/
17:12:14  <DevZone> Yippee, build fixed!
17:12:14  <DevZone> Project World Airliner Set build #540-push: FIXED in 3 min 19 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/540/
17:37:50  *** oskari89 has joined #openttdcoop.devzone
17:38:08  *** ODM has joined #openttdcoop.devzone
17:44:39  *** Zuu has joined #openttdcoop.devzone
18:35:11  <DevZone> Project World Airliner Set build #541-push: FAILURE in 28 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/541/
18:40:40  <DevZone> Project road-hog build #466-nightlies: SUCCESS in 39 sec: https://jenkins.openttdcoop.org/job/road-hog/466/
18:56:15  <DevZone> Yippee, build fixed!
18:56:15  <DevZone> Project World Airliner Set build #542-push: FIXED in 3 min 30 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/542/
19:03:05  <DevZone> Project World Airliner Set build #543-push: SUCCESS in 3 min 16 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/543/
19:10:39  *** andythenorth has joined #openttdcoop.devzone
19:12:50  <Alberth> o/
19:13:33  <DevZone> Project World Airliner Set build #544-push: SUCCESS in 3 min 58 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/544/
19:16:27  <DevZone> Project World Airliner Set build #545-push: FAILURE in 28 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/545/
19:17:32  <frosch123> http://devs.openttd.org/~frosch/diffs/nml/ <- add some more options for the info output
19:17:47  <frosch123> i am not happy with the name of the command line option though
19:17:58  <frosch123> "--detail", "--details", ...?
19:18:19  <frosch123> i do not like "--verbose" since that usually does not take a parameter
19:18:44  <frosch123> other options like --info-level, --detail-level feel too long
19:19:12  <frosch123> i am also not sure where to document the values for the integer :p
19:19:23  <frosch123> though we do not do that in ottd either, we just say more is more
19:21:56  <Alberth> I'd make constants   WARNING=1   INFO=2
19:22:59  <Alberth> you actually have a separate level for each type of message? I am confused by the "level = 2" in +def print_info(msg, level = 2):
19:23:24  <frosch123> not for now
19:23:32  <frosch123> at the end of the queue there are levels 1 to 4
19:23:43  <frosch123> 1 warnings, 2 info, 3 progress, 4 timing
19:24:00  <frosch123> constants would would, not sure whether we get different levels of info output
19:25:48  <DevZone> Yippee, build fixed!
19:25:48  <DevZone> Project World Airliner Set build #546-push: FIXED in 3 min 54 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/546/
19:26:28  <Alberth> --verbosity ?
19:27:14  <andythenorth> —debug-level
19:27:23  <andythenorth> —verboisty
19:27:24  <frosch123> it's not "debug"
19:27:56  <andythenorth> —spam
19:28:17  <andythenorth> I get complained at whenever I print shell output :|
19:28:25  <andythenorth> apparently you shouldn’t
19:28:39  <andythenorth> and a sensible person would simply mount the process with a debugger if they want output
19:28:45  * andythenorth is not a sensible person
19:28:48  <andythenorth> digressing also
19:30:08  <frosch123> andythenorth: do you not do continuous integration, with unit tests and fancy error rate plots at the end?
19:30:32  <andythenorth> apparently the continuous integration should mount a debugger
19:30:39  <frosch123> :)
19:30:40  * andythenorth is digressing
19:31:10  <andythenorth> also I do have a bad habit of printing things like ‘something worked'
19:31:12  <andythenorth> and timings
19:31:24  <andythenorth> viz. my newgrf compiles
19:31:26  <andythenorth> drives people mad
19:41:30  <Alberth> frosch123: for 00 I'd just hard-code different verbosity levels to compare against
19:41:43  <Alberth> unless I am failing to understand some point
19:42:50  <frosch123> the "level" parameter to print_info and print_progress is unused currently :)
19:42:59  <frosch123> i can remove it, if it adds confusion
19:43:16  <DevZone> Project World Airliner Set build #547-push: FAILURE in 33 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/547/
19:43:43  <Alberth> it's what is confusing to me
19:44:04  <Alberth> 01 the parentheses in the conditions are not actually needed
19:44:37  <frosch123> "is not None" looks quite confusing without ( ) to me :)
19:45:12  <Alberth> fair enough :)
19:45:21  <frosch123> i haven't quite figured out what "not" means in python
19:45:31  <Alberth> it takes a bit getting used to
19:45:34  <frosch123> is "a is not b" the same as "not a is b" ?
19:46:30  <Alberth> it's the same as "not (a is b)" at least, don't know the priority between "not" and "is"
19:46:54  <Alberth> but  not (a is b)  reads much less nice than a is not b
19:47:08  <frosch123> exactly my problem is "a is not b" :) why is it not "a is (not b)" :p
19:48:10  <DevZone> Project World Airliner Set build #548-push: STILL FAILING in 1 min 49 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/548/
19:49:33  <frosch123> so, i guess we go for "--verbosity"
19:50:09  <Alberth> given that it performs object identity checking "(not a) is b" would be useless :)
19:52:02  <Alberth> well, --verbosity seems to express what you want. I can live with --detail too, but you seem to not like that
19:53:07  <Alberth> the parentheses thing also holds for the normal expressions btw like (verbosity_level >= 4)  and a few others
19:54:16  <Alberth> 02  is quite luxury, printing elapsed time :)
19:54:27  *** Zuu has quit IRC
19:54:32  <frosch123> well, i had it as a debug patch for a while
19:54:41  <Alberth> I'd just dump current time in front of each line :)
19:55:08  <Alberth> it's nice and useful
19:55:36  <Alberth> although many people are a bit too focused on speed :p
19:55:40  <DevZone> Project World Airliner Set build #549-push: STILL FAILING in 24 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/549/
19:55:48  <andythenorth> which andythenorth complains about speed?
19:55:49  <andythenorth> :P
19:56:37  <Alberth> andy is one instance :p
19:57:20  <frosch123> well, i found a likely culprit for slow 32bpp encoding speed
19:57:23  <Alberth> you should writing code where you can do one test cycle every hour :)
19:57:31  <frosch123> after that the most pressing issue is cets memory usage
19:58:03  <frosch123> which is somewhat a mystery still
19:58:14  <Alberth> it is?
19:58:33  <DevZone> Project World Airliner Set build #550-push: STILL FAILING in 31 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/550/
19:58:45  <Alberth> if you look at the main program, it gets the main data structures, and builds parser objects etc
19:59:05  <Alberth> it stores them all in variables that stay in scope until the end of the main function
19:59:08  <frosch123> source is 9MiB, parsing result is 80MiB when pickles, but parsing actually allocated 1.4GiB when running
19:59:31  <frosch123> how does something that takes 80MiB when pickled, 1.4GiB in memory?
20:00:30  <frosch123> anyway, i think partial compilation is a good thing for everything
20:00:30  <andythenorth> ? http://effbot.org/pyfaq/why-doesnt-python-release-the-memory-when-i-delete-a-large-object.htm
20:00:31  <Webster> Title: Why doesn't Python release the memory when I delete a large object? (at effbot.org)
20:01:04  <frosch123> parallel compilation otoh not necessarily :p
20:01:15  <Alberth> sets and dicts eat a lot of memory in my experiences
20:01:21  <Alberth> *experience
20:02:02  <andythenorth> frosch123: all problems are made more interesting by multi-threading :P
20:02:17  <andythenorth> http://guillaume.segu.in/blog/code/487/optimizing-memory-usage-in-python-a-case-study/
20:02:21  <frosch123> yeah, if you lack problems, add parallelism
20:02:37  <Alberth> I think we have sufficient problems already :)
20:03:05  <andythenorth> I have already implemented loads of parallelism in my compiles :P
20:03:16  <andythenorth> didn’t have enough problems
20:04:21  <Alberth> frosch123: perhaps add a comment line about the meaning of progress_start_time and progress_update_time ?
20:04:34  <frosch123> good point
20:05:53  <DevZone> Project World Airliner Set build #551-push: STILL FAILING in 34 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/551/
20:11:39  <DevZone> Yippee, build fixed!
20:11:40  <DevZone> Project World Airliner Set build #552-push: FIXED in 5 min 4 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/552/
20:13:05  <Alberth> gn
20:13:35  <andythenorth> bye Alberth
20:13:55  *** Alberth has left #openttdcoop.devzone
20:25:47  <DevZone> Project xussrset - Trains from Russia build #528-push: SUCCESS in 6 min 1 sec: https://jenkins.openttdcoop.org/job/xussrset/528/
20:33:17  <DevZone> Project World Airliner Set build #553-push: SUCCESS in 5 min 19 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/553/
20:42:09  <DevZone> Project World Airliner Set build #554-push: SUCCESS in 5 min 57 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/554/
20:47:32  <DevZone> Project World Airliner Set build #555-push: SUCCESS in 5 min 22 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/555/
20:52:46  <DevZone> Project World Airliner Set build #556-push: SUCCESS in 5 min 13 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/556/
20:58:10  <DevZone> Project World Airliner Set build #557-push: SUCCESS in 4 min 13 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/557/
21:00:30  *** ODM has quit IRC
21:02:22  <DevZone> Project World Airliner Set build #558-push: SUCCESS in 4 min 11 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/558/
21:11:32  <DevZone> Project World Airliner Set build #559-push: SUCCESS in 4 min 13 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/559/
21:11:53  <DevZone> Project World Airliner Set build #560-push: FAILURE in 20 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/560/
21:13:46  <andythenorth> good old WAS
21:26:51  <DevZone> Yippee, build fixed!
21:26:51  <DevZone> Project World Airliner Set build #561-push: FIXED in 4 min 15 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/561/
21:27:30  <DevZone> Project yeti build #98-push: SUCCESS in 4 hr 39 min: https://jenkins.openttdcoop.org/job/yeti/98/
21:38:49  <DevZone> Project World Airliner Set build #562-push: SUCCESS in 3 min 59 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/562/
21:40:20  *** oskari89 has quit IRC
21:53:54  <DevZone> Project World Airliner Set build #563-push: SUCCESS in 4 min 4 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/563/
21:58:22  *** andythenorth has quit IRC
21:58:45  <DevZone> Project World Airliner Set build #564-push: SUCCESS in 3 min 54 sec: https://jenkins.openttdcoop.org/job/worldairlinersset/564/
21:59:21  *** LSky` has quit IRC
22:30:51  <DevZone> Project xussrset - Trains from Russia build #529-push: SUCCESS in 4 min 46 sec: https://jenkins.openttdcoop.org/job/xussrset/529/
23:01:02  *** frosch123 has quit IRC

Powered by YARRSTE version: svn-trunk