| --- Log opened Sat Feb 08 00:00:49 2014 | ||
| -!- sonne|osx [~sonne@e179077113.adsl.alicedsl.de] has joined #shogun | 06:38 | |
| @sonney2k | lisitsyn, could you please give us the full error http://buildbot.shogun-toolbox.org/memcheck/20140207-0059.html | 07:01 |
|---|---|---|
| @sonney2k | lisitsyn, otherwise it is too hard to fix issues | 07:01 |
| shogun-buildbot | build #44 of osx2 - python is complete: Success [build successful] Build details are at http://buildbot.shogun-toolbox.org/builders/osx2%20-%20python/builds/44 | 07:31 |
| shogun-buildbot | build #180 of clang34 - undefined behaviour analysis is complete: Failure [failed test] Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20undefined%20behaviour%20analysis/builds/180 blamelist: Soeren Sonnenburg <sonne@debian.org> | 07:48 |
| shogun-buildbot | build #175 of clang34 - thread analysis is complete: Failure [failed test] Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20thread%20analysis/builds/175 blamelist: Soeren Sonnenburg <sonne@debian.org> | 08:04 |
| shogun-buildbot | build #185 of debian wheezy - memcheck is complete: Failure [failed memory check] Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/185 blamelist: Soeren Sonnenburg <sonne@debian.org> | 08:37 |
| shogun-buildbot | build #190 of clang34 - static analysis is complete: Failure [failed analyse] Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20static%20analysis/builds/190 blamelist: Soeren Sonnenburg <sonne@debian.org> | 08:46 |
| -!- lambday [67157c4d@gateway/web/freenode/ip.103.21.124.77] has joined #shogun | 15:05 | |
| lambday | sonne|osx: hi! | 15:11 |
| lambday | sonne|osx: last year I used shogun for subsequent string kernel (for one of my class projects) - which is not in shogun yet.. I never sent a PR for that | 15:11 |
| lambday | sonne|osx: today I got a mail from someone who queried about that - do you think we can add this? | 15:12 |
| lambday | lol subsequence* | 15:18 |
| -!- lambday [67157c4d@gateway/web/freenode/ip.103.21.124.77] has quit [] | 16:17 | |
| -!- adrin [~adrin@guest-202.mpi-inf.mpg.de] has quit [Ping timeout: 250 seconds] | 17:04 | |
| -!- adrin [~adrin@guest-90.mpi-inf.mpg.de] has joined #shogun | 17:12 | |
| -!- zxtx [~zv@c-98-223-196-32.hsd1.in.comcast.net] has quit [Ping timeout: 250 seconds] | 20:20 | |
| @sonney2k | lisitsyn, ping? | 21:41 |
| lisitsyn | sonney2k: pong! | 21:41 |
| @sonney2k | lisitsyn, can you do anything about the no error shown xslt? | 21:42 |
| lisitsyn | sonney2k: yeah just wanted to do that | 21:42 |
| @sonney2k | lisitsyn, please do - we really need to get that stuff green before actual gsoc | 21:42 |
| lisitsyn | sonney2k: sure will do now | 21:43 |
| lisitsyn | sonney2k: the confusing part is that it will be a big error thing | 21:43 |
| -!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Quit: buildmaster reconfigured: bot disconnecting] | 21:44 | |
| -!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun | 21:44 | |
| @sonney2k | lisitsyn, show me | 21:45 |
| lisitsyn | sonney2k: give me half an hour | 21:45 |
| lisitsyn | ;) | 21:45 |
| @sonney2k | you have 5 minutes | 21:46 |
| @sonney2k | (that is what kirk is supposed to say) | 21:46 |
| @sonney2k | ok osx bot now works too | 21:49 |
| @wiking | sonney2k: ? | 21:49 |
| @wiking | sonney2k: what bot? :) | 21:49 |
| @sonney2k | wiking, http://buildbot.shogun-toolbox.org/builders/osx2%20-%20python | 21:49 |
| @wiking | ah u mean it went green :) | 21:49 |
| @wiking | i thought we've got an osx bot | 21:49 |
| @wiking | kudos for the fix | 21:50 |
| @wiking | sonney2k: what was the problem? | 21:50 |
| @sonney2k | wiking, floating points | 21:50 |
| @wiking | :< | 21:50 |
| @sonney2k | the way you compute how two floats are similar is far from trivial | 21:50 |
| @wiking | ok i owe one fix for the coveralls | 21:50 |
| @sonney2k | wiking, I just reconfigured the buildbot to create warnings not failues for the static analyze stuff | 21:51 |
| @sonney2k | wiking, one question - do you know if the wheezy memcheck will fail if we have only 'potential memory leaks'? | 21:52 |
| @sonney2k | wiking, ohh and good news we have the google cloud grant worth 1k$ | 21:52 |
| @sonney2k | wiking, so maybe if you have time you move the stuff from fatbot -> google cloud? | 21:53 |
| @wiking | sonney2k: account? | 21:54 |
| @wiking | and for how long a 1k usd will get us going ? | 21:54 |
| @sonney2k | wiking, no idea | 21:56 |
| lisitsyn | sonney2k: who am I supposed to send updated xslt? | 21:56 |
| @sonney2k | lisitsyn, could you give us some example output first maybe? | 21:56 |
| lisitsyn | yeah | 21:57 |
| @wiking | lisitsyn: just updated the gist | 21:57 |
| lisitsyn | wiking: https://gist.github.com/lisitsyn/8793002 | 21:58 |
| lisitsyn | updated | 21:58 |
| @sonney2k | wiking, just sent you an invitation | 21:58 |
| @wiking | sonney2k: got it, just trying to see what's this :) | 22:00 |
| @wiking | lisitsyn: sonney2k i've just updated the xslt... so the next build should generate the new output | 22:01 |
| lisitsyn | I don't mind to filter this output somehow | 22:01 |
| lisitsyn | but it is a trickery to do in xslt :D | 22:01 |
| @sonney2k | lisitsyn, could you just create an example please | 22:01 |
| @sonney2k | so we don't need to wait hours for each iteration? | 22:01 |
| lisitsyn | sonney2k: yeah let me upload it | 22:02 |
| lisitsyn | sonney2k: https://dl.dropboxusercontent.com/u/10139213/share/tmp/test.html | 22:03 |
| lisitsyn | damn | 22:03 |
| lisitsyn | it blocks htmls I guess | 22:03 |
| lisitsyn | https://dl.dropboxusercontent.com/u/10139213/share/tmp/test.html.txt | 22:04 |
| lisitsyn | sonney2k: please download and rename then open | 22:04 |
| @sonney2k | wiking, https://cloud.google.com/products/compute-engine/#pricing | 22:04 |
| @sonney2k | that's the prices | 22:04 |
| @sonney2k | wiking, so it is sth like 1$ per computing hour | 22:05 |
| @sonney2k | wiking, hard to reach if we don't do a cloud x-val project :D | 22:06 |
| @wiking | sonney2k: mmm i think they bill based on the online number of hours | 22:12 |
| @wiking | not the actual computing time or? | 22:12 |
| @sonney2k | looks like | 22:19 |
| @sonney2k | wiking, so choose sth that can last for ~100 days or so :) | 22:20 |
| @wiking | sonney2k: ok i'm just testing now | 22:21 |
| @wiking | btw where should the instance be | 22:21 |
| @wiking | us or eu? | 22:21 |
| @wiking | seems us is a bit cheaper | 22:21 |
| @wiking | ok cool this works nicely | 22:23 |
| @wiking | i'll shut down the instance now | 22:24 |
| @wiking | and i'll get back to continue hackint it later | 22:24 |
| shogun-buildbot | build #181 of clang34 - undefined behaviour analysis is complete: Failure [failed test] Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20undefined%20behaviour%20analysis/builds/181 blamelist: Soeren Sonnenburg <sonne@debian.org> | 22:33 |
| @sonney2k | multiclass ocas seems to be totally b0rken | 22:40 |
| @sonney2k | 66 uninited memory reads. wtf!? | 22:40 |
| @sonney2k | voila | 22:43 |
| @sonney2k | and fixed | 22:43 |
| @sonney2k | wiking, how can we require the osx test on the buildbot to work? | 22:44 |
| @sonney2k | wiking, it is currently allowing it to fail | 22:44 |
| lisitsyn | sonney2k: is html ok? | 22:45 |
| @sonney2k | lisitsyn, where is it? | 22:45 |
| lisitsyn | https://dl.dropboxusercontent.com/u/10139213/share/tmp/test.html.txt | 22:45 |
| @sonney2k | ahh sorry | 22:45 |
| @sonney2k | checking | 22:45 |
| @wiking | sonney2k: check the .travis.yml file ;) | 22:46 |
| @wiking | sonney2k: simply remove the lines that are for osx build from allow_failures part | 22:46 |
| @wiking | namely remove these two | 22:46 |
| @wiking | - language: objective-c env: OSX=1 | 22:46 |
| @wiking | which is just before | 22:47 |
| @wiking | virtualenv | 22:47 |
| @sonney2k | lisitsyn, would it be possible to add the failures in the short list so we have them at first glance? | 22:47 |
| @sonney2k | lisitsyn, the pull down stuff is nice though :) | 22:47 |
| @sonney2k | wiking, doing thanks | 22:48 |
| lisitsyn | sonney2k: what do you mean by that? | 22:48 |
| @sonney2k | lisitsyn, currently it lists only ./tests/unit/unit-MCLDA | 22:48 |
| @sonney2k | lisitsyn, woudl be nice if it said /tests/unit/unit-MCLDA (Potential Memory Leak (3)) | 22:48 |
| lisitsyn | ah okay easy | 22:49 |
| shogun-buildbot | build #176 of clang34 - thread analysis is complete: Failure [failed test] Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20thread%20analysis/builds/176 blamelist: Soeren Sonnenburg <sonne@debian.org> | 22:49 |
| @sonney2k | wiking, now since python works too on osx - could we not just build it on the osx bot too? | 22:50 |
| @sonney2k | ahh no I guess we need swig 2.0.12 / 3.0 | 22:51 |
| lisitsyn | sonney2k: https://dl.dropboxusercontent.com/u/10139213/share/tmp/test.html.txt | 22:53 |
| lisitsyn | wait wiat | 22:53 |
| lisitsyn | dropbox is having fun | 22:54 |
| lisitsyn | wiking: ich updated das xslt https://gist.github.com/lisitsyn/8793002 | 22:56 |
| @sonney2k | lisitsyn, ok fine! | 22:59 |
| @sonney2k | lisitsyn, now fix that malsar conditional memory read | 22:59 |
| @sonney2k | lisitsyn, then we only have one more critical in xml serialization | 23:00 |
| lisitsyn | sonney2k: it is not malsar that is buggy :D | 23:03 |
| lisitsyn | but a test | 23:03 |
| lisitsyn | I am seeing the code and wondering if I was drunk or what | 23:03 |
| @sonney2k | lisitsyn, then fix it :D | 23:08 |
| lisitsyn | yeah sure | 23:08 |
| lisitsyn | makes sense | 23:08 |
| @sonney2k | lisitsyn, and of course the answer is yes | 23:08 |
| lisitsyn | :D | 23:08 |
| @sonney2k | you are Russian | 23:08 |
| @sonney2k | my guess is that maybe you were not drunk | 23:08 |
| @sonney2k | so no wonder... | 23:09 |
| lisitsyn | sonney2k: didn't we have some work on compilation speedup by besser82? | 23:09 |
| lisitsyn | how did it end? | 23:09 |
| @sonney2k | lisitsyn, not ready - will be a gsoc project | 23:09 |
| @sonney2k | lisitsyn, but you need libshogun only | 23:09 |
| lisitsyn | I know | 23:09 |
| @sonney2k | and that is pretty fast anyway | 23:10 |
| lisitsyn | just curious | 23:10 |
| lisitsyn | yeah once parallel it is | 23:10 |
| @sonney2k | man what a crap - we need to get rid of this useless use of SG_UNSTABLE | 23:11 |
| @sonney2k | cluttering stuff with useless warnings doesn'thelp | 23:11 |
| @sonney2k | wiking, any idea what this NON-XML-CHAR stuff in serialization xml tests is about [NON-XML-CHAR-0x1B][1;34m[WARN][NON-XML-CHAR-0x1B][0m In file /home/buildslave/debian_wheezy_-_memcheck/build/src/shogun/structure/DisjointSet.cpp line 19: /home/buildslave/debian_wheezy_-_memcheck/build/src/shogun/structure/DisjointSet.cpp:CDisjointSet::CDisjointSet(): | 23:12 |
| shogun-buildbot | build #186 of debian wheezy - memcheck is complete: Failure [failed memory check] Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/186 blamelist: Soeren Sonnenburg <sonne@debian.org> | 23:16 |
| shogun-buildbot | build #191 of clang34 - static analysis is complete: Failure [failed analyse] Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20static%20analysis/builds/191 blamelist: Soeren Sonnenburg <sonne@debian.org> | 23:37 |
| @sonney2k | we have a problem when serializing XML - inf values cause valgrind errors / issues | 23:43 |
| @sonney2k | serializing AS xml | 23:43 |
| -!- travis-ci [~travis-ci@ec2-50-19-161-94.compute-1.amazonaws.com] has joined #shogun | 23:46 | |
| travis-ci | [travis-ci] it's Soeren Sonnenburg's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/18496123 | 23:46 |
| -!- travis-ci [~travis-ci@ec2-50-19-161-94.compute-1.amazonaws.com] has left #shogun [] | 23:46 | |
| --- Log closed Sun Feb 09 00:00:51 2014 | ||
Generated by irclog2html.py 2.10.0 by Marius Gedminas - find it at mg.pov.lt!