[12:13:34] hi [12:14:11] i have problems running the tests [12:14:35] "grunt perf" hangs at "Starting PerfJankie" and nothing happens [12:15:08] ofalvai: do you have the couchdb server running? [12:15:30] yes, I can access Futon [12:15:41] i'm on Windows btw [12:16:02] ofalvai: that may be the problem i dont have windows handy [12:16:12] ofalvai: can you do grunt perf --verbose [12:16:16] and gist the output [12:18:29] https://gist.github.com/ofalvai/ed3ecaba78ea0e8abb32 [12:19:09] maybe cygwin is the problem? [12:19:38] it looks like browserperf is not starting [12:20:04] ofalvai: can you try doing npm install -g browserperf [12:20:15] then try again and see if it changes [12:21:46] it's called browser-perf, right? [12:22:46] it still hangs :( [12:32:42] i think i understand the problem. i started chromedriver.exe, but it uses a different port than what's defined in perfjankie.js [12:33:21] but it still fails, saying "aborted due to warnings" [12:44:05] ofalvai: you shoudl not be starting chrome dirver [12:44:41] yes, now as i'm digging deeper, i see that selenium is started and i shouldn't mess with it [12:46:16] ofalvai: just follow the directions in the readme :-) [12:47:12] in which readme? because the chassis readme says nothing about setting up these things, i though grunt perf would work automatically [12:47:35] it should [12:47:41] other then npm install [12:47:52] you should not start selenimum or chromedriver [12:50:51] ofalvai: if you have a selenium running already it will hang and fail [12:51:30] i don't, i just tried that once, now i'm doing everything as i should [12:52:11] now it throws ECONNREFUSED [13:06:40] ok, i give up for now [13:07:12] did you run npm install? [13:07:28] anyway, i'm here because of the GSoC, so running the tests is not important now, right? [13:07:34] yes, i did [13:07:34] and did it run sucesfully without any error messages? [13:08:08] ofalvai: feel free to gist the verbose output again and ill look [13:08:12] yes...but i'll try starting from scratch [13:08:26] ofalvai: i would restart too [13:08:36] also rm -rf node_modules [13:08:43] and npm install again [13:08:56] geekman-rohit: did you ever get them running local? [13:09:03] yes [13:09:07] awesome [13:09:20] I am on windows, waiting for a 3gb download to finish [13:09:26] Ill try to install too [13:09:36] fun [13:12:18] arschmitz hes on windows? rm won't work ;) [13:12:48] lol will delete the directory [13:13:18] i'm on windows, but i use cygwin, and understand linux stuff :) [13:14:15] I'm going to try on windows7 right now, always pray before I try stuff on windows ;) [13:15:53] meanwhile, i've set up the project from scratch (without any install errors), and nothing changed, still can't connect [13:16:04] i'll see if a restart helps [13:21:07] it's the same as before...i give up for now :( [13:24:23] ofalvai: gist are great :-) [13:24:34] hard to help if i cant see the full output [13:26:38] https://gist.github.com/ofalvai/cd16e644aba8d63b47a3 [13:27:05] this is with the port set to 9515. with 4444 nothing happens after "Starting Browserperf" [13:30:32] ofalvai: did you change the port? [13:31:15] yes, in tasks/options/perfjankie.js [13:31:24] arschmitz, which port does couchdb run on? [13:31:33] dont change the ports [13:31:39] everything is configured to work as is [13:31:54] geekman-rohit: 5984 [13:32:11] yes, but as i said, it hangs with the default 4444 port, i tried that many times [13:32:37] but that does not change the port the server starts on [13:32:58] just where its listening so thats why your getting a connection refsused [13:33:06] oh, i see [13:33:09] there is nothing there to connect to [13:33:20] starting perfjankie [13:33:26] is where it hangs on my win7 [13:33:35] no movement after that [13:33:50] can you gist the output with --verbose [13:34:47] mine hangs two lines later (starting browser perf), but i remember the first time it was starting perfjankie [13:35:37] also what is the url that opens when you start couchdb? [13:37:31] what do you mean? when i start it on my machine? a window flashes for a few seconds, then disappears, and nothing opens [13:37:33] https://gist.github.com/geekman-rohit/bd3872e7029a47a27133 [13:37:52] but the server is running, i can access http://localhost:5984/_utils/ [13:37:55] a database is created on couch db css_performance.. but nothing after that [13:39:06] arschmitz, we should try to see if selenium works on windows first, outside of our grunt task [13:39:17] geekman-rohit: can you try doing npm install -g browser-perf [13:39:26] then do the same thing and gist the output [13:39:31] yes, will [13:43:20] my npm install fails [13:43:23] for node-sass [13:43:50] windows is a pain :P [13:45:35] ofalvai: i assume npm install worked for you [13:46:45] it did, but didn't help [13:47:19] iv never used selenium on windows [13:47:37] selenium is doing something strange localhost:4444 gives 403 [13:49:51] http://127.0.0.1:4444/wd/hub ? [13:51:03] or http://127.0.0.1:4444/wd/hub/ [13:52:16] it works for me [13:52:50] i mean because the grunt task still hangs [13:53:51] arschmitz, browser perf just worked fine.. direct use from command line [13:54:02] firefox open and test is run [13:54:19] geekman-rohit: did you try grunt perf --verbose again? [13:54:24] after the global install? [13:54:33] I started clean, now my npm isntall fails [13:54:36] :( [13:54:42] for node-sass [13:54:51] ofalvai: can you remove firefox from the config and try? [13:55:21] ofalvai: one of the gists you posted only showed firefox failures [13:55:56] it's the same without firefox [13:56:20] i edited perfjankie.js, i hope that's what you meant [13:57:00] yes [13:59:59] works!! [14:00:01] problem is [14:00:10] chrome driver is different for windows [14:00:12] :) [14:00:52] ah well thats from npm [14:01:01] we dont specificy the download directly [14:01:05] the download is an exe file, I changed start-selenium-server.js to point to the chrome driver I downloaded [14:01:10] and all is working fine :) [14:01:17] oh i see [14:01:31] ill have to add a check for that [14:01:59] http://chromedriver.storage.googleapis.com/index.html?path=2.14/ [14:02:06] this is where i downloaded the driver from [14:02:32] noticed the error when I ran only for firefox, that was working fine [14:02:39] geekman-rohit: what is the file thats downloaded by npm in node modules [14:02:45] so I guessed it was to do with chroe driver [14:03:15] just "chromedriver" [14:03:26] looks like thats the linux/unix driver [14:03:55] ill look into it [14:04:25] nope, found the right file too [14:04:26] hmm says it should work for windows [14:04:29] its in the lib folder [14:04:32] for windows [14:04:34] ok [14:06:16] node_modules/chromedriver/lib/chromedriver/chromedriver.exe is the path of the chrome driver for windows [14:07:00] geekman-rohit: thank you [14:07:11] nah, it was fun :D [14:07:32] and now i can test on firefox too :) which didnt work o my linux, so makes me happy :D [14:08:30] geekman-rohit: oh right you were stuck with the incompatible versions there right? [14:09:14] yes, worked fine on my ubuntu VM, some problem with fedora installation I guess [14:09:46] geekman-rohit: not super suprised its only fixed in the very newest osx version [14:10:26] so editing start-selenium-server.js should solve my problem as well? [14:10:48] lets hope that [14:11:25] edit the chrome driver path in start-selenium-server.js to node_modules/chromedriver/lib/chromedriver/chromedriver.exe [14:11:33] and try grunt perf? [14:11:56] "The environment you requested was unavailable" [14:12:11] for every test [14:12:34] geekman-rohit: want to test a fix for me? [14:12:42] sure! [14:12:54] but firefox works, yaay [14:13:00] ofalavi, I was runing from cmd, didnt try from sygwin [14:13:03] cygwin [14:13:09] just a sec im going to gist a fix [14:13:37] why dont you remove chrome from perfjankie.js? [14:13:45] keep everything else the same [14:15:32] ofalavi, try that: keep everything else same, just remove "chrome" from the browsers array in perfjankie.js [14:15:43] keep all other settings default [14:16:33] it works [14:17:22] but why doesn't chrome work for me? [14:17:28] now add chrome [14:17:38] geekman-rohit: https://gist.github.com/arschmitz/5b259c6c3e65c1870a04 [14:17:39] and make sure the path you set.. chromedriver.exe is right [14:18:01] serverOptions: {"Dwebdriver.chrome.driver=node_modules/chromedriver/lib/chromedriver.exe": ""}, [14:18:04] like this? [14:18:28] ofalvai: your missing a chromedriver/ in there [14:19:35] oh...now everything works :) [14:20:09] ofalvai: want to try the gist above for me [14:20:46] arschmitz, environment not available problem [14:20:59] geekman-rohit: ok just a sec [14:21:03] though I don't see how :( the path is right, though absoulute [14:28:25] geekman-rohit: ofalvai: https://gist.github.com/arschmitz/5b259c6c3e65c1870a04 [14:28:28] that should work now [14:29:12] yes, it works [14:29:20] it does :) [14:29:41] umm I'll test on linux tomorrow ? [14:30:26] i can launch a ubuntu vm [14:31:04] awesome [14:31:08] that should work everywhere [14:31:14] ill fix it [14:31:59] that should, cool [14:36:27] arschmitz, any specific reason for repeating tests twice? [14:40:55] it takes an average [14:42:52] geekman-rohit: makes the results slightly less finiky [14:45:14] understood, thanks :) [14:45:37] I'll do the BEM next week after I submit the GSOC proposal [14:47:39] geekman-rohit: cool kendo is very high priority too [14:48:12] i think after that its more components [14:48:29] You said someone else was working on it? [14:48:38] ah right [14:48:42] prasun I guess [14:48:50] yup i think so [14:49:26] i just landed his other one last night so he will probably do it soon [14:50:43] yep, I got the notification.. [20:11:23] [css-chassis] arschmitz opened pull request #54: Performance: Make path to chromedriver windows friendly (master...chromedriver-location) http://git.io/pdju [21:16:22] hello [21:16:48] @sfrisk [21:17:06] hellp [21:17:08] hello* [21:17:57] Im going to apply for jquery foundation so I need some help. [21:18:50] what kind of help are you looking for? [21:19:59] im applying for chasis - themeroller , so what you expect in that project? [21:21:37] For the themeroller project you would be using a nodejs backend. We're looking for something similar to what you can find in the mobile themeroller: http://themeroller.jquerymobile.com/ [21:23:25] You should be able to change the SCSS variables to generate not only updated CSS, but also raw scss files. [21:23:48] it should also generate a json file [21:24:29] that has the variables that were changed that can be uploaded to the server to recreate the theme later, to help make upgrading chassis easier [21:25:59] okay!!!! [21:26:10] thank you. [21:26:14] no problem [21:26:23] hopefully that helps [21:30:47] Can I get some further help , if I get problem in coding??? [21:31:07] @sfrisk [21:31:26] part of the job of being a mentor is to help you out if you need it [21:31:52] prior to gsoc starting, and probably the first week or so, we'll also have to work out the wireframe and design of the page [21:33:08] okay, I can do that. [21:36:01] can i get your mail id?? [21:36:31] my email is on github [21:37:04] also I would suggest if you haven't already, read through the issues on css-chassis, especially ones tagged Phase One, since that's what will be effected by the themeroller [21:37:10] and join in on conversations [21:37:29] also we have our weekly meeting on Tuesday, at 1PM EST in #jquery-meeting [21:37:58] okay. Got it [21:39:15] thank you very much! [21:39:48] bye [21:39:56] no problem!