19:00:20 #startmeeting Ansible Molecule Working Group 19:00:20 Meeting started Wed Feb 6 19:00:20 2019 UTC. 19:00:20 This meeting is logged and archived in a public location. 19:00:20 The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:20 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:20 The meeting name has been set to 'ansible_molecule_working_group' 19:00:20 i am sorry that https://github.com/ansible/molecule/pull/1691 is breaking the ci by turning on skipped tests (because necessary libraries get installed) 19:00:47 WOO LETS GO 19:00:58 Who's around? 19:01:11 \o< 19:01:12 me, made it this time :) 19:02:49 #chair themroc fabianvf Pilou decentral1se 19:02:49 Current chairs: Pilou decentral1se fabianvf gundalow themroc 19:03:00 o/ 19:03:06 #info https://github.com/ansible/community/issues/427 19:03:38 fabianvf: Do you have PR you'd like reviewed, or something to discuss? 19:03:57 yep one sec 19:03:57 #topic Molecule CI 19:04:06 fabianvf: cool, will come to it after this topic 19:04:07 yeah, there's a lot on the agenda 19:04:14 but we should discuss CI again to try to close it off 19:04:17 +1 19:05:03 Please correct me if I get any of this wrong, is CI for PRs (ie not Cron) apart from testing `devel`https://github.com/ansible/molecule/issues/1727 19:05:03 so, AFAIK, it's just setting allowed failures for things affected by ansible-devel issue 19:05:06 and the PR from themroc? 19:06:41 So to address Compatibility with Ansible devel (2.8) broken #1727, do we want to do as Pilou suggested above and just disable it for the moment? 19:06:56 +1 19:07:31 It could be more useful to leave it enabled but not allow it to fail the build, in order to monitor the issue 19:08:32 * gundalow doesn't have a preference, anyone want to raise a PR for either solution? 19:09:01 we can still monitor, but this will just make it easier for us to reason about the state of the CI for other contributions 19:09:41 am sorry that https://github.com/ansible/molecule/pull/1691 is breaking the ci by turning on skipped tests (because necessary libraries get installed), better keep it unmerged for the moment 19:09:41 I think it's just commenting out https://github.com/ansible/molecule/blob/master/.travis.yml#L306-L367 19:10:29 there is the fail to deploy to pip issue cf https://travis-ci.com/ansible/molecule/jobs/175744500 19:10:39 well, we'd like it to still run, I suppose. I'll get a PR in for this and let's see 19:11:03 this is the doc I was looking at: https://docs.travis-ci.com/user/customizing-the-build#rows-that-are-allowed-to-fail 19:11:30 decentral1se: you going to take the `devel` issue? 19:11:31 gundalow: other possibility is desactivate the cron, as devel is only tested during cron ? 19:11:42 gundalow: yep 19:12:08 themroc: good question, looking at Travis 19:12:21 why devel is tested only with cron? 19:12:38 #chair zbr 19:12:38 Current chairs: Pilou decentral1se fabianvf gundalow themroc zbr 19:12:41 probably to have some indication of issues 19:12:47 it shouldn't fail builds though 19:12:53 Cron job: https://travis-ci.com/ansible/molecule/builds/99566825 looks like Ansible 2.5, 2.6, 2.7, devel 19:13:04 i would find it more useful to have non-voting stage, but always running. 19:13:37 `devel` can be broken (it's not releases) so it can be "noisy" to have broken pre-released Ansible Devel causing issues on unreleated Ansible PRs 19:13:49 because if you do not include it in a normal PR, there is a high risk that a change would break devel even more. 19:14:00 #action decentral1se to make `devel` none voting 19:14:43 Thanks for offering to do that decentral1se :) 19:15:01 np 19:15:17 What other failing/instabilities are we seeing with CI at the moment? 19:15:56 That's it, no? 19:16:05 (there are a bunch of skipped tests, but we'll get there ...) 19:16:16 https://travis-ci.com/ansible/molecule/jobs/175744500 19:16:16 > /home/travis/build/ansible/molecule/.tox/metadata-validation/lib/python3.7/site-packages/readme_renderer/markdown.py:38: UserWarning: Markdown renderers are not available. Install 'readme_render[md]' to enable Markdown rendering. 19:16:20 from themroc 19:17:03 "PyPI upload failed" 19:17:26 ouch 19:17:44 oh, is what I pasted the warning, appologies 19:17:54 hum, do we know why it failed, I don't see any logs 19:18:27 Created https://github.com/ansible/molecule/issues/1730 19:18:30 NOTE: Try --verbose to see response content. 19:18:30 HTTPError: 400 Client Error: File already exists. See https://test.pypi.org/help/#file-name-reuse for url: https://test.pypi.org/legacy/ 19:18:51 decentral1se: Thanks 19:19:22 it failed twice, i restarted it today already 19:19:58 So that's coming from https://github.com/ansible/molecule/blob/master/.travis.yml#L369-L393 19:20:59 hum, wonder if and rerun failed as previous uploaded 19:21:22 Need to see if next merg works 19:21:26 OK, what's next? 19:22:33 here 19:22:46 #chair dachary 19:22:46 Current chairs: Pilou dachary decentral1se fabianvf gundalow themroc zbr 19:22:49 dachary: Welcome :) 19:22:55 for the ci: i tried to relaunch some builds for pr that failed previously, but maybe they need to be rebased first to get green ? 19:23:12 themroc: I *think* travis rebases before run 19:23:56 Anything else for CI? 19:24:21 On the plus side https://github.com/ansible/molecule/commits/master shows one green commit. 19:24:23 then all latest PR are broken https://travis-ci.com/ansible/molecule/pull_requests 19:24:47 510--515 19:25:48 these are the PR in the need review column in https://github.com/ansible/molecule/projects/4 19:26:18 themroc: Thanks 19:26:23 #info PRs needing review https://github.com/ansible/molecule/projects/4 19:26:45 and https://github.com/ansible/molecule/projects/2 19:27:40 how would we request a PR get added to the milestone? 19:27:46 fabianvf: ask here :) 19:27:59 myself themroc and decentral1se have powers to add 19:28:12 https://github.com/ansible/molecule/pull/1653 19:28:19 I'd like to align https://github.com/ansible/molecule/pull/1714 to 2.21 unless there's an objection (it would go under in progress right now) 19:28:34 https://github.com/ansible/molecule/pull/1653 needing review (already in the milestone) 19:29:34 fabianvf, you're served 19:29:56 * singuliere rebasing https://github.com/ansible/molecule/pull/1653 & resolving conflict 19:30:03 awesome, thanks! 19:30:32 https://github.com/ansible/molecule/pull/1728 is an easy merge 19:30:43 oh, done :) 19:30:44 decentral1se: merged (and related PR closed) 19:31:01 hum, that should kick of a test.PyPi I think, so we can see if it works now 19:31:03 #topic PR review 19:31:39 rebased & re-force-pushed 19:32:19 nice one 19:32:22 https://github.com/ansible/molecule/pull/1526 looked good to merge 19:32:46 also https://github.com/ansible/molecule/pull/1535 19:34:10 yes basically after these 2 i believe it's time for some "make all arguments available for docker module available in molecule" 19:34:14 1526 is failing CI due to syntax error, review added 19:34:58 good catch 19:35:11 Problem with failing CI, need to check why 19:35:27 I miss ansibulbot copying the failing text into a GitHub comment :( 19:35:52 oh that would be awesome! 19:35:57 Is there much more we ask from https://github.com/ansible/molecule/pull/1604? 19:37:43 In Travis-CI is there a way to rerun only failing tests? 19:37:54 Don't think so :/ 19:37:55 yes 19:38:02 ah, click rerun inside the job 19:38:07 \0/ 19:38:10 yes 19:38:51 1535: Rerunning CI 19:39:03 So if CI should be green now we need to ensure it is before hitting merge 19:40:01 nice one 19:40:30 watching https://travis-ci.com/ansible/molecule/jobs/175827471 (pypi release on latest master build ...) 19:41:19 decentral1se: think you'll have to wait 45mins for the tests to finish before that job starts 19:42:14 oh dear 19:44:45 fabianvf: Would you like to go though yours? 19:44:50 what's the PR link? 19:44:58 https://github.com/ansible/molecule/pull/1714 19:45:15 #topic [WIP] Add Ansible verifier #1714 19:45:19 fabianvf: floor is yours 19:45:32 #info https://github.com/ansible/molecule/pull/1714 [WIP] Add Ansible verifier 19:46:03 so the PR in it's current state is pretty much a POC, but it seems pretty easy to add, since it's basically just a passthrough to the verify.yml which is already used by the other verifiers 19:47:00 I've added the bits I have left to the TODO list in the PR, if anyone has a cycle or two any assistance (or even comments on the PR for the proper places to look) would be much appreciated 19:47:43 I'm hoping to steal some time in the next week or so to bring it closer to a finished implementation 19:48:25 you'll need an option when you create a template 19:48:45 when you create a role or a scenario sorry 19:48:59 added 19:50:07 Anyone else able to take a look atthis? 19:50:54 Happy to review as it progresses fabianvf! Not much cycles to spare otherwise 19:51:25 I cannot promise anything ATM, I wish I could, it could be quite useful for some of our usecases. 19:53:25 no promises necessary, only if it's convenient. I can definitely wrap this up on my own 19:53:54 Thanks all 19:53:58 fabianvf: anything else on that? 19:54:08 gundalow: I think that's it for me 19:55:12 a point on release 2.20 ? 19:57:42 could we release 2.20 without https://github.com/ansible/molecule/issues/1616 and https://github.com/ansible/molecule/issues/1609 ? should someone try before to run all the tests that are skipped in travis from a workstation (including all cloud related tests)? 19:58:26 Blockers were: #1723 (fix waiting) and #1725 (is it really?) 19:58:37 #topic release 2.20 19:59:07 We can skip waiting longer on #1616, no? It's only meta information that is nice to have? 19:59:21 I tried docker build locally and it failed 19:59:29 oh, upstream pip bug 19:59:36 https://github.com/ansible/molecule/projects/2 only 2 items in the todo 19:59:41 so hopefully that will be fixed by the time we are ready 20:00:13 * gundalow is happy to skip 1616 20:00:27 +1 20:00:30 Cool 20:01:18 -> 2.21 20:01:45 So just 1723 and 1725 and we're ready to rip?! 20:01:48 so should https://github.com/ansible/ansible-lint/pull/478 be v2.20 as well as the bug 1723 20:02:46 +1 20:04:25 erm,taht's a lint PR 20:04:37 https://github.com/ansible/molecule/issues/1725 - probably the Dockerfile needs to have the extras referenced in pip package, but the package need to be uploaded first 20:05:00 awcrosby: Not sure if you are still around, looks like https://github.com/ansible/ansible-lint/pull/478 is important to us in Molecule land 20:05:43 gundalow should be good to merge for 4.1.0, to be release in the next few days 20:05:58 Thanks, added 4.1.0 milestone 20:06:04 solid! 20:07:55 themroc: ah, I see that now 20:09:49 building locally now ... 20:10:30 cool, that's the hour (and a bit) 20:10:39 Anything else before I #endmeeting? 20:11:07 :) right, all clear from my side 20:11:14 a little celebration for the CI green just during the community update talk at cfgmgmtcamp ? 20:11:14 awesome work on this project from everyone 20:11:32 woot woot 20:11:33 Aye, really impressed, good work all :) 20:11:46 #endmeeting