Any interest in creating a "broken build" list? I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later. The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them. Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list?
I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later.
The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them.
Can't we use infra@ for build failing on infra issues and devel@ for the real issues?
Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
--oLBj+sq0vYjzfsbl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05/26, Sandro Bonazzola wrote:
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list? =20 I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later. =20 The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them. =20 Can't we use infra@ for build failing on infra issues and devel@ for the = real issues?
I thought we already were doing that :S
=20 =20
=20 Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com =20 _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel =20 =20 =20 --=20 Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --oLBj+sq0vYjzfsbl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVZI+5AAoJEEBxx+HSYmnDrlcH/26bJjXDCBEISyKpL/cay9cX Txd3Ak1aRYcDxZMm6vbOrlVE7lfV/L31F+engjIxcsDOO21cdjGVcVWkVCM+zbVR /XpFnH8NQFaHbZ8Qoz/BwzApfHiuzy7GiYsBpq4A2RiDS+aV06Te5qmQGvfCgUg0 8TB5wMz/Co1TXBIoEx5D0L3mQDX82EPTIUe2cJwiIjFFUjs+OXw7WdPLh0VUvUSi Li6ZosQnG8VUe39NdfhCb7ISWicDvtU4E3aUiOo2xZ7jUR+BIlmsiw0u9y4EpMrX nDZovZPc1meDY7MGDeK6snydKVm1oOI1UaCBYwD1ivOXaA40/9ASO0hZJhsS4q4= =t47+ -----END PGP SIGNATURE----- --oLBj+sq0vYjzfsbl--
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Greg Sheremeta" <gshereme@redhat.com>, "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Tuesday, May 26, 2015 11:22:33 AM Subject: Re: [ovirt-devel] broken build list?
On 05/26, Sandro Bonazzola wrote:
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list?
I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later.
The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them.
Can't we use infra@ for build failing on infra issues and devel@ for the real issues?
I thought we already were doing that :S
IMHO, there is way too much noise on infra.
Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
=20 =20 ----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Greg Sheremeta" <gshereme@redhat.com>, "infra" <infra@ovirt.org>, = devel@ovirt.org Sent: Tuesday, May 26, 2015 11:22:33 AM Subject: Re: [ovirt-devel] broken build list? =20 On 05/26, Sandro Bonazzola wrote:
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list? =20 I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later. =20 The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them. =20 Can't we use infra@ for build failing on infra issues and devel@ for =
--ALfTUftag+2gvp1h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05/26, Greg Sheremeta wrote: the
real issues? =20 I thought we already were doing that :S =20 IMHO, there is way too much noise on infra.
really? I thought it was mostly idle... have to check my filters
=20
=20
=20 =20
=20 Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com =20 _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel =20 =20 =20 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaborat= ion. See how it works at redhat.com
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra =20 -- David Caro =20 Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D =20 Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 =20
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --ALfTUftag+2gvp1h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVZJFRAAoJEEBxx+HSYmnD9MwH/35ab08z1AchSsFum+moNgIN XMeGqZccAuSHFHGpdM19moU+XM7AMLs6rYvQHXfxRChAZUG7J9XvUzCZmho7y24i YOn4c+Vc+g1aIaLSkyIbz8HKq5MEVav3iMy323z0UFXeTL8Kvjt3eGjlZqHPlMoY 9BFK8cqa14aAe4X8k16AAo4fQNo69BZ3S08Gh/MTz5sVE7bNP71aQ/YLbUnkoP3G /h4phLXmqnRH2Ohdw67P8DKl1IzJRPQx3CexajAuOsQAevoXX+TFbaMGhXTIXp9r 2cQpTPq6W8fsmXrmm3D9rAfD1GuWOvNohUZYfSvHT8Qjl0b4npg6JFJlw+wXl4U= =AhSw -----END PGP SIGNATURE----- --ALfTUftag+2gvp1h--
----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 6:25:08 PM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Greg Sheremeta" <gshereme@redhat.com>, "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Tuesday, May 26, 2015 11:22:33 AM Subject: Re: [ovirt-devel] broken build list?
On 05/26, Sandro Bonazzola wrote:
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list?
I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later.
The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them.
Can't we use infra@ for build failing on infra issues and devel@ for the real issues?
I thought we already were doing that :S
IMHO, there is way too much noise on infra.
i think last time we requested that any error that is unjustified to be reported to infra, so we can handle it. sure, we might not be able to handle any issue right away, but only if we'll have the issues reported we can start mitigating things. the last thing we'd like is to people not to trust ci and ignore errors... bad for everyone.. if regressions will go in due to noise. take into account that the environment isn't hosted on a perfect environment isolated from the world, any network issue with external repositories or slow gerrit response might fail jobs, we're working hard to eliminate those as much as possible. i suggest that any issue you think is not related to your patch and isn't a real issue ,report it to infra list with: subject: [ TICKET ] short desc of the problem body: info on the problem with links and why do you think its we'll accumulate the tickets and try to debug each issue according to capacity, we're in the process automating this via email to support and opening ticket in jira. e.
Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Greg Sheremeta" <gshereme@redhat.com> Cc: "David Caro" <dcaroest@redhat.com>, devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 11:40:16 AM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 6:25:08 PM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Greg Sheremeta" <gshereme@redhat.com>, "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Tuesday, May 26, 2015 11:22:33 AM Subject: Re: [ovirt-devel] broken build list?
On 05/26, Sandro Bonazzola wrote:
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list?
I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later.
The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them.
Can't we use infra@ for build failing on infra issues and devel@ for the real issues?
I thought we already were doing that :S
IMHO, there is way too much noise on infra.
i think last time we requested that any error that is unjustified to be reported to infra, so we can handle it. sure, we might not be able to handle any issue right away, but only if we'll have the issues reported we can start mitigating things.
the last thing we'd like is to people not to trust ci and ignore errors...
I can't speak for everyone, but when I see one of my builds fail, my first thought is that someone else broke it. Maybe I need to check my ego, haha :)
bad for everyone.. if regressions will go in due to noise.
take into account that the environment isn't hosted on a perfect environment isolated from the world, any network issue with external repositories or slow gerrit response might fail jobs, we're working hard to eliminate those as much as possible.
i suggest that any issue you think is not related to your patch and isn't a real issue ,report it to infra list with:
subject: [ TICKET ] short desc of the problem body: info on the problem with links and why do you think its
Ok, so if everyone will use infra this way, that is fine. I rarely see anyone reporting build issues. Thanks!
we'll accumulate the tickets and try to debug each issue according to capacity, we're in the process automating this via email to support and opening ticket in jira.
e.
Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "David Caro" <dcaroest@redhat.com>, devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 6:45:17 PM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Greg Sheremeta" <gshereme@redhat.com> Cc: "David Caro" <dcaroest@redhat.com>, devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 11:40:16 AM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 6:25:08 PM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Greg Sheremeta" <gshereme@redhat.com>, "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Tuesday, May 26, 2015 11:22:33 AM Subject: Re: [ovirt-devel] broken build list?
On 05/26, Sandro Bonazzola wrote:
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list?
I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later.
The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them.
Can't we use infra@ for build failing on infra issues and devel@ for the real issues?
I thought we already were doing that :S
IMHO, there is way too much noise on infra.
i think last time we requested that any error that is unjustified to be reported to infra, so we can handle it. sure, we might not be able to handle any issue right away, but only if we'll have the issues reported we can start mitigating things.
the last thing we'd like is to people not to trust ci and ignore errors...
I can't speak for everyone, but when I see one of my builds fail, my first thought is that someone else broke it. Maybe I need to check my ego, haha :)
I can't say the same thing about other developers unfortunately, master branch suffered pretty ugly regressions during past weeks, which could have been avoided if the jobs were running ok and weren't being ignored or reported for false positives.
bad for everyone.. if regressions will go in due to noise.
take into account that the environment isn't hosted on a perfect environment isolated from the world, any network issue with external repositories or slow gerrit response might fail jobs, we're working hard to eliminate those as much as possible.
i suggest that any issue you think is not related to your patch and isn't a real issue ,report it to infra list with:
subject: [ TICKET ] short desc of the problem body: info on the problem with links and why do you think its
Ok, so if everyone will use infra this way, that is fine. I rarely see anyone reporting build issues.
Thanks!
we'll accumulate the tickets and try to debug each issue according to capacity, we're in the process automating this via email to support and opening ticket in jira.
e.
Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
participants (4)
-
David Caro -
Eyal Edri -
Greg Sheremeta -
Sandro Bonazzola