[08:08:32] (PS9) Nuria: Adding coding guidelines to README.md file [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120542 [08:08:34] (CR) jenkins-bot: [V: -1] Adding coding guidelines to README.md file [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120542 (owner: Nuria) [08:52:05] (PS10) Nuria: Adding coding guidelines to README.md file [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120542 [08:57:20] (PS6) Nuria: Added tests for coalesced recurrent reports [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/122638 (owner: Csalvia) [11:02:51] (PS10) Nemo bis: Adapt dates used in test 10 to be relative to now [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [11:03:25] (CR) Nemo bis: "I merged the two commit messages proposals. I'm looking forward to seeing the tests pass!" [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [11:18:46] Nemo_bis++ [11:21:27] qchris++ [11:29:04] :) [11:29:05] Nemo_bis: hey, just notified Hashar that the tests didn't trigger. what's your e-mail so I can Cc you too ? [11:31:50] ah yeah, it was in gerrit all along [11:31:51] sorry [11:35:05] oh they did trigger [11:35:16] omg, I'm so silly [12:31:18] (CR) QChris: "> The analytics1012 issue is fixed, [...]" (1 comment) [analytics/kraken] - https://gerrit.wikimedia.org/r/121531 (owner: Ottomata) [12:32:04] yay! [12:50:49] (CR) QChris: [V: 1] "Yeah, sure. You like to see my name in commit messages :-(" [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [13:42:16] (PS11) Nemo bis: Adapt dates used in test 10 to be relative to now [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [13:42:51] (CR) Nemo bis: "Sorry for the name. If you actively dislike mentions, you should feel free to directly remove them." [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [13:54:27] (CR) QChris: [C: 1] "> Sorry for the name." [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [14:01:09] ottomata: Standup :-D [14:01:22] ack [14:19:03] (CR) Stefan.petrea: "In a previous life, in a standup meeting, I mentioned that for change 96738 I would prefer to have only comments , and not patchsets from " [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [14:58:50] (CR) Stefan.petrea: "Note for the brave and the corageous: Feel free to make any action on this gerrit change." [analytics/kraken] - https://gerrit.wikimedia.org/r/96738 (owner: QChris) [15:01:44] hey, i have a few atom.io invites, if anyone wants [15:01:56] it seems cool, but also kinda slow for me [15:07:02] freenode is being flaky today [15:44:05] whois ottomata [15:49:00] * average thinks a leading / was missed [15:50:59] whois j0kr?!?!?! [15:51:01] EH?! [15:51:01] EH!? [15:51:06] :p [15:51:25] I'm Kevin. [15:51:39] I don't have a cloak set up yet. [15:52:38] qchris_away: ah you are away [15:53:54] (CR) Ottomata: "Interesting." [analytics/kraken] - https://gerrit.wikimedia.org/r/121531 (owner: Ottomata) [15:56:02] (PS4) Ottomata: Adding camus wrapper script and camus properties file [analytics/kraken] - https://gerrit.wikimedia.org/r/121531 [17:04:03] ottomata: re. What's up? [17:05:20] yo, nuthin, just the patchset [17:06:22] Oh. Ok. [17:06:30] I just reviewed it and wondered ... [17:06:44] Do we actually rebase commits or just merge for kraken? [17:06:51] I guess just merge ... right? [17:07:34] (CR) QChris: [C: 2] Adding camus wrapper script and camus properties file [analytics/kraken] - https://gerrit.wikimedia.org/r/121531 (owner: Ottomata) [17:07:43] i'd rebase, but whatever [17:07:53] (PS5) QChris: Adding camus wrapper script and camus properties file [analytics/kraken] - https://gerrit.wikimedia.org/r/121531 (owner: Ottomata) [17:08:09] (CR) QChris: [C: 2 V: 2] Adding camus wrapper script and camus properties file [analytics/kraken] - https://gerrit.wikimedia.org/r/121531 (owner: Ottomata) [17:27:32] (CR) Milimetric: [C: 2] Add ability to create recurrent reports via UI [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/112165 (owner: Milimetric) [18:09:01] (CR) QChris: [C: 2] Adapt dates used in test 10 to be relative to now [analytics/wikistats] - https://gerrit.wikimedia.org/r/123603 (owner: Stefan.petrea) [18:14:05] (Abandoned) QChris: DO NOT COMMIT. Dummy commit to have Jenkins rerun tests [analytics/wikistats] - https://gerrit.wikimedia.org/r/123595 (owner: QChris) [18:14:20] (PS3) QChris: Fix typo [analytics/wikistats] - https://gerrit.wikimedia.org/r/118257 (owner: Nemo bis) [18:14:28] (PS3) QChris: Comment some path tests which overrode standard ones [analytics/wikistats] - https://gerrit.wikimedia.org/r/118261 (owner: Nemo bis) [18:14:34] (PS3) QChris: Remove all trailing whitespace [analytics/wikistats] - https://gerrit.wikimedia.org/r/118266 (owner: Nemo bis) [18:14:42] (PS5) QChris: Typofix in comments [analytics/wikistats] - https://gerrit.wikimedia.org/r/118366 (owner: Nemo bis) [18:14:50] (PS5) QChris: [Full dump analysis] Reduce edits_only and reverts_only intricacy [analytics/wikistats] - https://gerrit.wikimedia.org/r/118436 (owner: Nemo bis) [18:21:50] (CR) QChris: [C: 2] Fix typo [analytics/wikistats] - https://gerrit.wikimedia.org/r/118257 (owner: Nemo bis) [18:23:48] (PS6) QChris: Typofix in comments [analytics/wikistats] - https://gerrit.wikimedia.org/r/118366 (owner: Nemo bis) [18:24:37] (CR) QChris: [C: 2] Typofix in comments [analytics/wikistats] - https://gerrit.wikimedia.org/r/118366 (owner: Nemo bis) [18:26:09] (PS4) QChris: Typofix in squids report [analytics/wikistats] - https://gerrit.wikimedia.org/r/100368 (owner: Nemo bis) [18:27:08] (CR) QChris: [C: 2] Typofix in squids report [analytics/wikistats] - https://gerrit.wikimedia.org/r/100368 (owner: Nemo bis) [18:29:02] (PS4) QChris: Move download limiter to proper place and comment it as it's only a test [analytics/wikistats] - https://gerrit.wikimedia.org/r/92056 (owner: Nemo bis) [18:29:32] (PS3) QChris: Add perl dependencies to a CollectMailArchives.pl comment [analytics/wikistats] - https://gerrit.wikimedia.org/r/91998 (owner: Nemo bis) [18:29:48] wohooooo success [18:29:52] (PS3) QChris: Archives are downloaded in .txt.gz format: fix matching and opening [analytics/wikistats] - https://gerrit.wikimedia.org/r/92066 (owner: Nemo bis) [18:31:14] Nemo_bis: I merged all the things that I could easily verify and were sufficiently small. [18:31:20] The dashboard at [18:31:25] https://gerrit.wikimedia.org/r/#/projects/analytics/wikistats,dashboards/default [18:31:30] is now much cleaner. [18:31:49] Is it ok if I leave the rest for ezachte, as I do not understand too much of wikistats? [18:38:15] * average thinks 63478 could be closed on bugzilla [18:44:40] * qchris thinks average is right. [18:44:50] I closed the bug. [18:45:43] nice :) [19:21:20] (CR) QChris: "> I suspect that these errors have something to do with the fact that" [analytics/kraken] - https://gerrit.wikimedia.org/r/121531 (owner: Ottomata) [19:34:55] Not sure about policies ... [19:35:15] Say $PERSON is a volunteer, and signs an NDA. Can she get access to stat1003? [19:37:22] Hey qchris. That is a good question. [19:37:38] I'm not aware of a policy. I suppose ottomata might be. [19:38:18] In the past, managers were given access to stat1/003 upon request. [19:38:20] Ok. I guess I'll have to wait until ottomata is back. [19:38:27] yeah, it's more of an Ops question. [19:38:44] I know we've had volunteers with /root/ in the past, but none are active any more. [19:38:54] There are some volunteer home directories on stat1/stat1003, so I thought ... maybe :-D [19:39:26] now-volunteers or always-volunteers? [19:39:32] ^ [19:39:56] because we suck at cleaning up after ourselves [19:40:03] Some now-volunteers. Some where I am not sure. [19:40:06] Leslie still has her home directories. No way to get to them, because she left, but.. ;p [19:40:10] examples of the latter? [19:40:29] No. [19:40:42] I do not want to be responsible of people loosing their account. [19:40:50] (If they still had it as an oversight) [19:41:14] Seems like they should though. [19:41:33] Depends :-) [19:41:36] well, plus they presumably don't have valid SSH keys, rendering it irrelevant [19:41:42] in fact, have you looked at it that way? [19:41:48] compare the directory list to the puppet manifest. [19:42:18] If there are entries that are in one but not in the other, they should probably be discounted from any calculation of our current practices. [19:42:35] Puppet files need not reflect policies or possibilities. [19:43:00] Hey milimetric. If I needed to file a request for some support from analytics devs, where's the right place to do that? [19:43:05] Ottomata will remove doubt when he comes back :-) [19:43:24] * halfak is not sure who to bother about these things until Kevin is on IRC [19:43:53] Actually, qchris might know. See my message to milimetric above. [19:45:18] halfak: Sounds like you need help right away. Can do your support thing right away? [19:45:23] Or does it take more time? [19:45:39] I'm going to need some data purged from EventLogging after a 90 day window per our data retention guidelines. [19:45:47] I suspect the process to be easy. [19:45:59] But I need to know that someone will do it before we start collecting the data. [19:46:18] I guess that part has to go through our product owner. [19:46:25] is it gonna be purged from the json deep storage files too? [19:46:28] and any backups we have? [19:46:28] Is that Kevin? [19:46:37] Yes yuvipanda [19:46:51] "deep storage files" [19:47:01] alright. do keep me in the loop when that happens, halfak [19:47:17] *cold* storage files might be a better description but deep storage sounds cooler [19:47:23] * yuvipanda digs a 10km hole for storage [19:47:38] 10km hole is pretty deep. [19:48:22] http://imgur.com/6PSKTU3 [19:48:32] haha [19:48:39] qchris, no, my point was that if volunteers have file storage but not access to that file storage, it probably indicates they're in the category of "people who left" [19:49:42] yuvipanda, re. loop keeping. Affirmative. :) [19:49:49] halfak: :) [19:50:34] halfak: Kevin is j0kr (with a zero) in case you didn't know [19:50:35] Ironholds: Good point. However ... stat1003 should be fairly clean of "people who left" [19:50:48] s'true [19:50:52] Wut! [19:51:02] * halfak goes to add IRC handly to contact list.  [19:51:05] Thanks milimetric [19:51:07] but yeah, I think he's the one to ping about dev work halfak [19:51:26] but feel free to ask questions on here and ping any one of us, we're all friends :) [19:51:44] qchris: btw, do you guys have a Nexus instance for maven or somesuch? [19:51:48] Totally. I'm just trying to be respectful of your time/process. :) [19:51:52] * yuvipanda has http://tools.wmflabs.org/android-maven-repo setup [19:52:13] btw halfak: I just got done bragging about your analysis that went into fine-tuning the EEVS metrics to Erik M. He said he was going to look deeper into it [19:52:22] yuvipanda: nexus is dead. All hail arichva. [19:52:28] arichva [19:52:29] ? [19:52:36] I am just scping things to an http server ;) [19:52:48] http://archiva.wikimedia.org/ [19:52:51] :) archiva is like apt.wikimedia.org but for java stuff [19:53:09] DNS dead? [19:53:15] it's our production sanctioned "install JVM stuff" solution [19:53:31] yuvipanda: for nexus: yes. for archiva: no. [19:53:33] milimetric: yeah, I use maven heavily in the app too. [19:53:43] yeah, the search team does too [19:53:48] qchris: no, there seems to be unrelated DNS issues, plz2ignore :) [19:53:49] Woot milimetric. :) [19:54:06] i think spreading the word about archiva is one of the suggestions for the newly-proposed tech talks 2.0 [19:54:25] yuvipanda: ottomata even did some writeup ... let me find that [19:54:31] qchris: ah! [19:54:33] yeah [19:54:34] that'll be nice [19:54:49] yuvipanda: https://wikitech.wikimedia.org/wiki/Archiva [19:54:51] although hopefully there's an easy-to-use publisher for it so I can move things off tools.wmflabs.org to that [19:55:04] although it isn't that big a priority, since I am not deploying stuff to cluster [19:55:27] yuvipanda: But I hope I can get us to use a simpler maven setup. The current requirements are not really nice. [19:55:56] qchris: oh? just a simple file / http based one? [19:56:15] "mvn deploy"? [19:56:23] "mvn release"? [19:57:00] I mean ... not sure what the use case is. [19:57:36] https://wikitech.wikimedia.org/wiki/Archiva#Deploying_to_Archiva [19:58:24] qchris: hmm, for me it is just putting some 3rd party stuff that isn't possible on maven central (specifically the android libs) [19:58:35] well, not 'not possible' just that harder to do [19:58:40] I'll probably stick to tools for onw [19:58:53] WMF archiva already has jars that are not on central. [19:59:04] camus for example. [19:59:19] right [19:59:28] So you could use archiva for that. [20:00:10] * yuvipanda files bug [20:02:19] qchris: filed https://bugzilla.wikimedia.org/show_bug.cgi?id=63698 [20:02:46] yuvipanda: Looks good :-D [20:02:52] qchris: :) [20:47:17] (CR) QChris: [C: -1] Adding coding guidelines to README.md file (4 comments) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120542 (owner: Nuria) [21:01:03] trying to run scripts/tests and getting this error: ImportError: No module named mock. i tried running scripts/install, but not sure if mock was installed properly because it didn't fix the error. [21:01:16] anyone have an idea of how to fix this? [21:01:41] maybe [21:01:49] https://pypi.python.org/pypi/mock/1.0.1 [21:01:56] terrrydactyl: can you check if this is installed ? [21:02:13] maybe just pip install --user mock [21:03:32] Today wikimetrics saw a merge that added "mock==1.0.0" to requirements.txt [21:04:00] terrrydactyl: Are you on vagrant? [21:04:02] average: oops, i just realized that i installed scripts/test to my local environment, but not my vagrant one. [21:04:15] qchris: might be why. haha [21:04:36] terrrydactyl: :-D [21:04:39] looks like i don't get that error anymore. [21:04:45] \o/ [21:06:13] but i'm getting some test failures that seem to be unrelated to my changes [21:06:36] (at least i think they [21:06:45] 're unrelated. i git stashed my changes) [21:07:01] terrrydactyl: Let me fire up my vagrant instance, so I can reproduce (will take some minutes) [21:07:10] okay, thanks qchris :) [21:15:46] terrrydactyl: Same here ... seeing many 'E's [21:15:52] (on vanilla master) [21:16:13] IIRC there was some talking about upgrading some parts and upgrade scripts. [21:17:01] milimetric: You around? [21:17:13] nuria: ^ [21:17:57] hi qchris [21:18:13] oh I'm talking to terrrydactyl, I missed her ping earlier [21:18:23] Does the latest wikimetrics change require special upgrade? [21:18:29] Ah. Ok. [21:18:34] ok, so it seems people are having problems in general [21:18:41] let's talk in channel then [21:18:49] yep [21:19:03] latest wikimetrics just has some new dependencies [21:19:11] which should be installed via scripts/install [21:19:21] i ran scripts/instal and it fixed the mock problems [21:19:28] (I ran "alembic upgrade head" and "scripts/install") [21:19:32] ah, ok [21:19:56] http://paste.ofcode.org/AsNkuKZ2SCzHD5QxnGMS6q [21:19:59] terrrydactyl: did you run alembic upgrade head? [21:20:03] this is what my scripts/test looks like [21:20:07] no, i will run that now [21:20:30] ok, that will get the database into the right state [21:20:46] then, you'll have to rebase your change on master and fix any conflicts, but I can help with that [21:21:07] qchris: are you having problems as well? [21:21:27] Yes. [21:21:47] ERROR: test_create_reports_for_missed_days_0 (tests.test_models.test_run_report.RunReportClassMethodsTest) [21:22:04] IntegrityError: (IntegrityError) (1062, "Duplicate entry '428-2014-03-23 00:00:00' for key 'uix_report'") 'INSERT INTO report ... [21:22:06] well, so we don't have to work on this now, I can get up early tomorrow and help if you're going to bed qchris [21:22:30] milimetric: No need to help me fix this. [21:22:36] qchris: yes, that is a known issue. [21:22:45] a very few of the tests are non-deterministic [21:23:01] I was just trying to verify with terr rydactil that wikimetrics master is valid. [21:23:05] the reason is mentioned in the last commit message under the "Missing" section [21:23:21] thanks for helping with that [21:23:28] and sorry I was MIA [21:23:43] so was qchris' problem different from mine? [21:24:05] everyone has qchris' problem, it's a problem with integration testing [21:24:15] ah okay [21:24:28] I like the feeling the words "non-deterministic tests" cause in my head. ... It makes me dizzy a bit :-D [21:24:31] there's a bug filed for it, so for now we should ignore errors with the RunReportClassMethodsTest tests [21:24:46] hahaha qchris, yeah, it's not as crazy as it sounds [21:25:04] basically I try to stop the scheduler so that I can run some tests as if the scheduler isn't started [21:25:15] and it works most of the time [21:25:17] but fails sometimes [21:25:22] :-) [21:25:49] terrrydactyl: so how goes it with your setup? [21:26:20] well, alembic upgrade head didn't change anything.. was that supposed to be run in vagrant? [21:26:54] i got 2 fewer errors but 2 more failures, heh [21:27:03] after running the upgrade [21:27:12] alembic upgrade head should be run in whatever environment you're developing under [21:27:26] if you're developing in vagrant, you don't need to do anything outside of vagrant [21:27:49] vagrant is where all my databases are, so it should probably be running there. [21:28:00] but it didn't fix my issue. :( [21:28:46] so you're having the same errors [21:28:51] did you remember to stop the queue? [21:28:56] and check for ghost queues? [21:29:26] oh. what. i totally checked earlier, but i guess i started it up again somewhere. [21:29:28] ugh [21:29:58] that might be the problem [21:30:00] no worries - important thing is: [21:30:03] 1. i believe you [21:30:31] 2. the non-deterministic tests problem I was talking above is solved the same way as this silly ghost queue problem [21:30:39] do you know why sometimes pkill doesn't work and you have to individually delete the processes? [21:30:49] so when we address that newly filed bug (which should be soon), all this will be much simpler [21:30:53] yes [21:31:12] kill -9 is required when the processes aren't responding to normal killing [21:31:29] and one reason they can do that is if they're in some abnormal state [21:32:33] ah okay [21:32:58] milimetric: The you mentioned is [21:33:00] https://bugzilla.wikimedia.org/show_bug.cgi?id=63680 [21:33:01] ? [21:33:03] well, hopefully i won't have to worry about it later [21:33:14] yes qchris [21:33:18] milimetric: Thanks. [21:33:36] if we fix that bug we can basically ignore integration tests as part of our development flow [21:33:36] milimetric: okay, tests ran ok, thanks! [21:33:52] which solve ALL of the problems mentioned above [21:34:04] and is a good idea in general [21:34:18] :) I have a lot to learn about how to grow projects organically [21:34:32] we're all learning [21:34:38] I've never had so many people hop onto a project in the middle [21:34:54] people usually hop on after a distinct phase [21:34:59] anyway, good to hear terrrydactyl [21:35:06] soldier on! :) [21:36:30] btw, i kind of built the delete_wiki_user branch on top of the delete_cohort branch since i wanted to use some of the code as reference. will this cause problems? i can always stash my changes and make a new branch, but wonder if that's necessary. [21:39:05] (PS1) QChris: Revert "Add ability to create recurrent reports via UI" [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/124751 [21:39:56] (PS2) QChris: Revert "Add ability to create recurrent reports via UI" [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/124751 [21:41:45] terrrydactyl: not necessary to change your flow, I think the way you set it up seems sensible [21:42:05] okay cool, i will carry on then. [21:42:08] when you rebase, rebase your delete_cohort branch first, solve conflicts there, then rebase your delete_wiki_user branch second [21:42:43] qchris: are you saying you'd like to merge those reverts or are you just adding it for your own purposes? [21:43:17] qchris: to be clear, non-deterministic tests existed before this, the issue is not this commit [21:43:32] They did? [21:43:34] :-((( [21:43:46] (They never hit me up to today) [21:43:48] yes, integration tests are sort of that way by nature [21:43:53] ? [21:43:59] They shouldn't be :-D [21:44:05] integration between multiple asynchronous systems anyway [21:44:36] because by nature you have to start/stop different pieces of the system or time.sleep to let other parts catch up [21:45:07] Starting/Stopping pieces is part of the documentation ... I had the queue stopped. [21:45:17] oh no, I mean dynamically as part of the test [21:45:48] for example, if the scheduler mode is run by the test suite __init__ [21:45:56] Those things are not a problem. When testing the xmldumps, I created and tore down mysql cluster on the fly ... [21:45:57] so let's say I want to test days_missing [21:46:52] well, they're certainly a problem. maybe a solvable problem, but still a problem - clearly :) [21:47:26] so anyway, to test wikimetrics/models/report_nodes/run_report.py:RunReport.days_missing [21:47:32] you'd have to stop the scheduler [21:47:44] otherwise, since it runs every 1 second, after you create test data [21:47:49] it will alter the database [21:48:49] I am not sure I like the test setup. [21:48:54] So how to move forward? [21:48:59] Should I abandon the change? [21:49:24] I do not like that we have or add non-deterministic tests. [21:49:25] well, I definitely don't like the test setup, but that bugzilla bug, once fixed, should make things a lot better, no? [21:50:07] so I think we can move the integration tests to run maybe on the staging server, or to spin up a vagrant instance and run them there [21:50:14] But breaking something broken even more just to clean up afterwards is not a viable approach to me. [21:50:20] either way, we would remove them from the main development flow [21:50:57] I agree qchris, this is why I wanted desperately to talk about the scope of gerrit changes as part of our last retrospective [21:51:44] I said I didn't want to merge this change as is, and the team pushed back on me very hard [21:51:54] and said we would do it differently going forward [21:52:03] so ok, let's do it differently going forward [21:52:53] But I cannot recall the team to aggree on adding non-deterministic tests. [21:52:53] but that means that with this change I had two options: [21:52:53] delay for another one or two weeks while we split up and clean up the change [21:52:53] or merge [21:52:54] people were really against the delay option [21:53:54] Meh. I'll abandon the change. [21:54:05] Not sure if this is right. [21:54:18] I was under the impression the huge change would not break anything. [21:56:40] eh... huge change didn't technically break anything new, it just made an old problem more obvious [21:57:09] I'll send an email to j0kr and tnegrin to try and prioritize https://bugzilla.wikimedia.org/show_bug.cgi?id=63680 [21:57:47] Sounds good. [21:57:48] Thanks. [21:59:58] (Abandoned) QChris: Revert "Add ability to create recurrent reports via UI" [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/124751 (owner: QChris)