[12:00:11] ?pepteam [12:00:11] arschmitz jdalton jrossi jrossi1 jrossi2 jrossi3 jrossi9billion M4rius scott_gonzalez snover [12:00:17] hi [12:00:50] Oh, look... [12:00:51] ?pepteam [12:00:51] arschmitz bethge jdalton jrossi jrossi1 jrossi2 jrossi3 jrossi9billion M4rius scott_gonzalez snover [12:00:54] hi [12:01:09] I finally figured out how to update it. I feel like b-ot is constantly changing. [12:01:18] yay :D [12:02:33] Nobody from Microsoft has shown up in quite a while. [12:02:42] I'll email Jacob about it. [12:03:28] bethge's PR was merged :-) https://github.com/jquery/PEP/pull/256 [12:03:55] woo [12:04:10] Did you end up reaching out to snover about leadfoot? [12:05:03] Didn't get to it. I asked around the week before about iOS and he did help me out with the settings on the intern side of things, but the driver did not play along [12:05:34] ok [12:05:44] last weekend i stabbed at it with chromedriver + android sdk but didn't get deep enough into it [12:06:54] when you use chromedriver, you just start the bin as an executable, did I get that right? [12:08:53] On OSX the chromedriver bin just throws errors, not sure if they support osx directly [12:09:04] it always worked for me [12:09:12] previously anyway [12:09:18] and im on osx [12:09:36] i am getting failures now when i went back to my branch running it from grunt though [12:09:47] Yeah, you run `chromedriver --port=4444 --url-base=wd/hub` and then it should start up. [12:10:06] Ok cool, then it's just me [12:10:59] Well, that's no good, because a) I have no idea how to debug chromedriver issues; b) This could be happening for others and we just don't know. [12:11:53] There is still option c) : I am just doing something terribly wrong [12:12:12] ;) [12:12:13] i have debugged chrome driver a bunch [12:12:27] but let me see if i can get grunt working again and if that works for you [12:12:45] because that at least eliminates user error mostly [12:13:55] arschmitz: Think you'll have time to work on that this week? [12:13:57] i started looking into it again this week [12:14:20] yeah i am already just need to finish it up think i have it figured out [12:15:57] ok [12:16:27] chromedirver is a pain but its almost always somethign simple and stupid [12:16:32] bethge: Was that list of tests that you added (commented out), the complete list? [12:16:46] I think so [12:16:56] should be 64, I believe [12:17:38] Ok, I was thinking maybe we should close https://github.com/jquery/PEP/issues/170 and open new issues for small batches of related tests. [12:17:57] i think that makes more sense [12:18:04] something we can actually work though and close [12:18:14] We've been breaking them up in PRs anyway. This would make it easier for someone to claim ownership of a set and not worry about duplicated efforts. [12:18:36] I can double check to make sure that list is complete and then file issues for them. [12:19:04] That sounds good [12:20:26] Ok, I'll even commit to one of the batches for next week. [12:20:54] nice :) [12:21:51] btw. some tests are for mouse, touch and pen, should we do tests for all the input devices? (once we have touch and pen) [12:23:41] If we can, we should. [12:23:58] Because that's the only way we can really ensure that we're handling all the paths correctly. [12:24:32] yeah ... I imaged you would say that [12:24:39] I can file an issue for us to go back through the tests and see which ones should run multiple times. [12:24:53] fun fun fun, tests tests tests :D [12:24:56] :-) [12:27:06] https://github.com/jquery/PEP/issues/257 [12:28:21] I think that's everything for tests. [12:28:28] Is there anything else to discuss today? [12:40:46] Thanks everyone. [14:01:57] agcolom: apsdehal: gabrielschulhof: jasperdegroot: sfrisk: meeting time [14:02:04] hola [14:02:19] hello! [14:02:31] cogwurx: hello! [14:03:02] howdy [14:05:20] agenda https://docs.google.com/spreadsheets/d/11-mngR57h54cIOjGDE2Z6LjaiyRgDwlcvKUzZn2Fw6M/edit#gid=1983914725 [14:05:27] ok so big news this week [14:05:34] UI beta finally officially was announced [14:05:46] and as of about 2 minutes ago i just published out blog update [14:05:59] problems with API docs solved? [14:06:00] so every one quick tweet it [14:06:13] yeah it was the download builder that was the blocker for a while now [14:06:32] Hi [14:06:59] arschmitz: do you send a tweet from the @jquerymobile account? [14:07:00] but since we are talking about that once ui 1.12 stable is out scott will be concentarating on fixing the download builder and helping out getting it to work for mobile and that will be his concentration for a big [14:07:15] not yet logging in now i lterally just published the blog [14:07:39] haven't seen the tweet yet [14:07:53] ah...there it is [14:09:53] Hey! Sorry I'm late! [14:11:56] ok [14:12:02] so in regular business [14:12:15] i reviewed table [14:12:21] and am half way through panel [14:14:03] as for failing table tests on 1.5-dev [14:14:08] those are fixed in the table branch [14:14:17] but there is 1 failing test in all core versions still [14:14:23] so that should be easier to fix [14:14:39] panel is looking good so far just small things [14:14:56] table was also pretty much mostly small things [14:15:05] gabrielschulhof: any update on selectmenu [14:15:17] arschmitz: I can't reproduce any errors on my table branch using any jqueries, any tips [14:15:24] arschmitz: Yeah. I finally got the tests to be green again, but it's still slow going. [14:15:26] hrm [14:15:54] I'm still using pagehide on page though, so I need to move away from that. [14:15:55] https://travis-ci.org/jquery/jquery-mobile/jobs/103908456 [14:16:22] getting an undefined element somewhere in that test [14:16:41] its an actual error not just a failing test so should be easy to reproduce [14:16:48] maybe you have something not pushed? [14:17:12] i'll double check [14:18:35] awesome [14:18:42] nope, all clear, plus i just pulled the branch down on another machine and 1.9.1 is green, checking others now [14:18:51] weird [14:19:00] every version is failing on travis with same error [14:19:32] gabrielschulhof: you did a lot fo the work on that anything stand out to you? [14:19:35] well the git version is different and I can reproduce that [14:19:51] odd [14:20:19] but that is in transitions unit tests [14:20:42] anyway, I'll go through your review this week and maybe it'll work itself out on travis [14:20:53] 2 fails in 2.1 [14:21:08] arschmitz: Just that it's very fragile. [14:21:09] both for element undefined though [14:21:17] Oh, wait, you don't mean selectmenu. [14:21:22] no table [14:21:36] Looking ... [14:21:45] it might be a async issue [14:22:33] So, it's not reproducible locally, even with phantomjs? [14:22:47] so git has no table fails but does in transitions [14:22:50] I mean, I just ran into such an exception that was happening in phantomjs but not in Chrome. [14:23:00] 1.x fails 1 table test [14:23:05] 2.x fails 2 table tests [14:23:53] The only way of tracing that is to use try {} and console.log() and to submit to travis. Yuck! [14:24:30] ... and the stack traces phantomjs produces are useless. [14:24:36] yeah [14:24:38] I doubt that's coming from table_core.js [14:24:51] cgack: well just see what you can trace down with it [14:24:59] hopefully you can get it to happen local at least [14:25:20] i'll keep trying to break it :) [14:25:27] does anyone have anything else? [14:25:29] cgack: Hang in there ... [14:25:46] cgack: if you get stuck feel free to ping me and ill try and dig in [14:25:57] cgack: If you end up submitting repeatedly to travis, turn things off in .travis.yml [14:26:05] cgack: Like, all non-essential suites and stuff. [14:26:32] cgack: You can even say grunt connect:server qunit:http to skip directly to the tests. [14:26:53] cgack: Like, grunt --suites=table connect:server qunit:http [14:26:58] you could even make it just run the suite you want too [14:27:00] yeah exactly [14:27:45] cgack: Yeah, turn things off, push a branch to jquery/jquery-mobile, and run travis repeatedly for that branch. [14:27:50] iv had luck before just bogging down my machine to reproduce too [14:28:16] like run the tests in like 6 different tabs at once while watching video and photoediting lol [14:28:38] try to simulate the load on travis a bit [14:28:40] haha, VisualStudio usually does enough to bog this machine down [14:28:49] but yeah, i'll tinker around [14:29:21] :) [14:29:32] Reminds me of Petzold: https://www-user.tu-chemnitz.de/~ygu/petzold/ch20e.htm [14:29:35] ok any one have anything else? [14:29:51] for (i = 0 ; i < REP && pparams->bContinue ; i++) A = tan (atan (exp (log (sqrt (A * A))))) + 1.0 ; [14:30:04] But anyway ... [14:30:26] Nothing else here ... [14:31:27] ok [14:31:37] ill see everyone back on -dev then