missing gluster error codes - why me?

I'm seeing this error in the last days: 7:42:03 Triggered by Gerrit: http://gerrit.ovirt.org/28721 07:42:03 Building remotely on fedora19-vm03 (fedora19) in workspace /home/jenkins/workspace/vdsm_master_verify-error-codes_merged 07:42:05 Fetching changes from the remote Git repository 07:42:05 Fetching upstream changes from git://gerrit.ovirt.org/ovirt-engine 07:42:09 Checking out Revision 922dd1177ab4a63ba10aaa90e89f32c0e253b8f3 (origin/master) 07:42:12 Fetching changes from the remote Git repository 07:42:12 Fetching upstream changes from git://gerrit.ovirt.org/vdsm 07:42:14 Checking out Revision 117797987b5c438a04e1de0ce423264b953c274a (master) 07:42:15 Cleaning workspace 07:42:15 Resetting working tree 07:42:15 No emails were triggered. 07:42:16 [vdsm_master_verify-error-codes_merged] $ /bin/sh /tmp/hudson1468381801262173053.sh 07:42:16 Ignored error codes: 701 4100 4101 4102 4103 4104 4105 4106 4107 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4123 4124 4126 4129 4130 4132 4133 4134 4136 4141 4143 4147 4400 4401 4402 4403 4405 4137 4138 4140 4144 4145 4146 4148 4150 4152 4153 07:42:18 missing error code: [ 4570 ] from: /home/jenkins/workspace/vdsm_master_verify-error-codes_merged/vdsm/vdsm/gluster/exception.py: code = 4570 07:42:18 missing error code: [ 4571 ] from: /home/jenkins/workspace/vdsm_master_verify-error-codes_merged/vdsm/vdsm/gluster/exception.py: code = 4571 07:42:18 missing error code: [ 4572 ] from: /home/jenkins/workspace/vdsm_master_verify-error-codes_merged/vdsm/vdsm/gluster/exception.py: code = 4572 07:42:18 missing error code: [ 4573 ] from: /home/jenkins/workspace/vdsm_master_verify-error-codes_merged/vdsm/vdsm/gluster/exception.py: code = 4573 07:42:18 Build step 'Execute shell' marked build as failure 07:42:18 Email was triggered for: Failure 07:42:18 Sending email for trigger: Failure 07:42:19 Sending email to: engine-patches(a)ovirt.org nsoffer(a)redhat.com 07:42:21 Finished: FAILURE I don't have any idea what is this check that this job is running, but it is not related to my patch. The patch under test did not change vdsm/gluster/exception.py, so it does not make sense to send mail to the author of the patch. I guess that this is the result of a bad commit, and now everyone will get this mail until the code is fixed. So practically these mails may cause this error to be fixed :-) Thanks, Nir