Wednesday, 2016-11-23

*** syed__ has quit IRC01:56
*** syed__ has joined #craton02:17
*** Mudpuppy_ has quit IRC03:13
*** valw has joined #craton03:29
*** VW has joined #craton03:41
*** valw has quit IRC03:49
*** Mudpuppy has joined #craton03:56
*** valw has joined #craton04:26
*** VW has quit IRC04:35
*** mhayden has quit IRC04:38
*** valw has quit IRC04:49
*** mhayden has joined #craton04:50
*** VW has joined #craton05:14
*** VW has quit IRC05:18
*** valw has joined #craton05:20
*** valw has quit IRC05:25
*** tojuvone has quit IRC06:34
*** valw has joined #craton06:38
*** valw has quit IRC06:42
*** Mudpuppy has quit IRC06:56
*** Mudpuppy has joined #craton07:27
*** Mudpuppy has quit IRC07:32
*** syed__ has quit IRC08:06
*** valw has joined #craton08:39
*** valw has quit IRC08:43
*** tojuvone has joined #craton10:30
*** Mudpuppy has joined #craton12:26
*** Mudpuppy has quit IRC12:28
*** valw has joined #craton12:41
*** valw has quit IRC12:46
*** valw has joined #craton13:30
*** VW has joined #craton13:36
*** VW has quit IRC13:40
*** valw has quit IRC13:49
*** VW has joined #craton14:27
sigmavirussulo: https://gist.github.com/sigmavirus24/33bcf97f378690f93b274b1481e32732 is what I get when I try out your functional test suite patch14:39
*** valw has joined #craton14:48
*** valw has quit IRC14:54
sulosigmavirus: :(14:59
sigmavirussulo: it's very weird, but I'm also running into the problems jimbaker mentioned yesterday14:59
sulohmm thats interesting though ..14:59
sigmavirusAnd my ubuntu images was created 5/6 days ago14:59
sigmavirusI'm running this all on a cloud server14:59
* sigmavirus tries running docker build today14:59
sulobut that error sounds like it failed to get the image built ?15:00
sigmavirusStill failing with http://archive.ubuntu.com/ubuntu/pool/main/m/mysql-5.7/mysql-common_5.7.15-0ubuntu0.16.04.1_all.deb15:00
suloi dont know why i dont get this problem15:00
sigmavirusOr rather, it can't fetch mysql-common and libmysqlclient stuff15:00
sigmavirusMight be using a different mirror15:00
sigmavirusI'm hitting IP: 91.189.88.162 8015:00
sulo91.189.88.14915:01
sulowell that package doest exist15:02
*** valw has joined #craton15:03
sigmavirushuh15:03
sigmavirusIdk what's specifying that version (if anything)15:03
sulosigmavirus:  your image id for ubuntu e4415b714b62 ?15:05
sigmavirusYep!15:05
sigmavirus"Created 6 days ago"15:05
suloyes15:05
sigmavirusme is going to clear teh image cache15:05
sigmavirus^ should have been /me15:07
sigmavirusSO MANY FREE GIGS NOW15:07
sigmavirus:P15:07
* sigmavirus only hates docker a little15:07
sigmaviruswow15:15
sigmavirusthere were a lot of dangling images :/15:15
sigmavirusSTALE IMAGE CACHE15:15
* sigmavirus shakes fist15:15
sigmavirusjimbaker: you might need to do `docker rmi -f $(docker images -qf dangling=true)` to get past the build errors15:15
sulosigmavirus: Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 mysql-common all 5.7.16-0ubuntu0.16.04.1 [15.0 kB]15:16
sulois what my image is doing15:16
sigmavirussulo: yeah, I've no trouble building the image now15:17
sigmavirusI had to clear out the old cached bits15:17
sulocool15:18
sulosigmavirus: does that help the test maybe ?15:18
sigmavirusI think this is why docker's docs recommend deleting the apt cache in /var/lists/apt after an apt-get update && apt-get install15:18
sigmavirussulo: I would expect it will15:18
sigmaviruswaiting for the build to finish15:18
sulook15:18
sigmavirusfigure building right before might make the tests a bit faster?15:18
suloyeah15:19
suloit does15:19
sigmavirusalso building ensures it won't error :D15:19
sigmavirus(or lessens the likelihood probably)15:19
* sigmavirus thinks it's building the image again lol15:20
suloit build the craton image15:20
sigmaviruswoo15:21
sigmaviruslooks to have been successful15:21
sigmavirusYep!15:21
suloit should be quicker though (not having to download the base)15:21
suloalso https://review.openstack.org/#/c/401312/15:22
*** Mudpuppy has joined #craton15:29
*** syed__ has joined #craton15:54
*** valw has quit IRC15:56
*** valw has joined #craton15:57
jimbakersigmavirus, thanks for the guidance. i have only 3 dangling images around. good thing? ;) ~3GB to be freed...16:17
sigmavirusI had ... a lot16:18
jimbakeri did successively run docker rmi with docker images yesterday to get past ref count issues (or so i assume)16:18
jimbakeractually i had no idea what i was doing, just felt good running it multiple times. kill! kill! :)16:19
jimbakerbut now a cleaner system16:19
sulodocker rm $(docker ps -a -q); docker rmi $(docker images | grep "^<none>" | awk "{print $3}")16:20
jimbakersulo, so https://hub.docker.com/_/ubuntu/ - does this mean we should use FROM ubuntu:latest in Dockerfile ?16:21
jimbakersulo, generally commands like that are just golf versions of removing everything one ever cared about on a laptop ;)16:21
sulojimbaker: haha16:23
jimbakeri was not aware of docker ps -a - so that explains those zombies holding onto images16:25
jimbakerbut hey, -f16:26
jimbakersulo, back to my other question re ubuntu:latest16:26
jimbakeri assume this is the right tag for us16:26
sulojimbaker: re: update, i personally like images update without letting me know ..16:27
sulo*i dont like*16:27
suloif we want to just have latest .. we should just pull latest on the image rather than using lastest image16:28
sulolatest image will change without letting us know16:28
jimbakersulo, maybe then just a quick doc update then on the build steps16:28
jimbakerin Dockerfile16:28
jimbakerand corresponding docs16:28
suloyeah +116:29
sulolet me file an issue and fix that too16:30
jimbakersulo, sounds good16:31
sulohttps://review.openstack.org/#/c/401343/16:38
sulojimbaker: also did tests work for you with these changes ?16:39
suloit worked for sigmavirus after the images cleanup16:40
jimbakersulo, i was re-running, and just realized i forgot to pull latest. let my try again...16:40
sulojimbaker: also curious if you saw any errors yesterday, when it was hanging16:41
suloit can hang only if we didnt catch the excption .. i didnt think there was a place where that could happen16:41
sulobut maybe i am wrong16:41
jimbakeryeah, this hang is almost certainly because of the use of threading16:42
jimbakerand nontermination thereof16:43
jimbakersulo, so here's what i saw yesterday - https://gist.github.com/jimbaker/9fe0907a402df96ddd8b5ad21cf853c216:44
jimbakeri'm going to rerun now16:44
jimbakeralso sounds good about removing py34 support. wanted to see that happen :)16:44
jimbakerasap16:45
jimbakeri assume 3.6 is still on its release schedule for later this year16:45
sigmavirusjimbaker: yes, but we'll probably support 3.5 and 3.6 so long as xenial is the base image for the infra gate16:53
sigmavirusalso one snag with moving to py.test is the fact that it's not already in global-requirements16:54
jimbaker3.5 and 3.6 is good; just wanted to drop 3.416:57
sigmavirus3.4 is so great though!16:57
sigmavirus:P16:57
jimbakerstrictly speaking, i don't believe 3.4 gets in the way of type hints. but using type hints + mypy is the next thing i would like to see us trying16:57
jimbakerright there with coverage16:58
jimbakerhaving said that: 3.6 seems like an awesome codebase from my modest following to-date. i should spend a little time today going through the what's new16:59
jimbakerwordcode... ordered dicts by default...16:59
sulojimbaker: ok i see what needs to fix for your error yesterday .. i want properly catching it17:00
sulowasnt17:00
sigmavirusoh yeah that's not what I was running into17:04
jimbakersulo, functional testing still stalling on my laptop, even with the latest change about 20 min ago17:20
jimbakersulo, assuming you meant patch set 4 was supposed to fix17:21
sigmavirusjimbaker: sulo  (regarding our functional tests) http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html is relevant to our interest17:29
sigmavirus*interests17:29
jimbakersigmavirus, very nice18:09
jimbakerso we should add tools/test-setup.sh for this purpose to https://review.openstack.org/#/c/397872/18:10
jimbakersigmavirus, does this impact the discussion in https://review.openstack.org/#/c/397872/4/craton/tests/functional/test_cell_calls.py ?18:11
jimbakeractually it sounds like this proposed support is still WIP. so a separate branch then18:13
jimbakercommented accordingly18:21
jimbakerre 3.6 - nice to see pep 526 was adopted18:25
*** valw has quit IRC18:29
*** jovon has joined #craton19:08
*** valw has joined #craton19:10
*** Mudpuppy_ has joined #craton19:15
*** Mudpuppy has quit IRC19:19
*** Mudpuppy_ has quit IRC19:19
*** VW_ has joined #craton19:36
*** VW_ has quit IRC19:39
*** VW_ has joined #craton19:39
sigmavirusjimbaker: which one is 526 again?19:39
*** VW has quit IRC19:39
*** VW_ has quit IRC19:43
*** VW has joined #craton20:09
syed__guys, a general question, for https://bugs.launchpad.net/craton/+bug/1644270 writing tests for endpoints in routes.py20:12
openstackLaunchpad bug 1644270 in craton "Add test to validate routes/schema" [Medium,Triaged]20:12
syed__should the tests be for api endpoints20:12
*** VW has quit IRC20:13
*** VW has joined #craton20:43
sigmavirussyed__: what?20:43
syed__I am not sure to what we means for endpoint tests ? sigmavirus20:45
syed__https://github.com/openstack/craton/blob/master/craton/api/v1/routes.py#L16, should it be checking urls20:45
sigmavirusI think it actually wants you to verify that for every route in that list there's an entry in https://github.com/openstack/craton/blob/master/craton/api/v1/schemas.py#L1055 that has a valid schema associated with it20:49
sigmavirusIt might be a bit ... icky though20:49
-openstackstatus- NOTICE: Due to a problem with the cinder volume backing the log server, jobs are failing with POST_FAILURE. Please avoid issuing 'recheck' commands until the issue is resolved.21:05
jimbakersigmavirus, pep 526 is new syntax for being able to declare the type of variables, and without requiring the variable to be initializaed. mypy only supported this in comments prior to 3.621:10
jimbakerso it complements being able to do such declarations in the function signature21:11
jimbakeroften one can infer the types without declarations, but not always21:12
jimbakerwithout *such* declarations21:12
jimbakeresp from the function signature21:12
*** Mudpuppy has joined #craton21:19
*** jovon has quit IRC21:28
*** VW has quit IRC21:35
*** valw has quit IRC22:08
*** jovon has joined #craton22:16
*** VW has joined #craton22:18
-openstackstatus- NOTICE: The affected filesystems on the log server are repaired. Please leave 'recheck' comments on any changes which failed with POST_FAILURE.22:50
*** VW has quit IRC23:29

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!