[00:04:07] *** Quits: ziyeyang (~ziyeyang@134.134.139.83) (Quit: Leaving) [00:22:14] *** Quits: Shuhei (caf6fc61@gateway/web/freenode/ip.202.246.252.97) (Ping timeout: 260 seconds) [00:36:12] *** Joins: ziyeyang (~ziyeyang@134.134.139.72) [00:36:12] *** ChanServ sets mode: +o ziyeyang [00:37:22] *** Quits: Param (~Param@106.206.72.72) (Quit: Param) [00:56:19] NVMf hotplug tests fail in many times, e.g., http://spdk.intel.com/public/spdk/builds/review/345dbd955418d87c9012ab790175ed9063337c9c.1520315938/ [01:00:38] *** Quits: ziyeyang (~ziyeyang@134.134.139.72) (Quit: Leaving) [01:57:27] *** Joins: pzedlews (86bfdc49@gateway/web/freenode/ip.134.191.220.73) [02:01:48] *** Joins: tkulasek (~tkulasek@134.134.139.83) [02:06:20] *** Joins: tomzawadzki (tomzawadzk@nat/intel/x-whvqoshpsghmqvbb) [03:19:27] *** Quits: tomzawadzki (tomzawadzk@nat/intel/x-whvqoshpsghmqvbb) (Quit: Leaving) [04:49:06] *** Joins: ziyeyang (~ziyeyang@134.134.139.83) [04:49:06] *** ChanServ sets mode: +o ziyeyang [04:50:59] I am not sure that NVMe-oF failure raised by Paul or seem in other's patch is caused by not rebasing the master or it is an issue of NVMe-oF hotplug now. But will continue watching this issue [04:51:08] *** Quits: ziyeyang (~ziyeyang@134.134.139.83) (Client Quit) [04:54:16] *** Joins: tomzawadzki (~tomzawadz@134.134.139.73) [05:04:10] *** Joins: pzedlews_ (~pzedlews@134.134.139.76) [05:04:27] *** Quits: pzedlews_ (~pzedlews@134.134.139.76) (Client Quit) [05:05:25] *** Parts: pzedlews (86bfdc49@gateway/web/freenode/ip.134.191.220.73) () [05:06:00] *** Joins: pzedlews_ (~pzedlews@192.55.54.44) [05:06:08] *** Quits: pzedlews_ (~pzedlews@192.55.54.44) (Client Quit) [05:06:33] *** Joins: pzedlews (~pzedlews@192.55.54.44) [07:05:17] *** Quits: tkulasek (~tkulasek@134.134.139.83) (Remote host closed the connection) [07:05:32] *** Joins: param (6ace4848@gateway/web/cgi-irc/kiwiirc.com/ip.106.206.72.72) [07:05:35] *** Joins: tkulasek (~tkulasek@134.134.139.83) [07:12:01] *** Joins: param_ (uid285755@gateway/web/irccloud.com/x-lvvbwgatemsuwgit) [07:13:03] what is the meeting id or link? we have it in around 45 mins? [07:13:56] *** Quits: param (6ace4848@gateway/web/cgi-irc/kiwiirc.com/ip.106.206.72.72) (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) [07:13:56] *** param_ is now known as param [07:19:13] *** Quits: sbasierx (~sbasierx@192.198.151.36) (Quit: Going offline, see ya! (www.adiirc.com)) [07:19:19] *** Quits: peluse__ (48d0c853@gateway/web/freenode/ip.72.208.200.83) (Ping timeout: 260 seconds) [07:34:46] param: the meeting phone numbers, meeting id and webex links are provided on: http://www.spdk.io/community/ [07:36:18] *** lhodev1 is now known as lhlodev [07:36:35] *** lhlodev is now known as lhodev [08:55:53] *** Joins: jimharris_ (jimharris_@nat/intel/x-encmzfqzgwfcoupt) [08:58:10] *** Quits: jimharris_ (jimharris_@nat/intel/x-encmzfqzgwfcoupt) (Remote host closed the connection) [08:58:31] i am not able to setup the development environment in vagrant... looks like the url is not valid.. anyone tried it recently? [09:01:17] *** Joins: jimharris_ (jimharris_@nat/intel/x-otvlvlcavnwedksv) [09:04:09] param: I ran through it last week on my home desktop with no issues. On what base system are you building the environment? [09:04:37] i tried in macbook.. [09:06:01] I was using windows 10. I am not sure if the base image is different from OS to OS. Let me look in the script real quick. [09:06:09] sethhowe : Did you install ubuntu or centos.. i guess these are the options available in Vagrantfile... [09:06:34] I installed ubuntu [09:06:40] i was not able to reach the url as well to download the image.. [09:07:39] Are you behind a corporate firewall by chance? [09:08:04] no.. there is no firewall ... [09:08:49] its a link to hashicorp right? [09:09:40] *** Joins: bwalker (~bwalker@134.134.139.82) [09:09:40] *** Server sets mode: +cnt [09:10:19] I'm not 100% sure there. Puppetlabs is the base url. [09:10:28] *** Joins: darsto (~dstojacx@134.134.139.82) [09:10:51] *** darsto is now known as Guest13780 [09:11:00] yeah.. puppetlabs.. [09:11:17] then let me try in my windows box [09:11:56] param: what is the output of "vagrant box add puppetlabs/ubuntu-16.04-64.nocm" when you run it in your mac? [09:11:58] *** Joins: klateck (~klateck@134.134.139.82) [09:13:55] *** Joins: pbshah1 (~pbshah1@134.134.139.82) [09:14:42] actually my macbook got screwed up today.. i dont have my vagrant setup in the currently running windows box.. i dont have SPDK source code as well now.. will we be able to reach the url from browser and download? [09:15:30] *** Joins: ppelplin (~ppelplin@134.134.139.82) [09:15:53] *** Joins: pwodkowx (~pwodkowx@134.134.139.82) [09:16:31] *** Joins: pzedlews_ (~pzedlews@134.134.139.82) [09:17:27] *** Joins: tsg (~tsg@134.134.139.82) [09:19:03] *** Joins: changpe1 (~changpe1@134.134.139.82) [09:19:26] The full URL is https://vagrantcloud.com/puppetlabs/ubuntu-16.04-nocm. The page opens in the browser, but there doesn't appear to be a direct download link from there. [09:20:29] *** Joins: gangcao (~gangcao@134.134.139.82) [09:21:25] okay.. I will try in my windows box.. i should just download the vagrant and do a vagrant up right? [09:21:31] *** Joins: jimharris (~jimharris@134.134.139.82) [09:21:31] *** ChanServ sets mode: +o jimharris [09:22:38] Yes. I am assuming that you have VirtualBox and the extension pack already installed on your machine? [09:22:59] what is the extension pack to be downloaded? [09:23:01] *** Joins: lgalkax (~lgalkax@134.134.139.82) [09:23:50] *** Parts: jimharris_ (jimharris_@nat/intel/x-otvlvlcavnwedksv) ("Leaving...") [09:24:08] from the downloads page: https://www.virtualbox.org/wiki/Downloads there is a line VirtualBox 5.2.8 Oracle VM VirtualBox Extension Pack. Click the link next to that. [09:24:33] That gives support for the NVMe card we emulate. [09:24:50] yeah.. sure.. ill do that let you know.. [09:25:03] *** Joins: pniedzwx (~pniedzwx@134.134.139.82) [09:25:07] thanks for the support.. [09:25:33] *** Joins: qdai2 (~qdai2@134.134.139.82) [09:26:03] *** Joins: vermavis (~vermavis@134.134.139.82) [09:26:04] absolutely, I hope that I have been helpful. [09:26:34] *** Joins: ziyeyang (~ziyeyang@134.134.139.82) [09:41:14] *** Quits: tomzawadzki (~tomzawadz@134.134.139.73) (Ping timeout: 260 seconds) [09:41:27] *** Quits: pzedlews (~pzedlews@192.55.54.44) (Ping timeout: 245 seconds) [09:41:27] *** pzedlews_ is now known as pzedlews [09:59:29] *** Quits: tkulasek (~tkulasek@134.134.139.83) (Ping timeout: 256 seconds) [10:14:12] Build Pool Update, I am pausing the build pool to remove CentOS 6 from the build pool. Please see the mailing list for more details. [10:53:22] jim : can i start working on the card that you had suggested.. if yes can you guide me where to start on that.. or can i start working on another card if that one is complicated.. [12:04:29] hi param - have been thinking about this one some more and drv was right - it's going to be a lot more complicated than i originally thought - i'm in meetings most of today but will try to provide some more guidance later this week [12:11:04] *** Joins: cunyinch (~cunyinch@134.134.139.82) [12:49:14] jimharris: Hey, Jim, the revised patch for the spdk_app_start()/stop() about which we discussed earlier has been pushed and successfully built, https://review.gerrithub.io/#/c/401243/. As a named reviewer, do you automatically receive notifications of newly uploaded patches? [13:03:56] I do not - I think my e-mail would blow up if I enabled e-mail notifications :) I have a custom dashboard that I use - your patch now shows up at the top of my "Needs Review" list [13:04:12] i'm in all day meetings today so not sure i'll get a chance to look at it today - but hopefully tomorrow [13:04:26] jimharris: fair enough! By the way, I'm gonna re-push because I need to correct the commit message. [13:12:51] *** Joins: pzedlews_ (uid285827@gateway/web/irccloud.com/x-hugstytgdbuwcsiu) [13:24:38] My patch (#5) for https://review.gerrithub.io/#/c/401243/ built/tested fine, but upon realizing I needed to update the commit message, I fixed it and pushed (#6), and the subsequent build failed: https://ci.spdk.io/spdk/builds/review/5533f1119acff45e6ea0b4d466b6a02b88e0a5c5.1520366754 . Again, the only change was the git commit message. [13:31:09] Looks like: test/nvmf/nvmf.sh -> app/nvmf_tgt/mvmf_tgt which died with a SIGABRT on perhaps a free() invoked from _spdk_io_device_attempt_free(). Anyone see this kind of failure before? [13:36:29] this failure has popped up a couple of times - not sure if anyone is looking at it specifically yet though, for now I just removed the -1 to run it through the pool again [13:54:00] jimharris: Thx, Jim. The run through the pool again resulted in another failure, but this time on app/iscsi_tgt/iscsi_tgt which I believe has also been reported as failing intermittently. [13:54:20] ugh [13:56:12] The iscsi_tgt also perished with a SIGABRT, but an entirely different backtrace when it went belly up than the nvmf_tgt one. [14:00:05] I'm not familiar with the code, but upon inspecting _spdk_io_device_attempt_free() (for the nvmf_tgt failure), I see that the code takes a lock and runs through lists looking to see if anything else references the dev. It drops the lock, but potentially calling a unregister_cb and then free(). My knee-jerk question would be: could this be a race? In other words, at that juncture, is it safe to drop the lock where it does? [14:14:14] this does look a bit fishy - definitely need to look at this further but i'm almost positive this is not related to a race in the io_channel and instead is a bug in the nvme-of hotplug handling [14:54:52] jimharris: I guess 3 times a charm, lol. Looks like I managed to avoid hitting the nvmf_tgt and iscsi_tgt issues so it passed. [15:27:42] jimharris: I posted a response to your comment on https://review.gerrithub.io/#/c/402381/ [15:48:33] *** Joins: Shuhei (caf6fc61@gateway/web/freenode/ip.202.246.252.97) [15:49:26] param: were you able to try the vagrant setup on your windows machine? If so, how did it go? [15:59:13] *** Joins: kjakimia (~kjakimia@134.134.139.82) [16:31:24] *** Joins: jimharris_ (~jimharris@134.134.139.73) [16:59:27] *** Quits: jimharris_ (~jimharris@134.134.139.73) (Quit: Leaving...) [17:31:58] *** Joins: ziyeyang_ (~ziyeyang@192.55.54.42) [17:32:18] *** Quits: ziyeyang_ (~ziyeyang@192.55.54.42) (Client Quit) [17:32:31] *** Joins: ziyeyang_ (~ziyeyang@192.55.54.42) [17:32:48] *** Quits: ziyeyang_ (~ziyeyang@192.55.54.42) (Client Quit) [20:35:53] jim : sure .. thanks.. [20:36:34] sethhowe : not yet.. will do it today and let you know.. [21:57:00] *** Joins: ziyeyang_ (~ziyeyang@192.55.54.40) [22:11:53] *** Quits: ziyeyang_ (~ziyeyang@192.55.54.40) (Quit: Leaving) [23:29:59] *** Quits: drv (daniel@oak.drv.nu) (Ping timeout: 276 seconds) [23:30:09] *** Joins: drv (daniel@oak.drv.nu) [23:30:09] *** ChanServ sets mode: +o drv