--- Log opened Fri Oct 13 00:00:28 2017
00:02 -!- Horwitz [~mich1@p200300800E209000022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:02 -!- mode/#navit [+o Horwitz] by ChanServ
00:42 #navit: < pmckinley> Hi Michael
03:04 -!- noradtux [~noradtux@2a02:2028:672:1c01:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 258 seconds]
03:18 -!- noradtux [~noradtux@port-23037.pppoe.wtnet.de] has joined #navit
05:08 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:42 -!- pmckinley [~Peter_McK@88-110-193-131.dynamic.dsl.as9105.com] has left #navit []
08:19 -!- pmckinley [~Peter_McK@88-110-196-109.dynamic.dsl.as9105.com] has joined #navit
11:04 #navit: < pmckinley> :-/
11:25 -!- pmckinley [~Peter_McK@88-110-196-109.dynamic.dsl.as9105.com] has left #navit []
13:41 #navit: < youte> hi
14:37 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:59 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
16:09 #navit: < jkoan> hi youte
16:09 #navit: < jkoan> nice new icons
16:09 #navit: < jkoan> do you want to recreate the whole icon set?
16:09 #navit: < jkoan> ^^
16:23 #navit: <@KaZeR> hi there
16:24 #navit: <@KaZeR> jkoan: hopefully he will at some point and we'll have consistent icons :)
16:24 #navit: < jkoan> hi KaZeR
16:25 #navit: < jkoan> yes, but i think we must probably show youte a bit more about git (but its impressive for the first steps)
16:26 #navit: < youte> yes it's not pb, i like to do this
16:28 #navit: < jkoan> pb?
16:28 #navit: < youte> problem sorry :p
16:29 #navit: < jkoan> ah ^^ i already wrote with youte for the first steps ;)
16:29 #navit: < youte> yes git don't like me xD
16:32 #navit: <@KaZeR> yeah looks like he didn't branch from trunk for each PR. i pm'ed him already :)
16:33 #navit: < jkoan> KaZeR: what about PR#315 and #309 ?
16:42 #navit: <@KaZeR> thanks for reminding me
16:42 #navit: <@KaZeR> in #315, set_with_reason(map/shapefile "Android detected, saveing space" FALSE) appears twice
16:42 #navit: <@KaZeR> also there's a small typo : limeted instead of limited :)
16:44 #navit: <@KaZeR> regarding #309 i see outstanding requests/comments from sleske
16:49 #navit: < jkoan> okay for 315 i will look into
16:53 #navit: < jkoan> for 309 its a discussion which should go on, but is not related to me ^^ my opinion is shown in form of code :D
16:57 #navit: <@KaZeR> well one thing we could do to make the discussion easier is to add a debian install to the CI
16:57 #navit: < jkoan> what do you mean by "debian install" ?
16:58 #navit: <@KaZeR> spin up a debian container, install navit it in and try to run it
17:00 #navit: <@KaZeR> checkout this workflow example from a side project : https://imgur.com/a/u7ugl 
17:03 #navit: < jkoan> should not be a problem to install with only some components
17:06 #navit: <@KaZeR> exactly
17:06 #navit: <@KaZeR> want to take a stab at it?
17:09 #navit: < jkoan> not in the next weeks
17:12 #navit: <@KaZeR> no worries
17:50 #navit: < ilovekiruna> hi KaZeR, hi jkoan
17:55 #navit: < youte> hi ilovekiruna 
17:55 #navit: < ilovekiruna> hi youte
18:03 #navit: < jkoan> hi ilovekiruna
18:09 #navit: <@KaZeR> hey ilovekiruna 
18:42 -!- bzed [~bzed@shell.bzed.at] has quit [Remote host closed the connection]
18:43 -!- bzed [~bzed@shell.bzed.at] has joined #navit
19:13 #navit: < ilovekiruna> KaZeR: have u understood that part of the device farm, where you upload the apk file?
19:13 #navit: < ilovekiruna> i mean cant i also include the apk-file in my test_bundle?
19:14 #navit: < ilovekiruna> or how could one then run device farm as a kind of ci-system?
19:25 #navit: <@KaZeR> i don't think that you can upload the apk as part of the bundle. I think that the bundle stays, and the apk changes
19:25 #navit: <@KaZeR> but we can use the API to upload new apk and trigger runs
20:20 #navit: < ilovekiruna> ah, ok
20:21 #navit: < ilovekiruna> that leaves me another question honestly, which i should resolve at some point
20:21 #navit: < ilovekiruna> have you seen my test_first.py file?
20:25 #navit: <@KaZeR> i have but you mentionned that it was a first try
20:25 #navit: <@KaZeR> *mentioned
20:26 #navit: < ilovekiruna> i know, just wanted to point out one thing now, which i thought still could be valide
20:27 #navit: <@KaZeR> sure, shoot
20:27 #navit: < ilovekiruna> is anything in def setUp(self) considered by device farm?
20:27 #navit: < ilovekiruna> to me now everything seems totally useless
20:28 #navit: < ilovekiruna> at least all in desired_caps
20:29 #navit: <@KaZeR> oh that's probably some default settings
20:30 #navit: < ilovekiruna> i mean if u run appium locally on your own machine it can make sense
20:31 #navit: < ilovekiruna> but on device farm, i guess it is just totally ignored
20:31 #navit: < ilovekiruna> will now have a look, if i can make the other things run with less number of errors :)
21:04 #navit: < ilovekiruna> KaZeR: can you try to run a test?
21:04 #navit: < ilovekiruna> right now i just receive an error when trying to schedule a new one
21:18 #navit: <@KaZeR> yeah sure
21:18 #navit: <@KaZeR> let me see
21:18 #navit: < ilovekiruna> now i could run a test again
21:18 #navit: < ilovekiruna> was strange
21:18 #navit: < ilovekiruna> so it is ok, now
21:19 #navit: < ilovekiruna> seems like the current test is that much commented out that i get no error :)
21:19 #navit: <@KaZeR> haha
21:19 #navit: <@KaZeR> no code == no problem :D
21:19 #navit: < ilovekiruna> btw: have we any idea of navit on kindle fire HDX 7?
21:20 #navit: < ilovekiruna> now i need to add useful code
21:20 #navit: <@KaZeR> we can test it using the device farm, in interactive mode. that's one of the really cool feature, there's like 1000 devices to choose from
21:21 #navit: < ilovekiruna> now another question
21:21 #navit: < ilovekiruna> can you please check the video of the latest test?
21:21 #navit: < ilovekiruna> it seems like it doesnt find the speech engine
21:21 #navit: < ilovekiruna> and i have no clue what to do
21:21 #navit: <@KaZeR> talking about devices, maybe we should reduce the number of devices that we test on for now. currently we're consuming 5x the number of minutes, it's quite useless until we get some actual tests running
21:21 #navit: <@KaZeR> sure
21:21 #navit: < ilovekiruna> sure, we could limite it to one
21:21 #navit: < ilovekiruna> no prob
21:22 #navit: <@KaZeR> mm i don't see the video. for which test is it?
21:22 #navit: < ilovekiruna> simple test 2
21:22 #navit: < ilovekiruna> maybe check here: https://prod-us-west-2-results.s3-us-west-2.amazonaws.com/353437834531/f05c129c-e260-46ec-8f1b-c1cb0f200f65/d84cdf21-451a-44e7-a387-35b18189dd55/00000/00001/00000/894921b5-d6ad-4e44-acb0-03ef9d177a04.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20171013T212019Z&X-Amz-SignedHeaders=host&X-Amz-Expires=259200&X-Amz-Credential=AKIAJV4C3CWPBUMBC3GA%2F20171013%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-
21:22 #navit: < ilovekiruna> Signature=82d96714cfba4c2650bbc0031d1c4acfc966e2c5031287d3ad058b036525dc74
21:26 #navit: < ilovekiruna> did i post sth wrong now?
21:27 #navit: <@KaZeR> nop it's ok
21:27 #navit: <@KaZeR> i have the file
21:27 #navit: < ilovekiruna> check at second 22
21:27 #navit: <@KaZeR> yeah, it asks for which TTS to use
21:28 #navit: < ilovekiruna> can we suppress that or do i need to deal with that?
21:28 #navit: <@KaZeR> i think that this is caused by a samsung specific overlay in android
21:28 #navit: < ilovekiruna> it isnt samsung specific
21:29 #navit: < ilovekiruna> i also saw it in the video with the amazon kindle
21:29 #navit: <@KaZeR> the screenshot says "GoogleTTS or SamsungTTS"
21:29 #navit: <@KaZeR> what were the different options with the Kindle?
21:29 #navit: < ilovekiruna> need to check the video again
21:29 #navit: <@KaZeR> ok
21:30 #navit: < ilovekiruna> system to speech engine data is missing
21:30 #navit: < ilovekiruna> is the title of the message
21:30 #navit: <@KaZeR> ha, it's a bit different then
21:30 #navit: <@KaZeR> do you think that we could detect that from the test suite?
21:30 #navit: <@KaZeR> (the message)
21:31 #navit: < ilovekiruna> so far in the documentation i have seen that one can automatically input texts or clicks
21:31 #navit: < ilovekiruna> but nothing yet about detecting such things
21:31 #navit: < ilovekiruna> need to check
21:31 #navit: <@KaZeR> ok. i think that there's probably a way, because it's actually important to make sure that you are in the correct menu after an action
21:32 #navit: <@KaZeR> the difficulty will be to find how to do it :)
21:35 #navit: < ilovekiruna> my guess now would be one could try to find menu entries which should be visible and validate it by that
21:36 #navit: <@KaZeR> exactly
21:36 #navit: < ilovekiruna> but my first goal would be to make it run ;-)
21:36 #navit: <@KaZeR> :D
21:36 #navit: < ilovekiruna> which device would u suggest me to just use now?
21:36 #navit: < ilovekiruna> instead of the 5
21:37 #navit: <@KaZeR> from the current list, i'd probably take the galaxy S6
21:39 #navit: < ilovekiruna> who is most involved with the android development?
21:40 #navit: < ilovekiruna> S6 seems a pretty bad choice, i saw the video
21:40 #navit: < ilovekiruna> error message: Unfortunately Navit has stopped
21:46 #navit: <@KaZeR> haha. or maybe it's an excellent choice :D
21:47 #navit: <@KaZeR> jandegr was our android expert but he's less active recently
21:47 #navit: <@KaZeR> let's pick another device then and we can investigate the crash later
21:47 #navit: <@KaZeR> might be worth logging it in trac maybe
21:47 #navit: < ilovekiruna> am asking because for selecting how to find any object, I know the android interals too little
21:48 #navit: <@KaZeR> interals too little?
21:48 #navit: < ilovekiruna> internals
21:48 #navit: <@KaZeR> oh ok
21:48 #navit: <@KaZeR> i think that it's probably appium specific though. need to finish something and i can do some research later maybe
21:48 #navit: < ilovekiruna> i can also check, maybe i just give u some keywords now
21:49 #navit: < ilovekiruna> one can find elements by xpatch
21:49 #navit: < ilovekiruna> like android.widget.TextViewe
21:49 #navit: < ilovekiruna> or by accessibility id
21:49 #navit: < ilovekiruna> no clue what any of the two is
21:49 #navit: < ilovekiruna> will check a little
21:54 #navit: <@KaZeR> i think that you are on the right track. that's how pretty much all testing framework work
21:57 #navit: < ilovekiruna> the only thing which bothers me a little is how to find in the code which widget is of which type or has an accessibility id, or which one it has
21:58 #navit: <@KaZeR> in navit's code? or in the test code?
21:58 #navit: < ilovekiruna> i would expect that to be in the android code
21:58 #navit: < ilovekiruna> widget types and such for sure
21:59 #navit: < ilovekiruna> not sure about accessibility id though
22:07 #navit: <@KaZeR> i see
22:39 #navit: < ilovekiruna> could it be that there is a different choice of devices for automated tests and remote access session?
22:47 #navit: <@KaZeR> that would be surprising
22:47 #navit: <@KaZeR> i think that it's the same devices
22:50 #navit: < ilovekiruna> i didnt find Samsung S5 
22:50 #navit: < ilovekiruna> but now trying to figure out with S3
22:50 #navit: < ilovekiruna> seems similar things
22:57 #navit: < ilovekiruna> KaZeR: remind me. There was no option to download navit maps directly from navit?
22:59 #navit: < ilovekiruna> found it :)
22:59 #navit: < ilovekiruna> never mind
23:00 #navit: <@KaZeR> :)
23:00 #navit: <@KaZeR> yeah the UI is a bit inconsistent for this featyre
23:00 #navit: <@KaZeR> it's not in the usual menu because currently it's android specific.. so it's in an android specific menu :(
23:00 #navit: < ilovekiruna> actually u r right, would make sense to also place it under actions
23:01 #navit: < ilovekiruna> I c
23:01 #navit: <@KaZeR> yeah. we also need to finish the generic map downloader (currently in the curl_download branch)
23:01 #navit: <@KaZeR> it uses libcurl and should be cross platform...
23:08 #navit: < ilovekiruna> btw: I think I am really on the right way
23:08 #navit: < ilovekiruna> just need to learn how to find the elements :-S
23:15 #navit: <@KaZeR> yeah.. once we get the first one working, expanding the tests should be much easier
23:16 #navit: <@KaZeR> huge thanks for taking the lead on this. this is really going to have a huge impact on how we develop
23:19 #navit: < ilovekiruna> you're welcome
23:19 #navit: < ilovekiruna> no problem
23:20 #navit: < ilovekiruna> how many minutes do we have left this months?
23:27 #navit: <@KaZeR> looks like we consumed 34 minutes so far
23:27 #navit: < ilovekiruna> i was afraid it was more
23:27 #navit: < ilovekiruna> nice that it is so little
23:28 #navit: <@KaZeR> might be a bit delayed. iirc we have 1000 free minutes/month
23:28 #navit: <@KaZeR> and then it's $0.17/min
23:29 #navit: < ilovekiruna> the tests with the 6 devices where 25 mins each, i thought
23:29 #navit: < ilovekiruna> or does it just count the test time
23:29 #navit: < ilovekiruna> not accumulate between devices
23:29 #navit: <@KaZeR> i'm quite sure that it counts per device
23:30 #navit: < ilovekiruna> then we should be quite above 34 mins
23:30 #navit: <@KaZeR> yeah i think that today is not included in the 34 minutes
23:33 #navit: < ilovekiruna> i would estimate now, that i already used up 115 minutes or so
23:48 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
23:48 -!- Horwitz [~mich1@p200300800E209000022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
23:53 #navit: <@KaZeR> cool, we still have plenty of time left :)
--- Log closed Sat Oct 14 00:00:30 2017