Re: About NetBeans build quality

d'origine- > De : Hector Espert > Envoyé : samedi 2 mai 2020 17:19 > À : dev > Objet : Re: About NetBeans build quality > > Hi, > > About a pull request with an invalid mail or an invalid name. > > I've started experimenting with GitHub actions and I've

RE: About NetBeans build quality

logged and this information should be public ) Best Regards Eric -Message d'origine- De : Hector Espert Envoyé : samedi 2 mai 2020 17:19 À : dev Objet : Re: About NetBeans build quality Hi, About a pull request with an invalid mail or an invalid name. I've started experimenting

Re: About NetBeans build quality

flagged too before review code. It cost Matthias hours :p > Hector Espert do a lot of addition to travis test but I'm unsure the > coverage of travis test. > Best Regards > Eric > > -Message d'origine- > De : Neil C Smith > Envoyé : vendredi 1 mai 2020 12:23 > À : dev

Re: About NetBeans build quality

On Sat, 2 May 2020, 10:02 Matthias Bläsing, wrote: > a) an external change causes test failures - the recent failure of the > vscode extension build is one such sample > b) an external outage causes test failures - neighther github, nor > apache apache gitbox, nor the ousol, nor maven central

Re: About NetBeans build quality

Hi, Am Samstag, den 02.05.2020, 09:49 +0100 schrieb Neil C Smith: > If master testing is broken, that should be fixed before other > merges. If it's a flaky test, and we have a few, then it should be > retriggered to see if it passes. I'm not a fan of "this is always right in all situations",

Re: About NetBeans build quality

On Sat, 2 May 2020 at 08:20, Benjamin Graf wrote: > Yes, and they are green because work has been done to get them green > again. :-) Thanks! :-) > The problem is the big bunch of PRs based on old master > snapshots that where unstable in time of creation. That's the reason > their Travis

Re: About NetBeans build quality

On Sat, 2 May 2020 at 08:01, Matthias Bläsing wrote: > Am Samstag, den 02.05.2020, 00:57 +0200 schrieb Eric Barboni: > > For what I encounter since 2 months I guess, travis job is not more > > re triggerable (partial job too). > > I saw that in the past, what helped was logging out of travis-ci

Re: About NetBeans build quality

a lot of addition to travis test but I'm unsure the coverage > of travis test. > Best Regards > Eric > > -Message d'origine- > De : Neil C Smith > Envoyé : vendredi 1 mai 2020 12:23 > À : dev > Objet : Re: About NetBeans build quality > > On Fri, 1 May 2020 at 09:3

Re: About NetBeans build quality

Hi Eric, Am Samstag, den 02.05.2020, 00:57 +0200 schrieb Eric Barboni: > For what I encounter since 2 months I guess, travis job is not more > re triggerable (partial job too). I saw that in the past, what helped was logging out of travis-ci and logging back in. I don't know how they

RE: About NetBeans build quality

the coverage of travis test. Best Regards Eric -Message d'origine- De : Neil C Smith Envoyé : vendredi 1 mai 2020 12:23 À : dev Objet : Re: About NetBeans build quality On Fri, 1 May 2020 at 09:32, Benjamin Graf wrote: > IMHO we all should have a look and taking more care after our PRs be

Re: About NetBeans build quality

On Fri, 1 May 2020 at 09:32, Benjamin Graf wrote: > IMHO we all should have a look and taking more care after our PRs being green > on Travis, too. Sometimes periodically rebasing against master does help > getting green again if build is broken because of Travis bugs or someone else > broken

About NetBeans build quality

Hi everybody, I'm a bit concerned about the current build quality of NetBeans master branch and PRs done in the past. I have the feeling we're facing many broken PR builds over the last time causing/risking master to get unstable especially in the current process of building a LTS release.