[00:00:35] awight: haaa. ah. Ow. [00:01:54] hey again ejegg [00:02:18] hi atgo [00:03:14] i was going to ask you about the status 800's not getting into civi task [00:03:15] AndyRussG: that's odd. cos Krinkle was mentioning to me that we should move towards including all the logic to run tests, in the repo under test. But this grunt-karma-qunit thing has gone really far in the opposite direction... [00:03:25] but now i read it a bit more thoroughly and it looks like there are still open questions. [00:03:47] awight: It looks that way but it isn't. [00:03:56] awight: It's all in mediawiki-core/Grunt, not in Jenkins [00:04:11] so... basically nevermind. let me know if it feels like a sand trap though and we can reconsider if we want to keep digging at it [00:04:15] Just like phpunit has been for years, mediawiki-core. [00:04:39] Krinkle: ok, I'm looking for the new howto, for running qunit from the CLI... thanks! [00:04:41] Krinkle: hi! [00:05:22] Of course, for testing code that does not depend on mediawiki, the logic can just be in the repo. But for mediawiki extensions specifically, no logic has to be duplicated in each extension repo. You install the extension and run mediawiki's qunit test. [00:05:40] So for qunit the "repo" is mediawiki-core. Not the extension repo. That's all :) [00:06:06] atgo: they're definitely worth investigating! [00:06:17] Similar to how one registers phpunit test suites and then run phpunit.php in mediawiki core tests/phpunit [00:06:24] Krinkle: also I am compelled to mention that mediawiki-core/phpunit is not a success story! That thing has been broken for so long... [00:06:29] Let me know if you need any help registering the qunit tests. Although I think you've got that already. [00:06:31] yeah sounds good. I just saw your comment about the one that you solved and then actually read the rest and saw it wasn't totally solved :) [00:07:00] awight: Broken in what way? (btw, I'd be first to say it needs re-doing. It was this way when I got here, but it's on the list.) [00:07:12] Krinkle: Your narrative sounds good, though :) It definitely makes sense to reuse the testing logic. [00:07:17] Yeah, when I try to replicate that failure at 600 status locally, everything goes boom [00:07:32] Krinkle: PHPUnit is a huge nightmare on most fresh installs, in my experience. [00:07:37] So i'm not even sure how prod kept going and logged anything after that [00:07:42] With most projects, you stroll to the top level and "phpunit". [00:08:08] awight: If your code is independent and does not need mediawiki core classes or anything. Then you can totally run phpunit within the repo directly. See https://github.com/wikimedia/cdb and https://github.com/cssjanus/php-cssjanus for examples. [00:08:11] For MediaWiki core, it's this arcane commandline, and it doesn't work out of the box. Requires root privs, then 99% of the time it fails cos of that stupid PHAR thing. [00:08:35] wait, what about phpunit requires root privs? [00:08:45] Krinkle: well, yeah. But IMO it should do the right thing and run the entire test suite from the top level, including any enabled extensions. [00:08:46] And same for qunit. See oojs, and oojs-ui and visualeditor repos for a local Grunt qunit/karma example. pure 'npm install && npm test' [00:09:03] ejegg: it wants to install phpunit... in a way that is not compatible with what it expects to execute. [00:09:22] oh man, I must have erased that part from my memory [00:09:31] awight: phpunit itself being the nightmare or our use of it, or a specific distributions' package? Not sure I understand what you mean. [00:09:37] running phpunit via make is also a little funky [00:09:43] Krinkle: sorry, I'm not *trying* to start a flame war about the test harnesses, but... they really don't work well for me. [00:09:45] Run it via composer :) [00:09:49] heh [00:09:50] Krinkle: just getting back to this finally, BTW... I feel like the quesitons I'm gonna ask are probably be dumb and discoverable in the JJB config, but... so u said before, "Use npm install && grunt qunit from the MediaWiki core directory to run QUnit tests from the command-line in you local Chrome browser." ... tried that but it didn't work.... [00:10:30] AndyRussG: OK. Let's debug. What doesn't work? [00:10:40] Krinkle: let me back out further... I'd like to help fix the phpunit situation, some day :D [00:10:42] awight: root privs needed to run phpunit? huh don't recall that [00:10:45] It's important to me that this is documented well enough to not need my intervention. [00:11:03] AndyRussG: no, this is for the phpunit.php script to install PHPUnit on a fresh deployment. [00:11:06] So by all means ask anything you like :) [00:11:21] Krinkle: yes, the immediate issue is that we'd like to run qunit from the CLI [00:11:31] $ grunt qunit [00:11:31] Running "karma:main" (karma) task [00:11:31] Warning: Parameter 'url' must be a string, not number Use --force to continue. [00:11:31] Aborted due to warnings [00:11:49] (CR) Ejegg: "The code looks good! whitespace is inconsistent though." (1 comment) [extensions/DonationInterface] - https://gerrit.wikimedia.org/r/189136 (https://phabricator.wikimedia.org/T86251) (owner: Awight) [00:12:03] This script: https://github.com/wikimedia/mediawiki/blob/master/tests/phpunit/install-phpunit.sh is pretty horrible yeah. It won't be neccecary once we fetch phpunit via composer-install as devDependency. [00:12:06] awight: ah hmmm yeah I think I did have to install qunit somehow [00:12:28] awight: sorry I meant phpunit [00:12:35] AndyRussG: Latest mediawiki-core? node --version, npm --version, grunt --version [00:12:47] Krinkle: yes updated mwcore for this... [00:13:08] $ node --version [00:13:08] v0.10.29 [00:13:15] AndyRussG: Also be sure to have MW_SERVER and MW_SCRIPT_PATH set in your bash env. [00:13:31] Unfortunately npm does not install MediaWiki. That's a prerequisite. [00:13:32] $ grunt --version [00:13:32] grunt-cli v0.1.13 [00:13:32] grunt v0.4.5 [00:14:05] Krinkle: hmmm that sounds like something [00:14:38] Krinkle: yea thos are not set [00:14:44] e.g. export MW_SERVER='http://localhost' MW_SCRIPT_PATH='/w' [00:15:41] Krinkle: the URL for the local install I'm working with is http://localhost/mw1/index.php/Main_Page [00:16:14] $wgServer = "http://localhost"; [00:16:16] Krinkle: Perhaps the test harness should assert that those env vars are set... [00:16:39] $wgScriptPath = "/mw1"; [00:16:57] It would be nice if there were a channel for sending configuration data from PHP -> js, also [00:18:01] OK that's getting somewhere... [00:18:02] grunt qunit [00:18:02] Running "karma:main" (karma) task [00:18:02] INFO [karma]: Karma v0.12.31 server started at http://localhost:9876/ [00:18:02] INFO [launcher]: Starting browser Chrome [00:18:04] ERROR [launcher]: Cannot start Chrome [00:18:07] Can not find the binary google-chrome [00:18:09] Please set env variable CHROME_BIN [00:18:11] Warning: Task "karma:main" failed. Use --force to continue. [00:18:13] Aborted due to warnings. [00:18:43] AndyRussG: What OS, do you have Chrome installed? [00:18:45] Krinkle: This could be part of a compile step... for now, it could run as a Composer script, and dump a .json file or something. [00:19:03] awight: phpunit? [00:19:52] Krinkle: yes, on Debian [00:19:58] BTW it worked! [00:19:59] Krinkle: no, I was muttering that, it sounds like we need a compilation step which checks that the LocalSettings.php (etc) is synced to a .json file, which can be discovered by Grunt. [00:20:08] AndyRussG: great! [00:20:41] Or I mean, it ran tests and opened chrome [00:20:53] in reverse order ^ [00:20:55] $ grunt qunit [00:20:55] Running "karma:main" (karma) task [00:20:55] INFO [karma]: Karma v0.12.31 server started at http://localhost:9876/ [00:20:55] INFO [launcher]: Starting browser Chrome [00:20:56] INFO [Chrome 40.0.2214 (Linux)]: Connected on socket PYcXWzbNcI_a5LUJc0xO with id 28723612 [00:20:58] ................................................................................ [00:21:00] ................................................................................ [00:21:03] .................. [00:21:05] LOG: 'Exception thrown by test.module1' [00:21:07] ERROR: 'Error: expected', Error{} [00:21:09] ................................................................................ [00:21:12] ... [00:21:14] Chrome 40.0.2214 (Linux): Executed 261 of 261 SUCCESS (4.561 secs / 4.529 secs) [00:21:16] Done, without errors [00:21:17] awight: The problem is with multi-wiki setups. If it's a single-wiki setup, one can just shell out to maintenance/eval.php and echo $wgServer, or maintenance/getConfiguration.php [00:21:40] However I didn't do that for now as in most environment that install mediawiki (e.g. jenkins, vagrant) can already pre-expose those variarbles. [00:21:45] And locally I just add them to bash_profile [00:21:54] next to the MW_DB you already need for maintenance scripts in extensions [00:22:17] AndyRussG: Nice. What did you do to make it work? [00:22:40] Krinkle: ah, yeah multi-wiki has bitten me too. FWIW, we have to deal with a new multiwiki scenario, where we check out an entire mw-core tree at a different revision than master (for payments.wikimedia.org vagrant). [00:22:40] export CHROME_BIN='/usr/bin/chromium' [00:22:42] It couldn't auto-discover chrome the first time? [00:22:47] Ah, Chromium [00:23:00] Yeah, it only looks for Chrome (in about a dozen different places) but not Chromium. [00:23:03] I have a patch for that upstream. [00:23:10] Ah hmmm :) [00:24:15] Krinkle: out of curiousity, why does it say, "ERROR: 'Error: expected', Error{}"? [00:24:27] AndyRussG: part of some random unit test [00:24:45] That tests the ResourceLoader handling of exceptions [00:24:50] which qunit then logs to the console [00:25:01] Should be mocked in some way [00:25:14] Aaaaah I see, cute :) [00:25:37] I guess that's the explanation for the preceeding line, too, and also the fact that it ends with "Done, without errors" [00:25:40] Krinkle: I'm shooting in the dark from the hip here (ahem...), but maybe the multiwiki configuration should be represented in the .json thing I'm imagining, so you can run "grunt --wiki default qunit" and so on. [00:26:26] AndyRussG: getConfiguration.php already supports that as being a maintenance script. [00:26:40] Maintaining and syncing a file seems messy. [00:27:10] So we could pass --wiki on to that [00:28:18] Krinkle: that would be perfect. [00:29:49] Krinkle: awight: woot! I re-enabled CentralNotice on the wiki I'm testing with, and all the tests pass again! [00:30:58] And yea it does run the CN tests... the number of tests run went from 261 to 335, and we have exactly 74 CN qunit tests [00:35:01] Great [00:35:12] yeah! [00:35:28] Now looking at the integration config again... [00:45:18] AndyRussG: So, you'll want to add an entry for '{name}-{ext-name}-qunit-karma' in the jobs section of mediawiki-extension and invoke it with CentralNotice. Similar to what it does for the non-karma qunit variant already. [00:45:36] (PS4) Awight: Use common code for Adyen form handling [extensions/DonationInterface] - https://gerrit.wikimedia.org/r/189136 (https://phabricator.wikimedia.org/T86251) [00:45:50] And then enable it in zuul.layout.yaml for the 'test' and 'gate' pipeline. And probably non-voting for now as it's still in flux while I finetune it. [00:46:10] Krinkle: yurp... [00:46:26] I was also looking at mwext-VisualEditor-qunit-karma, but I guess that has stuff that's special for VE [00:47:37] (L204+ [00:47:38] ) [00:48:56] Yeah [00:49:03] The '{name}-{ext-name}-qunit-karma' template should work for CN [00:51:27] K [00:52:11] * AndyRussG studies new-for-me files [00:54:09] In that layout.yaml for CN we have currently only this: [00:54:09] - name: mediawiki/extensions/CentralNotice [00:54:09] template: [00:54:09] - name: extension-qunit [00:54:09] - name: extension-unittests [00:54:12] - name: extension-rubylint [00:56:14] others have no template prop but gate-and-submit, test and check, and some have all four... ah there's aslo one with experiemntal: [00:56:21] bear with me, I'll get it in a sec :) [00:59:15] (CR) Ejegg: [C: 2] "Nice! I wonder if GatewayResultPage should be a subclass of GatewayPage with this default handleRequest behavior." [extensions/DonationInterface] - https://gerrit.wikimedia.org/r/189136 (https://phabricator.wikimedia.org/T86251) (owner: Awight) [00:59:37] (Merged) jenkins-bot: Use common code for Adyen form handling [extensions/DonationInterface] - https://gerrit.wikimedia.org/r/189136 (https://phabricator.wikimedia.org/T86251) (owner: Awight) [00:59:42] (PS11) Ssmith: Data retrieval/superclassing. [wikimedia/fundraising/dash] - https://gerrit.wikimedia.org/r/190343 [01:02:54] Krinkle: awight: https://gerrit.wikimedia.org/r/#/c/194773/ [01:04:23] ah right, non-voting... [01:05:08] (PS1) Ejegg: Clean up some Adyen cruft [extensions/DonationInterface] - https://gerrit.wikimedia.org/r/194774 [01:07:01] (CR) Ssmith: [C: 2] Lint all js except node_modules and bower_modules [wikimedia/fundraising/dash] - https://gerrit.wikimedia.org/r/194389 (owner: Ejegg) [01:13:47] Mmmm eats! backsoon... Thanks much Krinkle awight [01:17:19] I thought he was a bassoon. [01:17:21] Huh. [01:40:20] (CR) Ejegg: "Some initial observations, will look again in the morning" (10 comments) [wikimedia/fundraising/dash] - https://gerrit.wikimedia.org/r/190343 (owner: Ssmith) [01:40:36] good night all [01:43:21] hey awight [01:43:25] good night ejegg|away! [01:52:47] atgo: hi! [16:49:44] Hey awight... How's Mari doing? [16:51:34] Oh thx! We're giving her the eye drops, she's doing well. [16:56:35] Ah glad to hear :) [16:57:46] awight: do you think it's not too late to write a proposal for Wikimania for the more general Editor Campaigns idea? [16:58:31] I bet they'd not say now [16:58:32] no [17:00:33] AndyRussG: We should probably ask the selection committee first... it's definitely past the deadline, and they're rejecting proposals out of hand, cos: https://wikimania2015.wikimedia.org/wiki/Submission_review#Disqualified [17:00:46] Oooh! really darn [17:01:03] There might be an alternative, though... unconference sessions or something? [17:03:28] It's a talk that could be given again and again, until everyone is on board :) [17:03:53] awight: yeah that sounds better, then. Drat! sorry for my inactionly tardiness bla bla etc [17:04:10] Even disqualifying WMF employees! [17:04:20] Well, I guess it's a popular venue then [17:05:20] Me too [17:05:32] awight: all the disqualifieds have no abstract [17:05:34] I barely squeaked my crypto-branching proposal through ;) [17:05:39] AndyRussG: that is true. [17:05:57] I wouldn't mind writing / collaborating on an abstract anyway, and we can reuse if rejected... [17:06:50] Hahah I was still copy editing and watching the clock, and I had one minute left, and was wondering if the server clock might be 30 seconds ahead of my laptop's [17:07:26] oh dear :) [17:07:49] I see someone who got disqualified for submitting before midnight D.F. time! [17:07:57] (organizers meant, UTC) [17:08:17] AndyRussG: you have something written? [17:08:26] No... [17:08:54] ...but ther'es doc that'd be a fine starting point... sounds like a good idea! We could write the submission, and ask the committee if they want to consider it, and if not, what they suggest [17:09:11] And could also ask Quim if there might be a place for it at the Wikimania hackathon [17:09:55] I like the idea of presenting the whole package, of several interoperating components... e.g. include Gather and Workflow in the vision. [17:10:05] hehe s/e.g./i.e./ [17:10:11] awight: that sounds like a great idea [17:10:19] +1 sneaking in via the hackathon [17:10:56] We could write it up but not put it immediately on the Wikimania wiki but somewhere else draft-ish [17:11:02] and see what they sez? [17:11:15] Or should we put it where all the submissions go? [17:17:43] Wikimedia-Fundraising-CiviCRM, Continuous-Integration, Fundraising Tech Backlog, Release-Engineering, and 2 others: Create CI slave instance for CiviCRM testing - https://phabricator.wikimedia.org/T89894#1095906 (awight) Created a m1.small instance, and following these instructions: https://wi... [17:19:12] AndyRussG: donno, we might as well try to sneak it into the middle of the pile of submissions ;) DaTE: feb 15 [17:49:45] awight: so how should we proceed? when is a good time for you to work on something? [17:50:03] i.e. should we each write some notes, maybe then do a hangout, etc? [17:50:13] or whatever u think would work best [17:50:52] Any time! I'm spending the day working on setting up a CI slave on labs, it's a good thing to interrupt frequently ;) [17:52:10] awight: OK! How about in a couple hours or so? [17:52:20] AndyRussG: pls send me the etherpad link we were working on... different computer... [17:52:23] sure! [17:52:58] awight: http://etherpad.wikimedia.org/p/ContinuingEditorCampaigns [17:59:59] (PS13) AndyRussG: Preload JS comes with no baggage [extensions/CentralNotice] - https://gerrit.wikimedia.org/r/181244 (owner: Awight) [18:17:35] Wikimedia-Fundraising-CiviCRM, Continuous-Integration, Fundraising Tech Backlog, Release-Engineering, and 2 others: Create and provision CI slave instance for CiviCRM testing - https://phabricator.wikimedia.org/T89894#1096112 (awight) [18:28:10] Wikimedia-Fundraising-CiviCRM, Continuous-Integration, Fundraising Tech Backlog, Release-Engineering, and 2 others: Create and provision CI slave instance for CiviCRM testing - https://phabricator.wikimedia.org/T89894#1096172 (awight) [18:28:32] Wikimedia-Fundraising-CiviCRM, Continuous-Integration, Fundraising Tech Backlog, Release-Engineering, and 2 others: Create and provision CI slave instance for CiviCRM testing - https://phabricator.wikimedia.org/T89894#1096173 (awight) Open>Resolved [18:28:33] Wikimedia-Fundraising-CiviCRM, § Fundraising Sprint Abba, § Fundraising Sprint Beastie Boys, § Fundraising Sprint the Cure, and 5 others: Deploy CiviCRM integration job to WMF integration server - https://phabricator.wikimedia.org/T86374#1096174 (awight) [18:30:00] Wikimedia-Fundraising-CiviCRM, Continuous-Integration, Fundraising Tech Backlog, Release-Engineering, and 2 others: Configure Jenkins to run CiviCRM builds on Fundraising CI slave instance - https://phabricator.wikimedia.org/T89895#1096178 (awight) [18:30:18] Wikimedia-Fundraising-CiviCRM, Continuous-Integration, Fundraising Tech Backlog, Release-Engineering, and 2 others: Configure Jenkins to run CiviCRM builds on Fundraising CI slave instance - https://phabricator.wikimedia.org/T89895#1048130 (awight) [18:33:28] (PS1) Awight: Move integration scripts into this repo [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 [18:33:59] (PS2) Awight: Move integration scripts into this repo [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) [18:34:15] ejegg|errant: If you have a minute to kickme, ^^ [18:53:47] (PS3) Awight: Move integration scripts into this repo [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) [18:55:02] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [18:57:06] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [18:59:58] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [19:10:53] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [19:13:17] awight: sure, one sec [19:13:39] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [19:13:55] ejegg|errant: actually, I'm still tweaking on those... [19:14:40] (PS4) Awight: WIP Move integration scripts into this repo [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) [19:15:27] ahh, I see. lmk when they reach steady state [19:15:35] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [19:15:59] ejegg|errant: It's been fun :) I think we're only a few days away from Civi CI, though! [19:18:03] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [19:20:43] woohoo! [19:21:17] (PS12) Ssmith: Data retrieval/superclassing. [wikimedia/fundraising/dash] - https://gerrit.wikimedia.org/r/190343 [19:25:08] (Abandoned) Ssmith: Save configuration for fraud gauge. [wikimedia/fundraising/dash] - https://gerrit.wikimedia.org/r/189840 (https://bugzilla.wikimedia.org/86836) (owner: Ssmith) [19:52:44] (PS1) Awight: HHVM compatibility when using "php -r" [wikimedia/fundraising/civicrm-buildkit] - https://gerrit.wikimedia.org/r/194937 [19:54:24] ejegg: if u can, ^ [19:54:39] sure thing, just playing with php -r ! [19:56:34] heh, they really like PHP. I guess some of that logic would be more complicated in pure shell script [19:56:38] wat. [19:56:44] oh, yeah exactly [19:56:51] hehe I misread that as "I really like PHP"! [19:56:57] heh [19:57:11] haven't drunk that much of the koolaid yet [19:57:32] I think this change is better for even the Zend PHP, cos it protects against arguments that might have special meanings 'n' stuff. [19:57:41] Yeah, they don't make kool-aid strong enough. [19:58:01] (CR) Ejegg: [C: 2] HHVM compatibility when using "php -r" [wikimedia/fundraising/civicrm-buildkit] - https://gerrit.wikimedia.org/r/194937 (owner: Awight) [19:58:10] (CR) Ejegg: [V: 2] HHVM compatibility when using "php -r" [wikimedia/fundraising/civicrm-buildkit] - https://gerrit.wikimedia.org/r/194937 (owner: Awight) [19:58:11] I hope u haven't looked at the src code for PHP? [19:58:32] no, why? [19:58:36] That horrifying? [19:58:42] yeah [19:58:53] it's like a high school compiler-writing exercise [19:59:04] i'll continue in my blissful ignorance then [19:59:25] ifelse OPCODE='if' then do some hair-raising bloated C thing... [19:59:55] hehe, at least they resisted the urge to optimize. [20:00:44] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [20:04:37] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [20:10:45] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [20:14:14] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [20:16:39] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [20:29:15] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [20:32:00] (CR) Awight: "check experimental" [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) (owner: Awight) [20:32:04] ahem... [20:37:47] ahem? [20:38:27] awight: I was gonna look at the EditorCampaigns/Edu stuff finally, if u have a chance... [20:39:12] Just gonna add some brainstorming to the etherpad [20:42:06] AndyRussG: we were just about to lunch, how about 4:30 EST? [20:42:21] awight: sure, that's perfect :) [20:42:28] ok, thanks! [20:42:32] likewise! :) [20:42:41] Does that mean that standup is unstood? [20:44:28] (PS1) Awight: update packages [wikimedia/fundraising/civicrm-buildkit/vendor] - https://gerrit.wikimedia.org/r/194943 [20:45:15] (PS1) Awight: composer package updates [wikimedia/fundraising/civicrm-buildkit] - https://gerrit.wikimedia.org/r/194944 [20:48:52] AndyRussG: good point, I'll try to feign attendance :) [20:49:30] awight: heh I'm sure it's not that important! [20:51:26] In case I miss it--my standup is: I'm unblocked on the Civi continuous integration, I've got a slave instance provisioned and linked to a job which can be triggered by a comment on patches. It doesn't run correctly yet, so I'll be fixing that for a day or two. [20:52:25] ejegg|bike: more CI patches above... [20:53:20] (PS5) Awight: WIP Move integration scripts into this repo [wikimedia/fundraising/crm] - https://gerrit.wikimedia.org/r/194915 (https://phabricator.wikimedia.org/T78100) [20:57:56] (CR) Ejegg: [C: 2 V: 2] update packages [wikimedia/fundraising/civicrm-buildkit/vendor] - https://gerrit.wikimedia.org/r/194943 (owner: Awight) [20:58:30] ejegg: it's worse than I thought. Some of the civicrm-buildkit/vendor/* are not being checked in for random git reasons... [20:58:42] aah, thrilling [20:59:05] oh yeah, i see the git packages [20:59:10] u do? [20:59:13] dagnabbit [20:59:18] I mean in the composer.json [20:59:20] totten/amp is on purpose, but where do you see the others [20:59:21] oh [21:01:50] what a disaster. See vendor/phpunit/phpunit-selenium/.gitmodules [21:03:20] ejegg: awight: following pizzzacat's wise lead, shall we call standup an email? [21:03:28] oh ok [21:03:50] I'm OK joining the hangout too if u prefer :) [21:04:09] email is good! [21:04:35] ejegg: coo' ! [21:04:42] (short for "cool") [21:04:57] awight|lunch: buen provecho :) [21:40:35] AndyRussG: hi! I'm available any time... [21:45:36] awight: K one sec :) [21:46:20] Mari just had her first bike accident... 0mph, but still got gravel and leaves in the face! [21:46:54] aww [21:47:04] I suppose it was a tricycle accident. [21:47:22] you got that thing from your folks' place fixed up? [21:47:45] I did! that's even more dangerous, tho. This is a tricycle with stealth parent handle built in. [21:48:04] ah, nice [21:48:29] A generic one of these: http://ecx.images-amazon.com/images/I/411iWN1oTIL._SY300_.jpg [21:49:19] that parent handle doesn't look too stealthy [21:49:39] It's easy to ignore things at your back :) [21:50:27] ejegg: fyi, this is ridiculous, but I'm considering actually using composer from the CI box. nothin' to lose, eh? [21:50:49] awight: aww [21:50:51] o rly? [21:50:57] can we do that? [21:50:59] hmmmm [21:51:11] awight: also all set anytime re: campaigns etc [21:51:19] you mean on each checkin? [21:51:23] There's already some stuff which downloads "civix"... [21:51:33] ejegg: yeah, just on the CI box, to provision the testing env [21:51:41] AndyRussG: ok, hanging out... [21:52:19] you don't even want to see the weather here. [22:08:00] awight: looks like crm/civicrm branch dev-v4.4 last had our master patches merged in March of last year. Shall I merge in the stuff we've done since then, or do you have other plans? [22:14:28] awight what's the trick I'm supposed to do where gerrit complains I don't have a change ID? [22:17:23] pizzzacat: mmm... so this is not the latest commit? [22:18:20] ejegg: Sure, if you think the changes are sane. I honestly can't remember whether those were good or not. [22:18:49] Most of that was just bugfixing and compatibility stuff, which might have been fixed in a more recent civi upstream 4.4. release [22:18:55] pizzzacat: as a temporary measure, if the gerrit complaint contains a suggested ID, you can copy it, then do git commit --amend and paste it into the commit message [22:19:02] awight: cool, probably don't need most of 'em [22:19:10] I hopenot! [22:19:17] Oh, and I should do those on top of your contrib-v4.4 merge [22:19:54] awight: here's what Anke, the OPW intern, has been working on. Her stint with us is ending Monday, BTW https://www.mediawiki.org/wiki/User:Sputniza/Interview_guide_line [22:20:06] She also has a final report in the pipeline [22:21:30] (PS13) Ssmith: Data retrieval/superclassing. [wikimedia/fundraising/dash] - https://gerrit.wikimedia.org/r/190343 [22:21:40] ejegg: That sounds much better! [22:22:42] AndyRussG: What is that? An exit poll method for EP students? [22:23:04] awight: no, it's Anke's interviews for research design... Results at the bottom [22:23:18] Or mostly undistilled results [22:23:27] But who gets interviewed? [22:23:34] I think they were EP professores [22:23:46] OK i see, teachers and students [22:24:00] and it looks like, after they have used EP for a semester [22:24:51] She e-mailed a draft version of the final report but I dunno if it's on-wiki yet, I should ask before sharing I guess [22:25:27] The 3 examples are nice [22:25:38] AndyRussG: you want to continue hanging out? [22:26:16] I pinged yurik, but it was the end of the day, so no luck locating his .js workflow thing. [22:26:23] awight: sure, one sec, getting coffee [22:26:34] I think he said it was for the Zero portal... which unfortunately means we cannot access it, afaik [22:26:37] k [22:27:35] hehe, or I could dump the db :) [22:28:16] the problem was that I had too many change id's because it was a rebase/merge [22:28:21] awight: I haz coffee [22:28:26] :) [22:29:19] pizzzacat: yeah, rebase -i might not work on a merge commit, so my advice is to checkout the offending commit, then "git commit --amend", which will give it a Change-Id, then go ahead and cherry-pick the rest of your branch. [22:30:29] AndyRussG: u in there? I see your avatar :) [22:30:55] yeah I just had to delete the other commit msgs that weren't the one being actually committed [22:31:02] and then it worked [22:31:10] err change id's [22:31:35] whoa [22:31:40] delete? [22:31:46] yep [22:31:50] One sec [22:31:51] That sounds a bit odd, but I'm glad it worked for now :) [22:31:53] k [22:31:59] everything was squashed into one commit msg [22:32:05] from the other squashed commits [22:32:06] oooh right. [22:32:15] awight: I'm there again now [22:32:19] so I just got rid of the unnecessary ones [22:32:43] Yes, now it all makes sense! [22:32:53] :) [23:55:07] AndyRussG: I tossed a short abstract in that etherpad, fwiw [23:56:01] awight: nice! [23:56:34] I'm turning domestic for a bit but I'll get to it again sooooooooon :) [23:56:48] * AndyRussG prepares to scrub floors [23:57:42] lol, that's usually my job, too [23:58:14] the best way to find interesting stuff! [23:59:00] :D don't spend it all in one place...