08:06:30 <anteaya> #startmeeting third-party
08:06:32 <openstack> Meeting started Tue Jul 21 08:06:30 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:06:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:06:35 <openstack> The meeting name has been set to 'third_party'
08:06:41 <anteaya> hello
08:06:48 <anteaya> sorry I'm late
08:06:56 <anteaya> anyone here for the third party meeting
08:11:06 <anteaya> tangchen: hello
08:11:31 <anteaya> tangchen: you need to make sure that your system doesn't submit the merge failed message back to the patch
08:11:32 <lennyb_> anteaya: Hi
08:11:37 <anteaya> hi lennyb_
08:11:53 <anteaya> tangchen: that is just noise about your system and doesn't help devs
08:12:02 <anteaya> lennyb_: how are you today?
08:12:42 <lennyb_> anteaya: thanks. how are you today?
08:12:44 <anteaya> tangchen: I don't see enough information to know why the test didnt' run
08:12:48 <anteaya> lennyb_: well thank you
08:12:59 <anteaya> lennyb_: and you?
08:13:10 <tangchen> anteaya: Hi, thanks for the reply.
08:13:40 <tangchen> But I don't quite know how to stop it from sending merge failed message
08:14:10 <lennyb_> anteaya: I am ok, but it's still early to be absolutely sure
08:14:17 <tangchen> And could you please tell me what info you need ?
08:15:29 <anteaya> lennyb_: I understand
08:15:44 <lennyb_> tangchen: sorry, I missed the start of the discussion, are they valid merge failures or it's a environment issue?
08:16:25 <anteaya> tangchen: well for starters you are responsible for however your system interacts with our gerrit, so if it posts a comment you have to make sure it is a comment you want, not just anything your system produces
08:16:58 <anteaya> so you have to ensure it isn't posting merge failure comments back to our gerrit
08:17:07 <anteaya> before you move off of the sandbox
08:17:13 <anteaya> and thank you for using the sandbox
08:17:49 <lennyb_> anteaya: I think it's part of the CI, if merge fails for a good reason CI should report about it.
08:18:16 <anteaya> lennyb_: no, the comment merge failed isn't helpful
08:18:30 <anteaya> build succeeded or build failed
08:18:46 <anteaya> telling someone they need to rebase their patch isn't the role of a third party ci
08:19:06 <anteaya> #link http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2015-07-21.log.html#t2015-07-21T07:06:20
08:19:17 <anteaya> tangchen was an hour early for the meeting
08:19:22 <lennyb_> anteaya: I am not sure that zuul can filter such things, I will check it
08:19:47 <anteaya> well we have told other operators not to post such messages
08:19:53 <anteaya> and they have accomplished it
08:19:59 <tangchen> Hi lennyb, anteaya: OK. I understand. But I dob't know how to config it to not to send such messages.
08:20:10 <anteaya> tangchen: thank you, and that's fine
08:20:18 <anteaya> you might have to run your own filter script
08:20:32 <anteaya> so that if your system produces such a message you don't send it
08:21:28 <anteaya> we don't need such a filter for infra so I doubt it is a configuration that can be set with the tools
08:23:49 <lennyb_> anteaya: but this script should be integrated with zuul....
08:25:13 <tangchen> lennyb_: Yes, I think this is a good idea, and will be much easier to use.  But again, I'm sorry, I don't know what a filter script looks like.
08:25:42 <anteaya> lennyb_: if you would like to offer a patch then folks can offer their opinions
08:25:49 <tangchen> Is it a shell or python script which I need to write myself ?
08:25:57 <anteaya> tangchen: yes
08:26:20 <anteaya> it would be a script you write to filter messages before they are sent to gerrit
08:26:21 <lennyb_> I will consider this, since we are experiencing such problem from time to time.
08:26:27 <anteaya> lennyb_: thanks
08:26:31 <tangchen> I think I can offer a patch since I want to join into CI development as soon as possible,
08:26:38 <anteaya> tangchen: thank you
08:27:00 <anteaya> tangchen: get something working on your system first and then offer a patch to gerrit
08:27:11 <anteaya> tangchen: thanks for your enthusiasum
08:27:14 <anteaya> :)
08:27:38 <anteaya> tangchen: so as to why your zuul doesn't trigger a job
08:27:51 <anteaya> I would need to see the full zuul log for that event
08:28:00 <anteaya> do you know paste.openstack.org?
08:28:10 <tangchen> wait a min
08:28:13 <anteaya> you paste the text into a window
08:28:22 <anteaya> and then bring the url of the paste back here
08:28:26 <anteaya> to the meeting
08:28:31 <anteaya> don't paste into the channel
08:29:04 <lennyb_> tangchen: if merge failed there is no reason to run a job
08:29:44 <anteaya> lennyb_: but did the merge fail or is that the default message the system is sending out
08:30:06 <anteaya> but you are correct, if the merge actually failed then the job wouldn't run
08:31:59 <lennyb_> anteaya: according to the message merge failed. We saw the same message when merge failed indeed.
08:32:40 <anteaya> good
08:32:52 <anteaya> it just isn't a message that is helpful to devs
08:32:56 <anteaya> from your system
08:33:14 <tangchen> http://paste.openstack.org/show/394824/
08:33:16 <anteaya> because is the patch actually needs to be rebased, Jenkins will tell them
08:33:17 <lennyb_> anteaya: this message comes from zuul developers :)
08:33:20 <anteaya> tangchen: thank you
08:33:22 <tangchen> Please refer to this url
08:33:47 <anteaya> lennyb_: right because zuul was written for infra, which needs to post the message, not for third party ci, which doesn't
08:35:25 <anteaya> tangchen: that patch adds a new file with no content
08:35:59 <anteaya> tangchen: while that should be enough of a change to allow the patch to be tested, perhaps you can add some content to the file for testing purposes
08:36:25 <tangchen> wait a min please
08:37:49 * anteaya waits
08:38:04 <anteaya> lennyb_: anything you wanted to talk about today?
08:38:24 <lennyb_> anteaya: no.
08:40:17 <tangchen> http://paste.openstack.org/show/394844/
08:40:18 <anteaya> okay, thanks for being here and helping tangchen :)
08:40:21 <tangchen> here, please
08:41:55 <anteaya> okay so you created a job and you can get it to run locally but you can't get it run on your patch
08:42:19 <anteaya> in your zuul/layout.yaml file
08:42:40 <anteaya> you need to ensure the job is on the repo being tested
08:43:50 <anteaya> for instance on the cinder repo for infra's tests, these are the job names that zuul knows about: http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n1646
08:44:13 <anteaya> if the job isn't in the zuul/layout.yaml file, zuul doesn't know about them
08:44:58 <lennyb_> tangchen: you also need to check in zuul.log what happened. If your changed was 'noticed' by zuul and what was decided.
08:45:08 <anteaya> doesn't know about it (it == the job)
08:45:15 <anteaya> lennyb_: good point
08:46:13 <lennyb_> you can increase debug level of zuul and gearman plugin ( if you use it), but in general zuul debug log provides you with enough info about it's steps
08:46:29 <anteaya> we have about 15 minutes remaining in the meeting, I just want to ensure you understand this is a meeting channel tangchen, not a channel for general questions
08:46:44 <anteaya> tangchen: what project do you want to test with your ci system?
08:47:04 <anteaya> once it works
08:47:26 <tangchen> anteaya: For now, just build the CI system and test sandbox
08:48:01 <anteaya> oh okay, well I ask because finding an operator who also tests the same project is helpful for you
08:48:09 <anteaya> so you have someone to ask questions
08:48:17 <anteaya> and a channel to have the conversation in
08:48:27 <anteaya> as the -meeting channel is for meetings only
08:49:16 <tangchen> Sorry for that and thanks for the info:)
08:49:34 <tangchen> Would you please tell me where is the best place to ask questions ?
08:49:52 <anteaya> tangchen: no problem
08:49:59 <anteaya> right, I'm trying to do that
08:50:11 <anteaya> the best place to ask is in the channel of the project you want to test
08:50:24 <anteaya> as someone is probably already successfully testing that project
08:50:34 <anteaya> so you can find them and they can help you
08:51:02 <anteaya> you can ask in -infra but sometimes we get too busy and can't be as helpful as we would like to be
08:52:31 <tangchen> OK, thanks. I'll check what you said above to see what the problem is.
08:52:54 <tangchen> And BTW, what does a meeting mean ?
08:53:03 <tangchen> what should I do in a meeting ?
08:54:00 <anteaya> we are in a meeting right now
08:54:23 <anteaya> are you using irc from the web browser?
08:55:09 <anteaya> and meetings are all structured differently
08:55:34 <anteaya> here is our channel logging page: http://eavesdrop.openstack.org/
08:56:01 <anteaya> it has links to all the meetings we have
08:56:15 <anteaya> you just starting asking questions an hour before this meeting
08:56:36 <anteaya> and most meetings are held at a time which is convient for north americans
08:56:39 <lennyb_> ok, sorry, but I must leave now. see you next time
08:56:48 <anteaya> lennyb_: thanks lennyb, see you next time
08:57:13 <anteaya> but I have this one specifically for people who have the sun in the sky now
08:57:52 <anteaya> tangchen: if you are using irc from a web browser I suggest you install an irc client
08:58:09 <tangchen> OK, thanks.
08:58:12 <tangchen> :)
08:58:13 <anteaya> tangchen: I find x-chat has a client of all 3 major operating systems
08:58:23 <anteaya> and I do believe is open source
08:58:24 <tangchen> Sure
08:58:38 <tangchen> OK, I'll install it
08:58:47 <tangchen> Bye :)
08:58:57 <anteaya> okay thank you tangchen
08:59:06 <anteaya> see you next week at the same time I hope
08:59:10 <anteaya> bye
08:59:59 <anteaya> it seems we are finished so I will end the meeting
09:00:03 <anteaya> see you next week
09:00:07 <anteaya> #endmeeting