Open in new window / Try shogun cloud
--- Log opened Wed Jan 08 00:00:42 2014
-!- pickle27 [~kevin@192-0-136-118.cpe.teksavvy.com] has joined #shogun01:24
pickle27hey did you guys see https://github.com/blog/1672-introducing-github-traffic-analytics01:24
pickle27what does shogun traffic look like?01:24
-!- Saurabh7 [~Saurabh7@117.200.177.85] has joined #shogun02:24
-!- Saurabh7 [~Saurabh7@117.200.177.85] has quit [Client Quit]02:25
-!- pickle27 [~kevin@192-0-136-118.cpe.teksavvy.com] has quit [Quit: Leaving]03:18
gsomixgood morning03:38
-!- gsomix [~gsomix@46.20.65.114] has quit [Remote host closed the connection]04:31
-!- besser82 [~quassel@fedora/besser82] has quit [Remote host closed the connection]04:35
-!- besser82 [quassel@fedora/besser82] has joined #shogun04:52
-!- besser82 [quassel@fedora/besser82] has quit [Ping timeout: 240 seconds]07:08
-!- besser82 [quassel@fedora/besser82] has joined #shogun07:14
besser82sonney2k, sonne|work: ping!07:39
-!- lisitsyn [~lisitsyn@213.87.139.68] has joined #shogun08:43
-!- lisitsyn [~lisitsyn@213.87.139.68] has left #shogun []08:56
-!- gsomix [~gsomix@185.6.237.115] has joined #shogun08:58
gsomixpassed08:58
besser82gsomix:  congrats!09:06
sonne|workgsomix: cool!09:30
sonne|workgsomix: so now you are free?09:30
sonne|workbesser82: hey!09:30
sonne|workbesser82: can you do the include order thing for adrin?09:31
sonne|workbesser82: I mean just adding the include?09:31
besser82sonne|work:  working on that; it seems to be a bit more complicated, than just adding that...09:37
besser82sonne|work:  I'm currently tracking the way all includes get stacked into the CMake-vars...09:37
besser82sonne|work:  Since we need to make sure it *always* is the first one09:38
sonne|workyeah. is it not that you can just put it in th einclude_dirs first?09:39
sonne|workbesser82: or is cmake reordering things?09:39
besser82sonne|work:  it's mot just cmake; it's way the CMakeLists are setup09:39
sonne|workbesser82: not sure what you mean?09:40
besser82sonne|work:  someone who did the include-stuff actually PREpends all the new includes to the global-var09:41
sonne|workbesser82: ohh I see09:41
besser82sonne|work:  like set( INCLUDES "newshit" ${INCLUDES})  ;)09:41
sonne|workbesser82: that is the way I did it in configure back then09:41
sonne|workmaybe09:41
sonne|workdon't remember09:41
sonne|workso I guess it is a result of that09:41
besser82sonne|work:  I possibly found a solution...  lemme check...09:46
besser82sonne|work:  but that is not gurateed to work with *all* compilers...09:46
-!- lisitsyn [~lisitsin@mxs.kg.ru] has joined #shogun09:46
sonne|workbesser82: what do you do?09:46
besser82sonne|work:  Trying to inject INCLUDE_DIRECTORIES( ${CMAKE_SOURCE_DIR}/src ${CMAKE_BINARY_DIR}/src ) into toplevel cmake...09:47
besser82sonne|work:  that should make sure they are set *BEFORE* any other include...09:48
sonne|workok09:48
besser82sonne|work:  looks like it works....09:56
besser82sonne|work:  lemme do some cleanups && push09:56
besser82sonne|work:  shall i push directly to `develop` to use featurebranch && PR?09:57
besser82sonne|work:  s/to/or/09:57
besser82sonne|work:  would actually just be one commit, so easily revertable...09:58
besser82sonne|work:  ready2go!  patch worxxx10:23
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun10:26
shogun-notifier-shogun: Bj?rn Esser :feature/fix-include-order * f100688 / / (10 files): https://github.com/shogun-toolbox/shogun/commit/f1006885ccad27456a71d75f014aa918b807cc3110:26
shogun-notifier-shogun: fix include-order to fix build when shogun-headers present in system-dirs10:26
sonne|workbesser82: errm PR?10:48
besser82sonne|work: here ya go!  https://github.com/shogun-toolbox/shogun/pull/181110:54
sonne|workbesser82: ok lets wait for travis and then we merge :)10:55
-!- travis-ci [~travis-ci@ec2-54-234-109-127.compute-1.amazonaws.com] has joined #shogun11:02
travis-ci[travis-ci] it's Bj?rn Esser'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/1657835811:02
-!- travis-ci [~travis-ci@ec2-54-234-109-127.compute-1.amazonaws.com] has left #shogun []11:02
shogun-notifier-shogun: Bj?rn Esser :develop * f100688 / / (10 files): https://github.com/shogun-toolbox/shogun/commit/f1006885ccad27456a71d75f014aa918b807cc3111:03
shogun-notifier-shogun: fix include-order to fix build when shogun-headers present in system-dirs11:03
shogun-notifier-shogun: Soeren Sonnenburg :develop * f751978 / / (10 files): https://github.com/shogun-toolbox/shogun/commit/f7519783e6366b737a098f06cf3b66f35bf1ae2b11:03
shogun-notifier-shogun: Merge pull request #1811 from shogun-toolbox/feature/fix-include-order11:03
shogun-notifier-shogun:11:03
shogun-notifier-shogun: fix include-order to fix build when shogun-headers present in system-dirs11:03
sonne|workbesser82: thanks a lot11:04
sonne|workadrin_: give it a try besser82 likely fixed your issue.11:04
besser82sonne|work:  np  ;)11:05
sonne|workbesser82: btw I was messing with debian shogun python package11:05
besser82sonne|work:  kaputt?11:05
sonne|workbesser82: it is tough ... trying to build for python 3 / 2 at once11:05
besser82sonne|work:  you simply need different build/-dirs11:06
besser82sonne|work:  like cd build && cmake ..  and cd build-py3 && cmake ...11:06
sonne|workbesser82: in debian that is all automagic11:07
besser82sonne|work:  but does python3-interfaces really work?!?11:07
besser82sonne|work:  is it?11:07
sonne|workbesser82: gsomix fixed things up - so they should11:07
besser82sonne|work:  with units?11:07
besser82sonne|work:  erm...  testing?11:07
sonne|workmight be that we have a few python2 things in notebooks though11:07
sonne|worknot tested11:07
besser82sonne|work:  gna11:08
besser82sonne|work:  no tests, no fedora / RHEL11:08
besser82sonne|work:  are you really forced to use all debhelper automagic in debian?!?11:09
sonne|workbesser82: gna?11:09
sonne|workbesser82: I better do11:09
sonne|workbesser82: well notebooks are run at night for python2 but not 3 - actually nothing is run for python3 yet11:09
besser82sonne|work:  gna like damn it  ;)11:09
sonne|workwiking: any chance you have time to set that up?11:09
sonne|workbesser82: gna like urgs11:09
sonne|workkk11:09
besser82sonne|work:  set what up?11:10
besser82sonne|work:  nb && stuff for py3?11:10
besser82sonne|work:  Testing stuff is more important  :-P11:10
sonne|workbesser82: well our buildbot could just get another py3 test11:10
sonne|workno we have the tests11:10
sonne|workwe just need to run everything with py3 installed11:10
sonne|workbesser82: I mean there is no difference - you just need to install python3 and compile11:10
besser82sonne|work:  I see;  lemme try that on Fedora buildzzz  ;)11:10
@wikingsonne|work: what?11:11
sonne|workquestion is whether we broke everything11:11
besser82sonne|work:  :D11:11
sonne|workwiking: a separate buildbot test for python311:11
besser82sonne|work:  That's what scratch builds good for  :-P11:11
@wikingsonne|work: it's in travis11:11
sonne|workwiking: can we also have it on the buildbot please so we can compile notebooks too?11:11
@wikingsonne|work: no11:12
@wikingno time for that sorry11:12
@wikingof course if anyboyd else has time for it go for it11:12
@wikingbut python3 doesnt work at all11:12
@wikingit needs extensial amount of work to get it compiling ...11:12
sonne|workwiking: why that? it did work with the configure a year back11:13
besser82wiking:  will it?11:13
@wikingsonne|work: it did not ever work11:13
besser82wiking:  swig should do all the needed workz  ;)11:13
sonne|workwiking: it did -  gsomix fixed things up and we had it in release notes IIRC for 2.011:13
@wikingsonne|work: the thing that it compiled does not mean that it worked11:13
@wikingyes it compiled11:13
sonne|workwiking: no he could run *all* examples11:13
@wikinghave u tried running examples?11:13
@wikingwell see travis bot11:13
sonne|workhe fixed up the examples11:14
sonne|worktravis py3 bot doesn't run11:14
@wikingagain. see travis bot's output11:14
sonne|worklike not at all11:14
sonne|worknot even attempting to compile11:14
besser82sonne|work, wiking: the problem on travis is, that it cannot build e.g. numpy  ;)11:16
besser82sonne|work, wiking: that would need work11:16
besser82sonne|work, wiking: lemme check the py3 stuff with some fedora-scratch-builds  ;)11:17
sonne|workbesser82: yeah but on debian / fc we have python3-numpy already11:17
@wikingbesser82: u mean scipy11:17
@wikingbesser82: and u mean that it runs out of lines ...11:17
@wikingright?11:17
besser82wiking: yes11:17
@wikingwhat's the new empty 'allowed to failed' build doing?11:21
@wikingis that clang?11:21
@wikingbtw the problem is that now it doesn't use the wheel packages11:21
@wikingwhich i dont really get because they are there11:21
@wikingso the thing is that this should install numpy and scipy from whl package instead of trying to compile it from src11:22
@wikingbut this has changed recently seems11:22
@wikingas it worked in the past11:22
@wikingbesser82: any ideas for that?11:26
@wikingok i think i know why11:28
besser82wiking:  compile failes, because the is not FORTRAN-compiler present  ;)11:32
@wikingbesser82: no it's not that11:32
@wikingbesser82: as said above i dont want it to compile it from source11:32
@wikingi want it to isntalling it from wheel package11:33
besser82wiking:  no idea about that, currently...11:35
besser82wiking:  lemme check after I tried to scratch build on fedora11:35
shogun-notifier-shogun: Viktor Gal :develop * d231b47 / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/d231b47469d3c92b3ca8ae15b30e1aee8b103d8e11:36
shogun-notifier-shogun: Upgrade pip to 1.5 for python3 job11:36
@wikingthis might do the trick11:36
@wikingok there u go12:08
@wikinghttps://travis-ci.org/shogun-toolbox/shogun/jobs/1658156012:08
@wikingand here are the fails:12:09
@wikinghttps://travis-ci.org/shogun-toolbox/shogun/jobs/16581560#L466212:09
@wikingthe factor graph error can be fixed with 2to312:10
@wikingas well as mathematics_logdet12:11
shogun-notifier-shogun: Viktor Gal :develop * 56e3fa9 / examples/undocumented/python_modular/ (4 files): https://github.com/shogun-toolbox/shogun/commit/56e3fa953aa630f111178fe96101b1687043c7b112:19
shogun-notifier-shogun: 2to3 fixes for python examples12:20
besser82wiking:  there is another problem  ;)12:45
besser82wiking:  the tests should be run with some py3 interp12:45
besser82wiking:  currently we are using the py2 interp when running them  ;)12:47
besser82wiking:  and to get all shiatz running with a py3 interp, we need to fix / change some more bits...12:48
besser82wiking:  like da scriptlet in Version.cmake and doxy2swig12:49
-!- travis-ci [~travis-ci@ec2-50-16-165-187.compute-1.amazonaws.com] has joined #shogun12:49
travis-ci[travis-ci] it's Viktor Gal'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/1658155612:49
-!- travis-ci [~travis-ci@ec2-50-16-165-187.compute-1.amazonaws.com] has left #shogun []12:49
besser82sonney2k, sonne|work:  ^^^12:50
@wikingbesser82: https://travis-ci.org/shogun-toolbox/shogun/jobs/16583442#L51813:02
@wikingbesser82: it works on travis13:02
@wikingbesser82: but as u can see examples fail13:02
besser82wiking:  yes, all errors boil down to "one simply cannot use py3-compiled.so with py2 interp"  :-P13:06
@wikingbesser82: ?13:07
besser82wiking:  like da stuff about pickle'ing and such13:07
@wikingthat thing there uses python 3.3 both for interpreter and library13:07
besser82wiking:  nope13:07
besser82wiking:  the is *always* python2 in minimal inst of ubuntu / debian13:08
@wikingi guess this is why it says13:08
@wiking-- Found PythonLibs: /usr/lib/libpython3.3m.so (found version "3.3.3")13:08
@wikingand13:08
@wiking-- Found PythonInterp: /home/travis/virtualenv/python3.3_with_system_site_packages/bin/python (found version "3.3.3")13:09
@wikingbesser82: that travis task is not a minimum installed ubuntu13:09
@wikingor debian13:09
@wikingit's actually a modded install by travis to have python 3.313:09
@wiking...13:09
@wikingso it's not because of different version of python lib and interperter13:10
@wikingthat's why actually there's an enforcer for this in cmakelists13:10
besser82wiking:  lemme check twice in my setup  ;)13:11
@wikingbesser82: well regardless of your setup13:11
@wikingthe thing that fails in that travis task13:11
@wikingis not because of what u said ...13:11
@wikingit's just because there's a problem currently supporting 3.3 with shogun13:11
@wikingbesser82: i've been working with this like for 2 months back in summer so i know what were then the problems and they still remains as nobody touched it13:12
besser82wiking:  then we should split off the module to python3_modular  ;)13:20
besser82wiking:  or sth13:20
besser82wiking:  to make use of the `-py3` switch in swig13:20
@wikingbesser82: u realised that we use that... right?13:21
besser82wiking:  nope, because travis doesn't use verbose make  :(13:22
besser82wiking:  and don't know any specific bits of the cmakelists  ;)13:22
@wikingbesser82: obviously as there is the max 10000 lines log limit on travis13:23
@wikingbesser82: git grep "-py3"13:23
@wikingor git grep "\-py3"13:25
besser82wiking:  alright seen it  ;)13:25
@wikingso it has nothing to do with either of the stuff you've mentioned.... it's just because there are stuff that are not python3 ready both in swig generated interface and some of the scripts (see python_modular integration tests)13:27
besser82wiking:  nevertheless:  doxy2swig will fail with py3, too13:28
@wikingbesser82: well that's the least of our concerns13:29
@wikingas that is some documentation problem and not functional bug13:29
besser82wiking:  and version.cmake, too, when building from release-tarball  ;)13:29
@wikingas said13:30
@wikingleast of our problems concerning python313:30
besser82wiking:  kk13:30
@wikingcurrently it fails functionally.. until that is not fixed13:30
@wikingpython3 is just out of the story13:30
@wikingnow that to support doxy2swig and release tarball13:31
@wikingthat's like doable within 10 minutes13:31
@wikingthe others hardly13:31
-!- lisitsyn1 [~lisitsin@mxs.kg.ru] has joined #shogun13:39
-!- lisitsyn [~lisitsin@mxs.kg.ru] has quit [Read error: Connection reset by peer]13:39
besser82wiking:  https://travis-ci.org/shogun-toolbox/shogun/jobs/16583442#L4356 ---> file = BytesIO(str)13:45
besser82wiking:  the pickle problem seem to be caused by "nested" classes....13:46
shogun-notifier-shogun: Bj?rn Esser :feature/improved_python3_support * 45a809e / examples/undocumented/python_modular/structure_dynprog_modular.py: https://github.com/shogun-toolbox/shogun/commit/45a809e3f60dbe37bb39c0a3c463a983f0b8e91814:07
shogun-notifier-shogun: fix structure_dynprog_modular for Python314:07
gsomixpython3 makes me sad14:16
besser82gsomix:  :/  We all want to have support for it, but...14:46
besser82wiking, sonne|work:  ^^^  With that patch structure_dynprog now fails for another, pickle-releated reason  ;)  Shall I merge?!?14:47
besser82wiking, sonne|work:  https://travis-ci.org/shogun-toolbox/shogun/jobs/16587844#L440914:47
sonne|workgsomix: what do you mean?14:48
besser82sonne|work, wiking: for comparison, prev. build:  https://travis-ci.org/shogun-toolbox/shogun/jobs/16583442#L435614:49
besser82sonne|work:  I thinks, he moans about non-ffwd-porting  ;)14:49
sonne|workbesser82: really just 4 tests fail?!14:50
besser82sonne|work:  nope still 5, but the "fixed" one for another reason  ;)14:51
sonne|workwell so few?14:51
sonne|workI am surprised that it basically works14:51
besser82sonne|work:  I'm not; since swigzzz should be able to hack it  ;)14:52
besser82sonne|work:  the only probs with that are now 5 examples / tests, doxy2swig, version.cmake  AFAIK14:53
shogun-notifier-shogun: Bj?rn Esser :develop * 45a809e / examples/undocumented/python_modular/structure_dynprog_modular.py: https://github.com/shogun-toolbox/shogun/commit/45a809e3f60dbe37bb39c0a3c463a983f0b8e91814:56
shogun-notifier-shogun: fix structure_dynprog_modular for Python314:56
gsomixsonne|work, I mean, something related to python3 support always breaks. that makes me sad14:58
sonne|workgsomix: yeah simply because we didn't enable test runs when you finally got it all working14:58
sonne|workgsomix: but we will now14:58
sonne|workand then it is solved14:59
-!- travis-ci [~travis-ci@ec2-23-22-190-94.compute-1.amazonaws.com] has joined #shogun14:59
travis-ci[travis-ci] it's Bj?rn Esser'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/1658784014:59
-!- travis-ci [~travis-ci@ec2-23-22-190-94.compute-1.amazonaws.com] has left #shogun []14:59
gsomixsonne|work, so now you are free? | yep, free. but not as free beer :)15:00
gsomixsonne|work, ok then.15:00
sonne|workbesser82: sure merge then15:00
besser82sonne|work:  done  :D15:00
sonne|workgsomix: ok free beer then give us matlab :D15:02
@wikingbesser82: sonne|work there's a problem with swig generated interface and pickle15:04
-!- adrin_ [~adrin@guest-202.mpi-inf.mpg.de] has quit [Quit: Leaving]15:05
-!- adrin [~adrin@guest-202.mpi-inf.mpg.de] has joined #shogun15:06
besser82wiking, sonney2k: haha, got that pickle shiatz-reason  ;)15:13
besser82wiking, sonney2k: py3-pickle  == py2 cPickle  ;)15:13
besser82wiking, sonney2k: so py3-pickle != py2 pickle  :-P15:13
besser82wiking, sonney2k:  try to find a workaround  ;)15:14
besser82wiking, sonney2k:  ^^ I'll15:14
@wikingbesser82: mmm wonder why integration tests never cry about that15:22
besser82wiking: because it is *mostly* compat15:23
besser82wiking: just some corner-cases are not compatible15:23
besser82wiking: and for those I'm digging up a workaround15:24
adrinHey guys, I just wanted to confirm that the package is successfully compiled on my server. Thanks :-)15:27
besser82adrin:  nice to hear  :D15:27
besser82adrin:  Freut mich  :D15:27
-!- bb_ [458fc8de@gateway/web/freenode/ip.69.143.200.222] has joined #shogun15:28
adrinI hope I can give you a hand in near future and pay back.15:28
besser82adrin:  I think with the 2to3ized doxy2swig you helped us a lot  ;)15:29
besser82wiking:  got a pickle workaround, lets see if it works15:29
@wikingpr it15:29
@wikingand travis will tell15:29
adrinbesser82: you're most welcome :-)15:30
besser82wiking:  I'm on it and will push to featurebranch asap  ;)15:30
besser82adrin:  :D15:30
sonne|workadrin: hurray :D15:36
sonne|workbesser82: I would always use cPickle then - it is just muuuuch faster15:37
adrinsonne|work: yeah it really does deserve a hurray for me :D15:37
besser82sonne|work: but has some flaws15:37
besser82sonne|work: like no Unpickler.dispatch  ;)15:37
besser82sonne|work: and problems (I assume) with those SVM^shit stuff15:38
sonne|workbesser82: no that is just a very complex serialization example15:38
sonne|workbesser82: if something breaks then that15:38
besser82sonne|work: 4 in a row?  all related to SVM^shit15:39
sonne|workbesser82: relax not all TJ's fault15:39
besser82sonne|work: nuthing about TJ in that particular, just Py3 changes  :-P15:40
besser82sonne|work: It is just suspicious...15:41
besser82sonne|work: I assume this is related to neseted classes, which in fact are a no-go for cPickle  ;)15:41
sonne|workno no15:53
sonne|workshould all work15:53
-!- lisitsyn1 [~lisitsin@mxs.kg.ru] has quit [Quit: Leaving.]16:14
besser82sonne|work:  ??? ^^^   btw.  Who created pickles with "LATIN-1" encoded strings?!?!?16:14
sonne|workwhat?16:15
besser82sonne|work:  that `DynProg_example_py.pickle.gz` has latin-1 encoded shit in it  :S16:15
besser82sonne|work:  and what was that about "no no should all work" ?!?16:20
sonne|workbesser82: c'mon these are just some legacy crap examples16:25
besser82sonne|work: so we shall purge them?!?16:25
sonne|workno16:25
besser82sonne|work: but?!?16:25
sonne|workwell we fix them16:26
besser82sonne|work: hahaha,  guess what I'm doing  :-P16:26
sonne|workbut these are like <0.1% of shogun16:26
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]17:56
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun18:27
shogun-notifier-shogun: Bj?rn Esser :feature/improved_python3_support * 2186913 / examples/undocumented/python_modular/structure_dynprog_modular.py: https://github.com/shogun-toolbox/shogun/commit/2186913d989ad4be0272a58a0aa4a82b17e9cd7718:27
shogun-notifier-shogun: finally Python3ized, hopefully18:27
besser82sonney2k, sonne|work, wiking: let's-a-wait 4 Travis18:27
besser82sonney2k, sonne|work, wiking: that should fix Pickles in one case18:27
besser82sonney2k, sonne|work, wiking: If that w0rkz, I'll adapt that to the other examples as well  ;)18:28
besser82gsomix, adrin:  ^^^18:30
besser82sonney2k, sonne|work, wiking, gsomix, adrin: that thing was a tough maze to solve  ;)18:31
besser82sonney2k, wiking: It failed again  :(  But at least for another reason  ;)18:51
-!- FSCV [~FSCV@50.7.50.60] has joined #shogun18:53
shogun-notifier-shogun: Bj?rn Esser :feature/improved_python3_support * 1c1a78e / examples/undocumented/python_modular/serialization_svmlight_modular.py: https://github.com/shogun-toolbox/shogun/commit/1c1a78e37de38c23d97d086a563d881145a46b0219:05
shogun-notifier-shogun: hopefully fixed serialization_svmlight_modular19:05
-!- naywhayare [~ryan@spoon.lugatgt.org] has quit [Ping timeout: 252 seconds]19:15
-!- iglesiasg [~iglesiasg@524AE0A7.cm-4-3d.dynamic.ziggo.nl] has joined #shogun19:16
-!- mode/#shogun [+o iglesiasg] by ChanServ19:16
@iglesiasgsup guys19:17
-!- naywhayare [~ryan@spoon.lugatgt.org] has joined #shogun19:17
besser82iglesiasg:  Heyya!19:43
besser82iglesiasg:  Wassup?  Does da Javazzz run?19:43
@iglesiasgbesser82, yesterday it didn't seem to compile when BUILD_EXAMPLES is ON19:43
besser82iglesiasg:  try with recent checkout...19:44
besser82iglesiasg:  for me && buildbot && travis it builds19:44
besser82iglesiasg:  me is currently on doing all the left-over stuff for da Python319:44
@iglesiasgbesser82, were there changes on that from yesterday?19:45
besser82iglesiasg:  yes19:45
@iglesiasgbesser82, let me try with current develop then..19:46
-!- gsomix [~gsomix@185.6.237.115] has quit [Remote host closed the connection]19:52
-!- gsomix [~gsomix@185.6.237.115] has joined #shogun19:59
-!- thoralf [~thoralf@91-65-138-245-dynip.superkabel.de] has joined #shogun20:06
thoralfHey hackers.20:06
besser82thoralf:  Heyya!!!20:11
besser82thoralf:  happy new year!!!20:11
thoralfOh, yes.  Happy new fear! ;)20:12
@iglesiasgbesser82, still broken20:15
@iglesiasgbesser82, now I had BUILD_EXAMPLES=OFF20:15
@iglesiasgbesser82, https://gist.github.com/iglesias/832266220:18
besser82iglesiasg:  which SWIG_ver do you use?20:20
besser82sonney2k:  ping?20:20
besser82wiking:  ping?20:21
@iglesiasgbesser82, 2.0.420:21
besser82iglesiasg:  might be related to that, possibly...20:21
@iglesiasgok20:21
besser82iglesiasg:  me was trying with 2.0.8 && 2.0.11  which both worked20:21
@iglesiasgbesser82, I think travis uses ubuntu 12.04 as well20:22
@iglesiasgbesser82, and this is the SWIG in the repositories I believe20:22
besser82iglesiasg:  lemme check travis...20:22
besser82iglesiasg:  indeed 2.0.420:23
besser82iglesiasg:  on travis20:23
besser82iglesiasg:  lokks like there is sth. br0k3n on your sys...20:23
@iglesiasgbesser82, ok.. I can live with that. Not interested at this moment of using java for this :)20:24
besser82iglesiasg:  can you try with a clean VM, plz?20:24
besser82iglesiasg:  kk20:24
@iglesiasgbesser82, I can try with the OpenJDK and we can find out if it is related to using Oracle Java20:24
@iglesiasgalthough I guess it has nothing to do with that due to the type of error20:25
@iglesiasgso I think I will just forget about it20:25
besser82iglesiasg:  buildbot.shogun uses ShitracleJDK  and has no error   ;)20:25
besser82iglesiasg:  If you don't need java atm then let's forget20:26
besser82sonney2k, wiking: what might this shiatz be related to?  https://travis-ci.org/shogun-toolbox/shogun/jobs/16605587#L462220:27
-!- naywhayare [~ryan@spoon.lugatgt.org] has quit [Ping timeout: 252 seconds]20:34
-!- naywhayare [~ryan@spoon.lugatgt.org] has joined #shogun20:35
-!- travis-ci [~travis-ci@ec2-50-16-20-105.compute-1.amazonaws.com] has joined #shogun20:40
travis-ci[travis-ci] it's Bj?rn Esser'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/1660558320:40
-!- travis-ci [~travis-ci@ec2-50-16-20-105.compute-1.amazonaws.com] has left #shogun []20:40
@sonney2kbesser82, what did I miss?21:01
@sonney2kHey thoralf! Happy new year to you too!21:01
thoralf:)21:01
@sonney2kHOpe to see you around next monday too!21:01
thoralfsonney2k: In IRC or somewhere in real life?21:02
thoralfHybrid virtual meeting ;)21:02
@sonney2kthoralf, I have to be here doing kids babysitting21:03
@sonney2kso no way to escape to c-base or so21:03
thoralfToo bad.  I'll see what I can do. :)21:09
thoralfWould be a good chance to push my other uncommitted changes...21:09
-!- pickle27 [d8bfe7da@gateway/web/freenode/ip.216.191.231.218] has joined #shogun21:19
pickle27do we have links to the build bots anywhere? I can never remember how to get to that page21:23
@sonney2kpickle27, sure sure21:23
@sonney2kpickle27, and hey happy new year too :)21:23
@sonney2kpickle27, buildbot.shogun-toolbox.org21:23
pickle27yes happy new year!21:24
@sonney2kpickle27, btw we now have the sgt.eu domain too21:24
pickle27maybe we should put a link to that page on the contact page21:25
@sonney2kpickle27, so we can do things like  http://sgtb.eu/SVM21:26
@sonney2kpickle27, as shortlinks for documentation that you can use in your notebooks for example21:26
pickle27handy!21:26
@sonney2kpickle27, I should actually make buildbot.sgtb.eu work too21:27
@sonney2kpickle27, voila http://buildbot.sgtb.eu/21:34
@sonney2kthoralf, yeah it would be nice to have these all in...21:34
pickle27nice!21:34
@sonney2kpickle27, if you have time to help out with the website I can give you access to it21:43
pickle27hmmm I probably won't have time to do much21:52
@sonney2kpickle27, then feedback - where you would expect what on the website at least please :)21:55
pickle27I was thinking on the contact page21:55
pickle27anywhere really21:55
pickle27or a new tab for status?21:56
@sonney2kpickle27, contact page? what do you suggest?21:57
@sonney2kpickle27, and what should status do?21:57
pickle27maybe have a status header after Mailing List and place links to the buildbot and travis CI21:58
@sonney2kpickle27, we currently have that under doc: http://sgtb.eu/page/documentation/resources21:59
pickle27ahh then that answers my original question21:59
@sonney2kpickle27, well if you cannot find it who can...22:00
pickle27hmmm maybe we should have a documentation tab like we do and a developer tab22:00
pickle27and put that page there22:01
pickle27we might be able to consolidate news and events to make room22:02
pickle27I could mess around on a fork of shogun web22:03
pickle27and take some screens22:03
pickle27there is a way to run the site locally yes?22:03
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Quit: buildmaster reconfigured: bot disconnecting]22:04
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun22:04
@sonney2kshogun-buildbot, force build 'deb4 - python3'22:04
shogun-buildbotbuild #0 forced22:04
shogun-buildbotI'll give a shout when the build finishes22:04
pickle27just looked at so yeah I'll play around with it22:04
@sonney2kpickle27, yeah problem is the content is in a database22:05
@sonney2kpickle27, and on the server it is in mysql / locally sqlite22:05
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]22:05
@sonney2kand no idea how to convert between them22:05
pickle27I should be able to do some re-org without all the content though22:06
@sonney2kpickle27, anything more clean structure wise is highly appreciated22:09
@sonney2kpickle27, even if it is just a plan22:09
pickle27okay I'll see what I come up with!22:09
pickle27simple is good too!22:09
shogun-buildbotbuild #0 of deb4 - python3 is complete: Failure [failed python static]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/022:11
-!- pickle27 [d8bfe7da@gateway/web/freenode/ip.216.191.231.218] has quit [Quit: Page closed]22:41
-!- bb_ [458fc8de@gateway/web/freenode/ip.69.143.200.222] has quit [Ping timeout: 272 seconds]22:43
@sonney2kbesser82, alright we have a failing python3 buildbot now so feel free :)22:43
shogun-buildbotbuild #1 of deb4 - python3 is complete: Failure [failed python static]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/1  blamelist: Orion Poplawski <orion@nwra.com>23:07
shogun-buildbotbuild #2 of deb4 - python3 is complete: Failure [failed python static]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/2  blamelist: Soeren Sonnenburg <sonne@debian.org>23:08
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun23:16
shogun-notifier-shogun: Orion Poplawski :develop * 054852f / cmake/FindOctave.cmake: https://github.com/shogun-toolbox/shogun/commit/054852fe9b573056edca5ca870f34188d6d8379923:16
shogun-notifier-shogun: Octave 3.8.0 does not have libcruft23:16
shogun-notifier-shogun: Soeren Sonnenburg :develop * 17bf0ff / cmake/FindOctave.cmake: https://github.com/shogun-toolbox/shogun/commit/17bf0ff026f374224d1c2d99312c67b30022333f23:16
shogun-notifier-shogun: Merge pull request #1812 from opoplawski/octave3823:16
shogun-notifier-shogun:23:16
shogun-notifier-shogun: Octave 3.8.0 does not have libcruft23:16
-!- travis-ci [~travis-ci@ec2-54-234-102-70.compute-1.amazonaws.com] has joined #shogun23:41
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/1661655323:41
-!- travis-ci [~travis-ci@ec2-54-234-102-70.compute-1.amazonaws.com] has left #shogun []23:41
--- Log closed Thu Jan 09 00:00:43 2014