08:01:01 <anteaya> #startmeeting third-party
08:01:02 <openstack> Meeting started Tue Jan 20 08:01:01 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:01:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:01:05 <openstack> The meeting name has been set to 'third_party'
08:01:09 <anteaya> hello
08:01:19 <anteaya> anyone here for the third-party meeting?
08:04:22 <jyuso1> anteaya: hi:)
08:05:44 <anteaya> hello jyuso1
08:06:00 <anteaya> how did you do creating a new CI account with launchpad?
08:08:17 <jyuso1> anteaya: not yet.we thought PCI CI just on-line for a week.so new account may be stuck CI for some time and I've not decided to create new account:)
08:09:02 <anteaya> okay that is fine
08:09:21 <anteaya> but now you know the process in case you do want to change the email on your account
08:09:49 <anteaya> how is everything else with your system?
08:10:39 <jyuso1> anteaya: yes.few issues.Lots of issues caused by network:(
08:10:55 <jyuso1> anteaya: like git fail,curl fail:(
08:11:08 <anteaya> :(
08:11:19 <anteaya> the network
08:11:29 <anteaya> is this due to the firewall you are behind?
08:11:39 <anteaya> or firewalls?
08:12:39 <jyuso1> anteaya: No.The bandwiths of our IP is not isolated.so sharing always make some problem.
08:12:50 <anteaya> oh
08:13:00 <anteaya> :(
08:13:03 <jyuso1> anteaya: we are still try to get help from other department
08:13:26 <anteaya> do you need to escalate the issue?
08:13:37 <anteaya> does adrian know you are having this problem?
08:15:25 <jyuso1> anteaya: yes.I think so.I think it will be solved soon.everyone is take care of us:)
08:15:34 <anteaya> oh okay good
08:16:02 <jyuso1> anteaya: BTW,I still have a question to ask
08:16:07 <anteaya> I'm not much help on internal issues, but don't continue to be stuck if you keep having this problem
08:16:11 <anteaya> jyuso1: go ahead
08:18:59 <jyuso1> anteaya: we use Gerrit trigger as project trigger.I notice that when a patchset 1 is coming to my trigger queue,then same patch be modified again,comes patchset 2.My CI would test twice.
08:19:40 <anteaya> hmmmm
08:20:13 <jyuso1> anteaya: the other CI would just add patchset 2 and abandon patchset 1.Is there some settings of queue I've missed?
08:20:24 <anteaya> in our system if a new patchset is submitted, the new patchset is tested and the old patchset is no longer tested
08:20:41 <anteaya> that might be something in zuul that removes the first patchset though
08:20:55 <anteaya> I think it is probably a setting in zuul
08:21:11 <anteaya> jhesketh SergeyLukjanov do you happen to know the answer to jyuso1's question?
08:22:54 <anteaya> jyuso1: I think it is a setting in zuul, so your set up wouldnt' have that feature
08:23:07 <jyuso1> anteaya: OK..thanks.
08:23:23 <anteaya> I am not sure how to create that feature with Jenkins and a Gerrit trigger
08:23:24 <jyuso1> anteaya: yes,I don't find such option in Gerrit trigger
08:23:49 <anteaya> can you manually stop a job if it is running and a new patchset comes in?
08:24:51 <nibalizer> anteaya: im not sure thats an issue since the new patchset iwll fire a new job anyways right?
08:25:13 <anteaya> nibalizer: the new patchset should fire its own job
08:25:32 <anteaya> nibalizer: it can become an issue for systems where testing resources are scarce
08:25:38 <nibalizer> ya
08:26:12 <anteaya> the concern about scarcity of testing resources is a common concern from third party operators
08:26:31 <jyuso1> anteaya: I don't get it.I think I can manually stop a running job,is there any difference?
08:27:17 <anteaya> well if you can manually stop a running job, perhaps you can script something to recongize that two jobs are running and stop an earlier running job
08:28:00 <anteaya> this is one of the benefits of using open source software, you can (if you wish) modify your tools
08:28:44 <anteaya> I have not heard this concern come up before from folks running jenkins with the gerrit trigger plugin
08:29:01 <anteaya> so I don't know if anyone else has modified the tools to address this issue
08:30:38 <jyuso1> anteaya: like this URL:https://review.openstack.org/#/c/145761/
08:31:10 <jyuso1> anteaya: you can find our Intel PCI CI fail at patset 6 and 7
08:32:14 <jyuso1> anteaya: But before our result of patchset 6 return,the owner have submitted Patch Set 7.
08:32:19 <anteaya> 6 and 7 were uploaded 2 minutes apart from each other
08:33:06 <anteaya> the message from Intel PCI CI for both patchset 6 and 7 is build successful
08:35:14 <jyuso1> anteaya: Yes.the interval time is short.But I think other CI system don't have a testing result for patchset 6.so I think may be they abandon patchest 6,when monitor patchset 7 coming....
08:35:32 <anteaya> where are the failures you are talking about? "anteaya: you can find our Intel PCI CI fail at patset 6 and 7"
08:36:46 <anteaya> correct the other systems don't report back any findings on patchset 6
08:36:53 <anteaya> is that what you mean by failure?
08:36:59 <jyuso1> anteaya: yes
08:37:08 <jyuso1> tanteaya: that's it.
08:37:13 <anteaya> since I see your test runs on both patchset 6 and 7 as building successfully
08:37:22 <anteaya> okay well that is not a failure then
08:38:30 <anteaya> that is just an issue with your system, not a failure in the execution of the tests
08:39:03 <anteaya> I don't know exactly which accounts use zuul and which don't
08:39:14 <anteaya> my guess would be that the other accounts use zuul
08:40:20 <jyuso1> anteaya: OK,may be I could asked those owners of other CI.thanks:)
08:40:40 <anteaya> that might be a good way forward
08:41:06 <jyuso1> anteaya: yes.
08:42:54 <jyuso1> anteaya: still thank you for your reply.I always ask lots of questions:)
08:43:36 <anteaya> jyuso1: you do
08:43:41 <anteaya> I appreciate them
08:43:50 <anteaya> it means you are working very hard on your system
08:44:04 <anteaya> your logs are very nice, well formatted and informative
08:44:21 <anteaya> it means you care about providing good feedback to the developers
08:44:25 <anteaya> so your testing is useful
08:44:28 <anteaya> that means a lot
08:44:30 <anteaya> thank you
08:44:32 <jyuso1> anteaya: thanks.
08:44:42 <anteaya> :D
08:45:12 <jyuso1> anteaya: still lot of things to improve:)
08:45:25 <anteaya> jyuso1: it is a challenging area
08:45:38 <anteaya> and there are many things changing all the time
08:45:56 <anteaya> so it is a big job to stay current on the latest developments and impliment them
08:46:09 <anteaya> and yes, there is lots of room for improvement
08:49:01 <jyuso1> anteaya: yes.
08:49:17 <jyuso1> anteaya: I don't have more questions.
08:49:55 <jyuso1> anteaya: thank you very much.
08:50:30 <anteaya> jyuso1: thank you
08:50:36 <anteaya> :D
08:50:53 <anteaya> I have another meeting right after this one
08:51:06 <anteaya> so no harm keeping this meeting open until the top of the hour
08:52:17 <jyuso1> anteaya: Oh...you are the best.If I were you,I should go to bed few hours ago:)))
08:52:55 <anteaya> thanks
08:53:12 <anteaya> no matter where I am in the world I see to get up in the middle of the night
08:53:34 <anteaya> it is okay, folks at the keystone mid-cycle know not to expect me first thing in the morning
08:53:56 <anteaya> s/see/seem
08:58:46 <jyuso1> anteaya: sorry,need to leave my seat now.see you next week.Thank you:)
08:59:47 <anteaya> jyuso1: see you next week
08:59:54 <anteaya> #endmeeting