--- Log opened Fri Nov 24 00:00:44 2017
00:04 -!- gegolo_ [~gegolo@pool-108-26-212-25.bstnma.fios.verizon.net] has quit [Quit: Leaving]
00:06 -!- Horwitz [~mich1@p200300800E3E3200022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
00:12 -!- michael__ [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has joined #navit
00:17 -!- michael__ [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has quit [Client Quit]
00:18 -!- mvglasow_ [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has joined #navit
00:18 -!- mvglasow [bc6e4c38@gateway/web/freenode/ip.188.110.76.56] has quit [Quit: Page closed]
00:18 -!- mvglasow_ [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has quit [Client Quit]
00:19 -!- mvglasow [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has joined #navit
00:19 -!- Horwitz [~mich1@2003:80:e54:1800:222:68ff:fe64:e7c4] has joined #navit
00:19 -!- mode/#navit [+o Horwitz] by ChanServ
00:20 -!- mvglasow [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has quit [Client Quit]
00:23 -!- mvglasow [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has joined #navit
00:24 -!- mvglasow [~michael@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has quit [Client Quit]
00:25 -!- mvglasow__ [bc6e4c38@gateway/web/freenode/ip.188.110.76.56] has joined #navit
00:26 -!- mvglasow_ [~mvglasow@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has joined #navit
00:27 -!- mvglasow__ [bc6e4c38@gateway/web/freenode/ip.188.110.76.56] has quit [Client Quit]
00:27 -!- mvglasow_ [~mvglasow@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has quit [Client Quit]
00:28 -!- mvglasow [~mvglasow@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has joined #navit
00:28 -!- mvglasow [~mvglasow@dslb-188-110-076-056.188.110.pools.vodafone-ip.de] has quit [Client Quit]
01:31 -!- gegolo [~gegolo@pool-108-26-212-25.bstnma.fios.verizon.net] has joined #navit
01:43 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds]
01:49 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
02:25 -!- gegolo [~gegolo@pool-108-26-212-25.bstnma.fios.verizon.net] has quit [Ping timeout: 248 seconds]
06:40 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:49 -!- noradtux [~noradtux@2a02:2028:665:8301:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 250 seconds]
06:54 -!- noradtux [~noradtux@2a02:2028:71a:ad01:ec4:7aff:fe33:3dc1] has joined #navit
07:32 -!- naggety [~naggety@172.red-81-47-39.dynamicip.rima-tde.net] has joined #navit
08:05 -!- naggety [~naggety@172.red-81-47-39.dynamicip.rima-tde.net] has quit [Ping timeout: 246 seconds]
10:48 #navit: < jkoan> hi @all 
10:49 #navit: < jkoan> KaZeR: please look at PR#365 could you approve this now?
12:32 -!- naggety [~naggety@50.red-81-47-80.dynamicip.rima-tde.net] has joined #navit
12:44 -!- youte [~youte@AStrasbourg-551-1-157-75.w86-235.abo.wanadoo.fr] has quit [Ping timeout: 248 seconds]
14:01 -!- naggety [~naggety@50.red-81-47-80.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
14:10 -!- gegolo [~gegolo@pool-108-26-189-131.bstnma.fios.verizon.net] has joined #navit
15:18 -!- ILoveKiruna_ [~pho17@efzn-dsc007.efzn.tu-clausthal.de] has quit [Read error: Connection reset by peer]
15:50 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
16:07 -!- gegolo [~gegolo@pool-108-26-189-131.bstnma.fios.verizon.net] has quit [Ping timeout: 240 seconds]
16:11 #navit: <@KaZeR> hi there
16:14 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
16:19 -!- gegolo [~gegolo@2600:380:8d22:b929:d140:7ac0:5831:ea08] has joined #navit
16:27 #navit: <@KaZeR> hi gegolo 
16:30 #navit: <@KaZeR> jkoan: i double checked the 0.1.0 release details, it was on Nov 26th actually
16:36 #navit: < jkoan> KaZeR: hi
16:37 #navit: < jkoan> KaZeR: so probably we could make the release tomorrow?
16:38 #navit: < jkoan> KaZeR: https://github.com/navit-gps/navit/releases/edit/untagged-2fc3ed094de1edd6f204 see here
16:44 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 248 seconds]
16:59 #navit: <@KaZeR> i'm leaving for an extended week-end soon, might be tough to release tomorrow but we can try
16:59 #navit: < jkoan> :O
17:01 #navit: <@KaZeR> let's call that an intensive field test of navit :)
17:02 #navit: < jkoan> so rc1 ?
17:02 -!- youte [~youte@AStrasbourg-551-1-157-75.w86-235.abo.wanadoo.fr] has joined #navit
17:02 #navit: <@KaZeR> we still have the issue with the android images
17:02 #navit: < youte> hi all
17:02 #navit: < jkoan> yes and we dont know why
17:02 #navit: < jkoan> hi youte
17:09 -!- mvglasow [~mvglasow@dslb-188-104-102-111.188.104.pools.vodafone-ip.de] has joined #navit
17:09 #navit: <@KaZeR> afk 30 min
18:06 -!- gegolo [~gegolo@2600:380:8d22:b929:d140:7ac0:5831:ea08] has quit [Quit: Leaving]
20:35 #navit: < ilovekiruna>   hi KaZeR, hi youte, hi jkoan
20:35 #navit: < jkoan> hi ilovekiruna
20:39 #navit: < ilovekiruna> jkoan: what's up?
20:50 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
20:53 #navit: < jkoan> probably navit 0.5.1-rc1 will happen this weekend depending on KaZeR but for example we have issues with apk generation so we cant release it. Do you have andy idea why this is happeing? i will go to sleep soon
20:54 #navit: < ilovekiruna> so far i just heard that the toolchain is somehow broken
20:54 #navit: < ilovekiruna> dont know details, sorry
20:54 #navit: < ilovekiruna> jkoan: wow u really sleep early for a friday
20:55 #navit: < jkoan> i would think its more the cmake itself 
20:55 #navit: < jkoan> yes, i stand up today at 5:00
20:56 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 258 seconds]
20:56 #navit: < jkoan> because the copy of the files sometimes fails
20:57 #navit: < ilovekiruna> wow
20:57 #navit: < ilovekiruna> i would be dead after waking up that early
20:57 #navit: < ilovekiruna> totally unproductive
20:58 #navit: < jkoan> today i was not extreamly productive, but yes
20:58 #navit: < ilovekiruna> i hope for navit next week, i can finally do sth again
20:58 #navit: < ilovekiruna> will c
20:59 #navit: < jkoan> okay :)
20:59 #navit: < ilovekiruna> do you know if anything came up, about the app testing on google cloud?
20:59 #navit: < ilovekiruna> could it finally detect our problems?
20:59 #navit: < jkoan> no i dont knnow
20:59 -!- gegolo [~gegolo@2600:380:8d22:b929:61df:909e:ac82:68e0] has joined #navit
21:00 #navit: < jkoan> but i was thinking about a own device farm (i have already some old devices). Do you have an idea about that?
21:01 #navit: < ilovekiruna> i love the idea
21:02 #navit: < ilovekiruna> was discussing it after we figured out the limitations of AWS
21:02 #navit: < ilovekiruna> we just have 1000 minutes in total
21:02 #navit: < jkoan> yep
21:02 #navit: < ilovekiruna> was actually my idea even before starting with AWS
21:02 #navit: < ilovekiruna> i like to have control over my own infrastructure
21:02 #navit: < jkoan> the only question is what software i need
21:02 #navit: < jkoan> yep
21:02 #navit: < ilovekiruna> all droids?
21:03 #navit: < ilovekiruna> i see one advantage of sth on our own.
21:03 #navit: < jkoan> i have at least 4 old android phones here
21:03 #navit: < ilovekiruna> I could also offer two sailfish devices
21:03 #navit: < ilovekiruna> which i can time to time connect
21:03 #navit: < ilovekiruna> for running tests one could use Appium, like i do
21:04 #navit: < jkoan> does appium has an interface to control everything?
21:04 #navit: < ilovekiruna> i can answer if you tell me what everything is for u
21:04 -!- gegolo [~gegolo@2600:380:8d22:b929:61df:909e:ac82:68e0] has quit [Remote host closed the connection]
21:05 -!- gegolo [~gegolo@2600:380:8d22:b929:61df:909e:ac82:68e0] has joined #navit
21:06 #navit: < jkoan> a web interface to controal touch, install uninstall, screenshots and so on. So the basic actions and also trigger automatic tests
21:06 #navit: < ilovekiruna> Appium is more script based
21:06 #navit: < ilovekiruna> so I can run gui tests on a few different OS
21:06 #navit: < ilovekiruna> so far WP, iOS and Droid
21:07 #navit: < ilovekiruna> i think install and uninstall should work
21:07 #navit: < ilovekiruna> screenshots or video should be via adb
21:07 #navit: < ilovekiruna> i think we could trigger it automatically
21:07 #navit: < ilovekiruna> with a webhook
21:07 #navit: < jkoan> screens and video will not work on old phones also touch will not work
21:08 -!- gegolo [~gegolo@2600:380:8d22:b929:61df:909e:ac82:68e0] has quit [Read error: Connection reset by peer]
21:08 #navit: < ilovekiruna> what is old?
21:08 #navit: < ilovekiruna> in terms of android version
21:08 #navit: < jkoan> 2.3.4
21:09 #navit: < jkoan> do you have a working appium test?
21:09 #navit: < ilovekiruna> yes
21:09 #navit: < jkoan> where? ^^
21:09 #navit: < ilovekiruna> but i think i need to modify it for that old versions
21:10 #navit: < ilovekiruna> my private repo
21:10 #navit: < ilovekiruna> https://github.com/hoehnp/navit_test
21:10 #navit: < jkoan> okey, i will test
21:10 #navit: < ilovekiruna> let me check
21:10 #navit: < ilovekiruna> for 2.3.4 i will need modifications
21:10 #navit: < ilovekiruna> for sure
21:10 #navit: < ilovekiruna> i use uiautomator
21:10 #navit: < ilovekiruna> that is too new for 2.3.4
21:11 #navit: < jkoan> could you also say me how i would start the test?
21:15 #navit: < ilovekiruna> I just checked a little, need to c older versions of appium
21:15 #navit: < ilovekiruna> selendroid seems to go till API 10
21:16 #navit: < ilovekiruna> I see now appium allows installing and removing apps
21:17 #navit: < ilovekiruna> closing and starting apps
21:17 #navit: < ilovekiruna> place and retrieve files
21:17 #navit: < ilovekiruna> and touch actions
21:18 #navit: < jkoan> touch even for 2.3.4?
21:19 #navit: < ilovekiruna> we should check out the coming days
21:19 #navit: < ilovekiruna> cant verify here
21:19 #navit: < jkoan> okay
21:19 #navit: < jkoan> not today sounds good
21:19 #navit: < ilovekiruna> my oldest phone here is ICS
21:20 #navit: < jkoan> i dont know what thhe oldest is, probably i have something laying around 
21:20 #navit: < ilovekiruna> ICS is 4.0
21:20 #navit: < jkoan> i would look up it now, bu all those phones are empty
21:21 #navit: < ilovekiruna> btw: you find how to run js based tests right on the startpage of appium
21:21 #navit: < ilovekiruna> but i prefer python
21:21 #navit: < ilovekiruna> http://appium.io/
21:23 #navit: < ilovekiruna> python tests are here:
21:23 #navit: < ilovekiruna> http://appium.io/
21:23 #navit: < ilovekiruna> https://github.com/appium/sample-code/tree/master/sample-code/examples/python
21:23 #navit: < jkoan> right now the problem is apium install itself...
21:24 #navit: < ilovekiruna> in which way?
21:24 #navit: < jkoan> npm
21:24 #navit: < ilovekiruna> :-o
21:25 #navit: < jkoan> its not in the repo so i thought it whould be good because it is there official way (also i like npm and nodejs)
21:29 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
21:30 #navit: < ilovekiruna> sorry, didnt get what for?
21:30 #navit: < ilovekiruna> appium-python?
21:30 #navit: < ilovekiruna> appium?
21:30 #navit: < jkoan> appium itself
21:30 #navit: < ilovekiruna> appium isnt in the npm repo?
21:32 #navit: < jkoan> it is not in the deb repo but it is in the npm but it does not install correctly 
21:32 #navit: < ilovekiruna> hmmm
21:32 #navit: < ilovekiruna> didnt try on deb so far
21:34 #navit: < jkoan> one of the install scripts has a problem because it does not generate the directory correctly 
21:35 #navit: < ilovekiruna> which debian is it?
21:35 #navit: < ilovekiruna> or ubuntu?
21:36 #navit: < jkoan> its ubuntu
21:37 #navit: < ilovekiruna> one guess i have is that the nodejs version in the repos is a bit aged
21:37 #navit: < ilovekiruna> which version?
21:37 #navit: < jkoan> last
21:37 #navit: < ilovekiruna> then today or tomorrow can try in a VM
21:37 #navit: < ilovekiruna> 17.10?
21:37 #navit: < jkoan> yep and nodejs v8.7.0
21:40 #navit: < ilovekiruna> try npm install -g appium-doctor
21:40 #navit: < jkoan> why doctor?
21:40 #navit: < ilovekiruna> and then run appium-doctor --android
21:40 #navit: < ilovekiruna> it is a tool to check you have all the required dependencies installed
21:42 #navit: < jkoan> the error is on installing appium-chromedriver because he cant create the directory (with root)
21:42 #navit: < ilovekiruna> try it without root
21:42 #navit: < ilovekiruna> as ordinary user
21:43 #navit: < jkoan> then i cant install with -g
21:44 #navit: < ilovekiruna> http://appium.io/getting-started.html
21:44 #navit: < ilovekiruna> am reading the requirements here
21:45 #navit: < ilovekiruna> they mention one shouldnt have installed node with sudo
21:45 #navit: < ilovekiruna> jkoan: I think i will be off for now, hope it is ok to continue tomorrow, probably
21:46 #navit: < jkoan> okay see u
21:46 #navit: < ilovekiruna> see you
22:06 #navit: < mvglasow> KaZeR are you around?
22:13 #navit: < mvglasow> in case you read the logs: I’ve made progress on the plugin issue we discussed yesterday
22:14 #navit: < mvglasow> I included traffic.h in start_real.c and called one of its functions in main_real()
22:14 #navit: < mvglasow> with that, the error from the plugin is gone
22:15 #navit: < mvglasow> my suspicion is that the toolchain optimizes out any source file that is never called in navit core
22:20 #navit: < mvglasow> since core files usually are used in navit core somewhere, this may never have come up
22:21 #navit: < mvglasow> but I got bitten by this since I’m still in an early stage of development
22:21 #navit: < mvglasow> I’ve pushed the workaround to my repo
22:22 #navit: < mvglasow> will get in touch again during the next days
22:22 -!- mvglasow [~mvglasow@dslb-188-104-102-111.188.104.pools.vodafone-ip.de] has quit [Quit: Leaving]
23:30 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 268 seconds]
23:34 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 260 seconds]
23:44 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
--- Log closed Sat Nov 25 00:00:46 2017