Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-23 Thread Ben Cooksley
On Mon, Jan 24, 2022 at 12:56 AM Albert Astals Cid wrote: > El diumenge, 23 de gener de 2022, a les 1:59:01 (CET), Ben Cooksley va > escriure: > > On Sun, Jan 23, 2022 at 12:29 PM Albert Astals Cid > wrote: > > > > > El diumenge, 23 de gener de 2022, a les 0:09:23 (CET), Ben Cooksley va > > >

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-23 Thread Albert Astals Cid
El diumenge, 23 de gener de 2022, a les 1:59:01 (CET), Ben Cooksley va escriure: > On Sun, Jan 23, 2022 at 12:29 PM Albert Astals Cid wrote: > > > El diumenge, 23 de gener de 2022, a les 0:09:23 (CET), Ben Cooksley va > > escriure: > > > On Sun, Jan 23, 2022 at 11:29 AM Albert Astals Cid > >

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-22 Thread Ben Cooksley
On Sun, Jan 23, 2022 at 12:38 PM Albert Astals Cid wrote: > El diumenge, 23 de gener de 2022, a les 0:09:23 (CET), Ben Cooksley va > escriure: > > On Sun, Jan 23, 2022 at 11:29 AM Albert Astals Cid > wrote: > > > > > El dissabte, 22 de gener de 2022, a les 6:11:29 (CET), Ben Cooksley va > > >

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-22 Thread Ben Cooksley
On Sun, Jan 23, 2022 at 12:29 PM Albert Astals Cid wrote: > El diumenge, 23 de gener de 2022, a les 0:09:23 (CET), Ben Cooksley va > escriure: > > On Sun, Jan 23, 2022 at 11:29 AM Albert Astals Cid > wrote: > > > > > El dissabte, 22 de gener de 2022, a les 6:11:29 (CET), Ben Cooksley va > > >

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-22 Thread Albert Astals Cid
El diumenge, 23 de gener de 2022, a les 0:09:23 (CET), Ben Cooksley va escriure: > On Sun, Jan 23, 2022 at 11:29 AM Albert Astals Cid wrote: > > > El dissabte, 22 de gener de 2022, a les 6:11:29 (CET), Ben Cooksley va > > escriure: > > > EXCLUDE_DEPRECATED_BEFORE_AND_ATOn Sat, Jan 22, 2022 at

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-22 Thread Albert Astals Cid
El diumenge, 23 de gener de 2022, a les 0:09:23 (CET), Ben Cooksley va escriure: > On Sun, Jan 23, 2022 at 11:29 AM Albert Astals Cid wrote: > > > El dissabte, 22 de gener de 2022, a les 6:11:29 (CET), Ben Cooksley va > > escriure: > > > EXCLUDE_DEPRECATED_BEFORE_AND_ATOn Sat, Jan 22, 2022 at

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-22 Thread Ben Cooksley
On Sun, Jan 23, 2022 at 11:29 AM Albert Astals Cid wrote: > El dissabte, 22 de gener de 2022, a les 6:11:29 (CET), Ben Cooksley va > escriure: > > EXCLUDE_DEPRECATED_BEFORE_AND_ATOn Sat, Jan 22, 2022 at 1:31 PM Friedrich > > W. H. Kossebau wrote: > > > > > Hi, > > > > > > > seems that Gitlab CI

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-22 Thread Albert Astals Cid
El dissabte, 22 de gener de 2022, a les 6:11:29 (CET), Ben Cooksley va escriure: > EXCLUDE_DEPRECATED_BEFORE_AND_ATOn Sat, Jan 22, 2022 at 1:31 PM Friedrich > W. H. Kossebau wrote: > > > Hi, > > > > seems that Gitlab CI is currently configured to show the green "Success" > > checkmark for

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-22 Thread Volker Krause
Important topic, thanks for bringing this up! On Samstag, 22. Januar 2022 01:31:13 CET Friedrich W. H. Kossebau wrote: > Bhushan gave two first ideas just now on #kde-sysadmin: > > Well we can add a switch that repos can commit to saying test failure is > > build failure > > > Another

Re: Gitlab CI: failed unit tests vs. currently passing CI

2022-01-21 Thread Ben Cooksley
EXCLUDE_DEPRECATED_BEFORE_AND_ATOn Sat, Jan 22, 2022 at 1:31 PM Friedrich W. H. Kossebau wrote: > Hi, > seems that Gitlab CI is currently configured to show the green "Success" > checkmark for pipeline runs even if unit tests are failing. > That is correct, only compilation or other internal

Gitlab CI: failed unit tests vs. currently passing CI

2022-01-21 Thread Friedrich W. H. Kossebau
Hi, seems that Gitlab CI is currently configured to show the green "Success" checkmark for pipeline runs even if unit tests are failing. Reasons seems to be that there Gitlab only knows Yay or Nay, without the warning state level known from Jenkins. And given that quite some projects (sadly)