Re: [Development] Monthly CI maintenance break - April (Mon, Apr 17th 2023)

[Heikki Halmet via Development]

This starts NOW

From: Heikki Halmet
Sent: tiistai 11. huhtikuuta 2023 11.54
To: Qt development mailing list 
Subject: RE: Monthly CI maintenance break - April (Mon, Apr 17th 2023)

Time correction: Maintenance will start at 5:00 UTC

From: Heikki Halmet
Sent: maanantai 10. huhtikuuta 2023 8.21
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - April (Mon, Apr 17th 2023)

Hi,

We'll have our scheduled maintenance break on next Monday (17th of April). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - April (Mon, Apr 17th 2023)

[Heikki Halmet via Development]

Time correction: Maintenance will start at 5:00 UTC

From: Heikki Halmet
Sent: maanantai 10. huhtikuuta 2023 8.21
To: Qt development mailing list 
Subject: Monthly CI maintenance break - April (Mon, Apr 17th 2023)

Hi,

We'll have our scheduled maintenance break on next Monday (17th of April). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Monthly CI maintenance break - April (Mon, Apr 17th 2023)

[Heikki Halmet via Development]

Hi,

We'll have our scheduled maintenance break on next Monday (17th of April). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - February (Mon, Feb 6th 2023)

[Heikki Halmet via Development]

CI is up and running again.

Thanks for the patience!


From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 19.38
To: Qt development mailing list 
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

We are facing problems with CI. Opennebula don't allocate VMs correctly. 
Unfortunately we were forced to shutdown the CI for now. Hopefully we will get 
it back online tomorrow.


From: Development 
mailto:development-boun...@qt-project.org>> 
On Behalf Of Heikki Halmet via Development
Sent: maanantai 6. helmikuuta 2023 16.50
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Re: [Development] Monthly CI maintenance break - February (Mon, Feb 
6th 2023)

Maintenance break is now DONE.

Thanks for the patience!


From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 14.01
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Maintenance break is taking more time than we expected. Our current estimate 
for downtime is 1-2 hours

From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 8.01
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

This maintenance break starts NOW

From: Heikki Halmet
Sent: maanantai 30. tammikuuta 2023 9.37
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Hi,

We'll have our scheduled maintenance break on next Monday (6th of February). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - February (Mon, Feb 6th 2023)

[Heikki Halmet via Development]

We are facing problems with CI. Opennebula don't allocate VMs correctly. 
Unfortunately we were forced to shutdown the CI for now. Hopefully we will get 
it back online tomorrow.


From: Development  On Behalf Of Heikki 
Halmet via Development
Sent: maanantai 6. helmikuuta 2023 16.50
To: Qt development mailing list 
Subject: Re: [Development] Monthly CI maintenance break - February (Mon, Feb 
6th 2023)

Maintenance break is now DONE.

Thanks for the patience!


From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 14.01
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Maintenance break is taking more time than we expected. Our current estimate 
for downtime is 1-2 hours

From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 8.01
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

This maintenance break starts NOW

From: Heikki Halmet
Sent: maanantai 30. tammikuuta 2023 9.37
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Hi,

We'll have our scheduled maintenance break on next Monday (6th of February). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - February (Mon, Feb 6th 2023)

[Heikki Halmet via Development]

Maintenance break is now DONE.

Thanks for the patience!


From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 14.01
To: Qt development mailing list 
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Maintenance break is taking more time than we expected. Our current estimate 
for downtime is 1-2 hours

From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 8.01
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

This maintenance break starts NOW

From: Heikki Halmet
Sent: maanantai 30. tammikuuta 2023 9.37
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Hi,

We'll have our scheduled maintenance break on next Monday (6th of February). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - February (Mon, Feb 6th 2023)

[Heikki Halmet via Development]

Maintenance break is taking more time than we expected. Our current estimate 
for downtime is 1-2 hours

From: Heikki Halmet
Sent: maanantai 6. helmikuuta 2023 8.01
To: Qt development mailing list 
Subject: RE: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

This maintenance break starts NOW

From: Heikki Halmet
Sent: maanantai 30. tammikuuta 2023 9.37
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Hi,

We'll have our scheduled maintenance break on next Monday (6th of February). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - February (Mon, Feb 6th 2023)

[Heikki Halmet via Development]

This maintenance break starts NOW

From: Heikki Halmet
Sent: maanantai 30. tammikuuta 2023 9.37
To: Qt development mailing list 
Subject: Monthly CI maintenance break - February (Mon, Feb 6th 2023)

Hi,

We'll have our scheduled maintenance break on next Monday (6th of February). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Monthly CI maintenance break - February (Mon, Feb 6th 2023)

[Heikki Halmet via Development]

Hi,

We'll have our scheduled maintenance break on next Monday (6th of February). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - January (Mon 9th Jan 2023)

[Heikki Halmet via Development]

This took more than we expected but finally this is DONE.

Thank you for your patience!

From: Development  On Behalf Of Ville-Pekka 
Karhu via Development
Sent: maanantai 9. tammikuuta 2023 8.05
To: Qt development mailing list 
Subject: Re: [Development] Monthly CI maintenance break - January (Mon 9th Jan 
2023)

This maintenance break starts NOW

From: Ville-Pekka Karhu
Sent: Monday, January 2, 2023 09:46
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - January (Mon 9th Jan 2023)

Hi all!

We'll have our scheduled maintenance break on next Monday (9th of January). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.

Br,
VP

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Requesting platform and SW upgrade exceptions for 6.5

[Heikki Halmet via Development]

Hi,

Requesting exception for following platforms and SW upgrades after Qt 6.5 Beta 
1 is out:

RHEL 9: https://codereview.qt-project.org/c/qt/qt5/+/447263
OpenSSL 3: https://codereview.qt-project.org/c/qt/qt5/+/410267/23
Ubuntu 22.04: https://codereview.qt-project.org/c/qt/qt5/+/436468
Xcode 14.2: https://codereview.qt-project.org/c/qt/qt5/+/449217
MacOS 13 intel: https://codereview.qt-project.org/c/qt/qt5/+/445278


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Problems with CI

[Heikki Halmet via Development]

Problem solved. CI works normally again.

Thanks for the patience!

Br
Heikki

From: Heikki Halmet
Sent: perjantai 2. joulukuuta 2022 10.13
To: 'development@qt-project.org' ; Qt Development 
; Qt Externals 
Subject: Problems with CI

Hi,

We currently have problems with Windows signing. This will affect to all 
integrations and all windows builds will fail. We are trying to fix it ASAP.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Problems with CI

[Heikki Halmet via Development]

Hi,

We currently have problems with Windows signing. This will affect to all 
integrations and all windows builds will fail. We are trying to fix it ASAP.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] 'CI Reviewers' group to reviewers section when adding changes to Qt5/coin

[Heikki Halmet via Development]

Hi,

Please remember to add 'CI Reviewers' group to reviewers section when you make 
changes under 'coin' folder in 
"https://codereview.qt-project.org/qt/qt5;<https://codereview.qt-project.org/qt/qt5%22>.
CI team wants to keep track what changes in CI environment.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - June (Mon 6th Jun 2022)

[Heikki Halmet]

Hi,

Maintenance break is now DONE


Br
Heikki

From: Development  On Behalf Of Heikki 
Halmet
Sent: maanantai 6. kesäkuuta 2022 8.00
To: Qt development mailing list 
Subject: Re: [Development] Monthly CI maintenance break - June (Mon 6th Jun 
2022)

Hi,

This maintenance break starts NOW


Br
Heikki

From: Heikki Halmet
Sent: maanantai 30. toukokuuta 2022 15.26
To: Heikki Halmet mailto:heikki.hal...@qt.io>>; Qt 
development mailing list 
mailto:development@qt-project.org>>
Subject: RE: Monthly CI maintenance break - June (Mon 6th Jun 2022)

Little correction here. Work will start at 5:00 UTC on next Monday

Br
Heikki

From: Development 
mailto:development-boun...@qt-project.org>> 
On Behalf Of Heikki Halmet
Sent: maanantai 30. toukokuuta 2022 15.15
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: [Development] Monthly CI maintenance break - June (Mon 6th Jun 2022)


Hi all!



We'll have our scheduled maintenance break on next Monday (6th of June). We'll 
begin our work at 6:00 UTC and you can prepare for 6 hours of CI not working.






Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - June (Mon 6th Jun 2022)

[Heikki Halmet]

Hi,

This maintenance break starts NOW


Br
Heikki

From: Heikki Halmet
Sent: maanantai 30. toukokuuta 2022 15.26
To: Heikki Halmet ; Qt development mailing list 

Subject: RE: Monthly CI maintenance break - June (Mon 6th Jun 2022)

Little correction here. Work will start at 5:00 UTC on next Monday

Br
Heikki

From: Development 
mailto:development-boun...@qt-project.org>> 
On Behalf Of Heikki Halmet
Sent: maanantai 30. toukokuuta 2022 15.15
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: [Development] Monthly CI maintenance break - June (Mon 6th Jun 2022)


Hi all!



We'll have our scheduled maintenance break on next Monday (6th of June). We'll 
begin our work at 6:00 UTC and you can prepare for 6 hours of CI not working.






Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - June (Mon 6th Jun 2022)

[Heikki Halmet]

Little correction here. Work will start at 5:00 UTC on next Monday

Br
Heikki

From: Development  On Behalf Of Heikki 
Halmet
Sent: maanantai 30. toukokuuta 2022 15.15
To: Qt development mailing list 
Subject: [Development] Monthly CI maintenance break - June (Mon 6th Jun 2022)


Hi all!



We'll have our scheduled maintenance break on next Monday (6th of June). We'll 
begin our work at 6:00 UTC and you can prepare for 6 hours of CI not working.






Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Monthly CI maintenance break - June (Mon 6th Jun 2022)

[Heikki Halmet]

Hi all!



We'll have our scheduled maintenance break on next Monday (6th of June). We'll 
begin our work at 6:00 UTC and you can prepare for 6 hours of CI not working.






Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI is offline until tomorrow

[Heikki Halmet]

Hi,

Unfortunately we needed to shutdown the CI again for tonight because of low 
disk space. People are working hard to get this issue solved quickly as 
possible.
Hopefully we can put it online again tomorrow morning.

Thank you for your patience!


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI is offline until monday

[Heikki Halmet]

Hi,

Unfortunately we needed to shutdown the CI for the weekend. We are having 
issues with the disk space and we can't take a risk that it would fill up 
during the weekend.
Hopefully during next week we have needed tools to resolve this issue.

Thank you for your patience!


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - February (Mon 7th Feb 2022)

[Heikki Halmet]

Hi,

Test server had some issues and it needed to be recreated from backups. When 
the server was booted up it apparently didn't start Squid daemon. This was 
manually fixed this morning

Br
Heikki

-Original Message-
From: Development  On Behalf Of Thiago 
Macieira
Sent: tiistai 8. helmikuuta 2022 22.22
To: development@qt-project.org
Subject: Re: [Development] Monthly CI maintenance break - February (Mon 7th Feb 
2022)

On Tuesday, 8 February 2022 00:37:50 PST Ville-Pekka Karhu wrote:
> This is now DONE

Not exactly. The Squid daemon running on port 3130 on the network test server 
isn't up. All integrations in qtbase are currently failing.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CI down

[Heikki Halmet]

Hi,

We have monthly CI maintenance break starting tomorrow morning. We should have 
CI online after it. Until then we keep the CI offline so that we don't stumble 
this compellent issue again during the night time.

Br
Heikki

From: Development  On Behalf Of Heikki 
Halmet
Sent: sunnuntai 6. helmikuuta 2022 10.56
To: Qt development mailing list 
Subject: [Development] CI down

Hi,

Our CI is currently down. It seems that the compellent got filled this morning 
and because of it there are multiple critical VMs down.
Work to get this fixed ongoing. Unfortunately no estimation at this point


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI down

[Heikki Halmet]

Hi,

Our CI is currently down. It seems that the compellent got filled this morning 
and because of it there are multiple critical VMs down.
Work to get this fixed ongoing. Unfortunately no estimation at this point


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Senior Software Engineer | CI Lead
Delivery Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - January (Mon 10th Jan 2022)

[Heikki Halmet]

Hi,

Unfortunately maintenance break is still ongoing. We have some issues which CI 
team is trying to resolve as quick as possible.

Br
Heikki

From: Development  On Behalf Of Ville-Pekka 
Karhu
Sent: maanantai 10. tammikuuta 2022 8.06
To: Qt development mailing list 
Subject: Re: [Development] Monthly CI maintenance break - January (Mon 10th Jan 
2022)

This maintenance break starts NOW

From: Ville-Pekka Karhu
Sent: Monday, January 3, 2022 09:19
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - January (Mon 10th Jan 2022)


Hi all!



We'll have our scheduled maintenance break on next Monday (10th of January). 
We'll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.



Br,

VP

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - Moved to June (Mon 14th Jun 2021)

[Heikki Halmet]

This maintenance break is now DONE

From: Development  On Behalf Of Heikki 
Halmet
Sent: maanantai 14. kesäkuuta 2021 9.01
To: Qt development mailing list 
Subject: Re: [Development] Monthly CI maintenance break - Moved to June (Mon 
14th Jun 2021)

This maintenance break starts NOW

From: Development 
mailto:development-boun...@qt-project.org>> 
On Behalf Of Ville-Pekka Karhu
Sent: torstai 3. kesäkuuta 2021 15.32
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Re: [Development] Monthly CI maintenance break - Moved to June (Mon 
14th Jun 2021)

Hi,

We will postpone this maintenance break by a week because of 6.2 Feature Freeze 
activities.


From: Ville-Pekka Karhu
Sent: Monday, May 31, 2021 12:50
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - June (Mon 7th Jun 2021)


Hi all!



We'll have our scheduled maintenance break on next Monday (7th of June). We'll 
begin our work at 5:00 UTC and you can prepare for 6 hours of CI not working.



Br,

VP

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - Moved to June (Mon 14th Jun 2021)

[Heikki Halmet]

This maintenance break starts NOW

From: Development  On Behalf Of Ville-Pekka 
Karhu
Sent: torstai 3. kesäkuuta 2021 15.32
To: Qt development mailing list 
Subject: Re: [Development] Monthly CI maintenance break - Moved to June (Mon 
14th Jun 2021)

Hi,

We will postpone this maintenance break by a week because of 6.2 Feature Freeze 
activities.


From: Ville-Pekka Karhu
Sent: Monday, May 31, 2021 12:50
To: Qt development mailing list 
mailto:development@qt-project.org>>
Subject: Monthly CI maintenance break - June (Mon 7th Jun 2021)


Hi all!



We'll have our scheduled maintenance break on next Monday (7th of June). We'll 
begin our work at 5:00 UTC and you can prepare for 6 hours of CI not working.



Br,

VP

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] download.qt.io is down

[Heikki Halmet]

Hi,

This will also affect to provisioning in CI


Br
Heikki

-Original Message-
From: Development  On Behalf Of Jani 
Heikkinen
Sent: tiistai 19. tammikuuta 2021 11.18
To: development@qt-project.org; releas...@qt-project.org
Subject: [Development] download.qt.io is down

Hi all,

You have most probably already noticed that download.qt.io is down. We are 
fixing the issue so please be patient. I'll inform you when it should work OK

br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CI is having problems with provisioning

[Heikki Halmet]

Hi,

Issue has been fixed and provisioning should work now. Thank you for your 
patience!



  *   Heikki

From: Development  On Behalf Of Heikki 
Halmet
Sent: tiistai 15. joulukuuta 2020 8.22
To: Qt development mailing list 
Subject: [Development] CI is having problems with provisioning

Hi,

After CI maintenance break we have faced problems with provisioning. CI team is 
currently trying to fix those with highest priority.



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI is having problems with provisioning

[Heikki Halmet]

Hi,

After CI maintenance break we have faced problems with provisioning. CI team is 
currently trying to fix those with highest priority.



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Building additional components with Conan for Qt 6

[Heikki Halmet]

Hi,

I'm not the expert when it comes to Conan so I'm asking what would be the main 
gain we would achieve by using Conan instead of scripts we currently have..? 
List of packages and versions in one place? With quick review this would take 
lot of effort and honestly I'm pretty skeptical about the gain we would have vs 
time we would spent to make needed changes.

>>> 2) Build stuff from sources in provisioning time, sometimes in a 
>>> sophisticated way (e.g. 
>>> https://code.qt.io/cgit/qt/qt5.git/tree/coin/provisioning/common/windows/android-openssl.ps1).
>>>  These can be (and IMO should be) replaced with Conan, to reduce 
>>> provisioning time and complexity.
>> Of course, it's also possible to use conan packages for category (1), 
>> however this may require writing quite a few custom recipes (see manual 
>> [1]), possibly containing more boilerplate than existing ps1 snippets. 
>> However, this would allow to have a nice list of all provisioned packages 
>> with >> their versions in one place.
You mean reducing provisioning time when everything would be prebuilt already? 
This is something we could change to existing scripts already. Script could 
check from the local cache do we have the prebuilt stuff and if don't then 
build those and add those to cache. And next time use prebuilt package. 
Currently, e.g. with gcc installation, script will use prebuilt package if it 
exist and if don't it will be built from sources. But in some cases we have 
just prebuilt the package and added it to cache without source build option in 
the script.
With installers I don't think there's no point to start putting those under 
Conan packages. I think the only thing we would gain here is the listing thing. 
And what comes to complexity - if we would start using Conan for everything we 
still would need to start creating  quite complexity conanfiles for it, right? 
I guess the gain in some cases would be that we could use the same conanfile in 
unix and windows.

>>> In current implementation stuff is loaded from Internet, but all packages 
>>> are verified against manifests stored in provisioning repo. But you can 
>>> also set up internal Conan repository by running instance of Artifactory CE.
Yes, we would have to use our own internal Conan repo and the repo should be 
kept up to date automatically.  
Do we know what kind of regression Conan repos have? Is there a risk that some 
package is not reachable etc. E.g. with brew we have stumbled to connection 
problems or their repositories haven't been available.

Back in days we used Puppet for provisioning. With puppet we stumbled to 
problems which were quite hard to debug. Reason why we dump it and moved to 
shell/powershell scripts was to simplify things and make debugging easier. 

We definitely could improve the readability of our provisioning scripts but 
it's all matter of prioritizing.


Br
Heikki


-Original Message-
From: Development  On Behalf Of Konstantin 
Tokarev
Sent: Thursday, October 8, 2020 12:24 PM
To: Toni Saario ; Iikka Eklund ; Richard 
Weickelt ; development@qt-project.org
Subject: Re: [Development] Building additional components with Conan for Qt 6



08.10.2020, 11:59, "Toni Saario" :
>>> Most of provisioning scripts fall into 2 categories:
>>> 1) Download installer (or other binary package) of 3rd party stuff, verify 
>>> checksum, install. These scripts are quite simple.
>>> 2) Build stuff from sources in provisioning time, sometimes in a 
>>> sophisticated way (e.g. 
>>> https://code.qt.io/cgit/qt/qt5.git/tree/coin/provisioning/common/windows/android-openssl.ps1).
>>>  These can be (and IMO should be) replaced with Conan, to reduce 
>>> provisioning time and complexity.
>>
>> Of course, it's also possible to use conan packages for category (1), 
>> however this may require writing quite a few custom recipes (see manual 
>> [1]), possibly containing more boilerplate than existing ps1 snippets. 
>> However, this would allow to have a nice list of all provisioned packages 
>> with their versions in one place.
>>
>> [1] 
>> https://docs.conan.io/en/latest/devtools/create_installer_packages.html#create-installer-packages
> That is what the automatic documentation tools are asking. Might be stupid 
> questions due to the knowledge. We would install all dependencies during the 
> provisioning and during the builds conan only exposes dependencies listed in 
> the conanfile?

Yes. There would be no network downloads or unnecessary compilations during 
product builds.

> One thing that conflicts a little bit here is that we want to use cached 
>stuff from our servers instead of downloading from the internet in the 
>provisioning and also have the provisioning to be runnable by anyone, but i 
>guess that if the conan caches all the packages then it equals pretty much the 
>same.

In current implementation stuff is loaded from Internet, but all packages are 
verified against manifests stored in provisioning repo. But you can also set up 

[Development] Monthly maintenance break on CI Infra

[Heikki Halmet]

Hi!

To keep things updated CI Team is planning to start monthly maintenance break 
which is used to update various Infra SW. Breaks might take several hours which 
means that during that time CI might be down. Downtime depends on what we are 
updating and how well we can do things on parallel.

Monthly maintenance break will be kept on first Monday of the month. E.g. first 
one is planned to be on next Monday (5th of October) . If there's something 
critical blocking the maintenance break (e.g. release schedule) then the break 
will be kept on the following Monday.
Email notification will be sent from every upcoming maintenance break.





Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Toni Saario as approver

[Heikki Halmet]

Hi all,

I'd like to nominate Toni Saario as approver for the Qt Project.

Toni has been working in the CI team as a Coin SW developer since he joined the 
Qt Company over one year ago. First as a trainee and starting from last august 
as a full-time employee. Toni has been focusing mainly to improve and maintain 
Coin SW. I'll trust that he will use the approver rights responsibly and follow 
the Qt guidelines.

Here is the list of his changes:
https://codereview.qt-project.org/q/owner:toni.saario%2540qt.io,175



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Infra problems - CI is up and running

[Heikki Halmet]

Hi,

CI is now up and running again. During the weekend there was update done to our 
compellent which apparently caused these problems. CI team don't have all the 
details yet or the root cause   why our servers went down. We are still waiting 
for the answers. Hopefully we can avoid these problems in the future.

Thanks for your patience!


Br
Heikki

From: Heikki Halmet
Sent: Saturday, February 29, 2020 7:41 PM
To: development@qt-project.org; Qt Development 
Subject: Infra problems - CI is down

Hi,

We have problems with our infra and for that reason our CI is currently down. 
Unfortunately no estimation yet when we have system up and running again.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Infra problems - CI is down

[Heikki Halmet]

Hi,

We have problems with our infra and for that reason our CI is currently down. 
Unfortunately no estimation yet when we have system up and running again.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] When next Coin update can be expected?

[Heikki Halmet]

Hi,

We don't know the exact date yet. It depends when we get fixes for 
https://bugreports.qt.io/browse/QTBUG-79623 or we need to make some kind of 
workaround for the patches we have in master branch. 

If those patches are urgent then I think we can take those in as hotfixes if 
production update keeps pending too long.


Br
Heikki


-Original Message-
From: Development  On Behalf Of Konstantin 
Tokarev
Sent: perjantai 1. marraskuuta 2019 14.26
To: development@qt-project.org
Subject: Re: [Development] When next Coin update can be expected?



29.10.2019, 13:29, "Konstantin Tokarev" :
> In particular, I'm interested in fixes for COIN-412 and COIN-421

Ping

-- 
Regards,
Konstantin

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CI problem

[Heikki Halmet]

Hi,

CI is working again. We had some issues with database, but those are fixed now.

Thanks for your patience!


Br
Heikki

From: Heikki Halmet
Sent: tiistai 15. lokakuuta 2019 17.02
To: development@qt-project.org
Subject: CI problem

Hi,

We have problems in CI. Integrations don't get VM's for some reason. Hopefully 
we'll solve this out soon as possible.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI problem

[Heikki Halmet]

Hi,

We have problems in CI. Integrations don't get VM's for some reason. Hopefully 
we'll solve this out soon as possible.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Gerrit update

[Heikki Halmet]

Hi,

Coin fixed and integrations should be work now. 
Thanks for your patience!


Br
Heikki

-Original Message-
From: Development  On Behalf Of Heikki 
Halmet
Sent: maanantai 30. syyskuuta 2019 9.20
To: Jukka Jokiniva ; Qt Project Development Mailing-List 

Subject: Re: [Development] Gerrit update - problem with integrations

Hi,

We have problem in Coin with the newer Gerrit version. It means that currently 
integrations won't work. We are fixing the issue with highest priority.


Br
Heikki

-Original Message-
From: Development  On Behalf Of Jukka 
Jokiniva
Sent: maanantai 30. syyskuuta 2019 8.52
To: Qt Project Development Mailing-List 
Subject: [Development] Gerrit is back online


Gerrit is back online,

Main changes to the functionality are:
   * Confirmation dialog for Stage button has been removed.
   * Each staging attempt doesn't not generate new patch set for the change. 
New patch set is added only after successful integration.

 --Jukka



On 30/09/2019, 7.57, "Development on behalf of Jukka Jokiniva" 
 wrote:


Hi,

Gerrit 3.0.2 upgrade starts in 5 minutes. The codereview.qt-project.org 
will be offline for about  20 - 30 mins.

--Jukka



On 23/09/2019, 16.50, "Development on behalf of Frederik Gladhorn" 
 wrote:

Hi all,

I hope this is a complete no-event, but we'd like to give you a 
heads-up, in 
case something unexpected comes up. We Gerrit admins are currently 
working 
towards moving us to Gerrit 3.0.2.

The plan is to upgrade on Monday next week, the 30th of September.
There are no huge improvements in Gerrit itself, it's a cleanup release 
mostly, getting rid of the old database handling moving completely to 
note-db.

We don't expect major issues, the testserver upgrade takes around five 
minutes, 
so there will be a short down-time, but otherwise there shouldn't be 
any real 
interruptions.
We'll be testing in the meantime and may still postpone the upgrade, in 
case 
any blockers are found.

Cheers,
Frederik



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Gerrit update - problem with integrations

[Heikki Halmet]

Hi,

We have problem in Coin with the newer Gerrit version. It means that currently 
integrations won't work. We are fixing the issue with highest priority.


Br
Heikki

-Original Message-
From: Development  On Behalf Of Jukka 
Jokiniva
Sent: maanantai 30. syyskuuta 2019 8.52
To: Qt Project Development Mailing-List 
Subject: [Development] Gerrit is back online


Gerrit is back online,

Main changes to the functionality are:
   * Confirmation dialog for Stage button has been removed.
   * Each staging attempt doesn't not generate new patch set for the change. 
New patch set is added only after successful integration.

 --Jukka



On 30/09/2019, 7.57, "Development on behalf of Jukka Jokiniva" 
 wrote:


Hi,

Gerrit 3.0.2 upgrade starts in 5 minutes. The codereview.qt-project.org 
will be offline for about  20 - 30 mins.

--Jukka



On 23/09/2019, 16.50, "Development on behalf of Frederik Gladhorn" 
 wrote:

Hi all,

I hope this is a complete no-event, but we'd like to give you a 
heads-up, in 
case something unexpected comes up. We Gerrit admins are currently 
working 
towards moving us to Gerrit 3.0.2.

The plan is to upgrade on Monday next week, the 30th of September.
There are no huge improvements in Gerrit itself, it's a cleanup release 
mostly, getting rid of the old database handling moving completely to 
note-db.

We don't expect major issues, the testserver upgrade takes around five 
minutes, 
so there will be a short down-time, but otherwise there shouldn't be 
any real 
interruptions.
We'll be testing in the meantime and may still postpone the upgrade, in 
case 
any blockers are found.

Cheers,
Frederik



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] INTEGRITY

[Heikki Halmet]

Hi,

Aapo is on sick leave today.

<< There is a flag in Coin to build tests are module build time instead of 
before testing. Perhaps that can somehow be combined with the DisableTests 
feature flag in Coin. Aapo, do << you think that would be possible?
Yes, this one is already done and merged: 
https://bugreports.qt.io/browse/COIN-174 (Create test binaries as a part of 
building phase)
We still need to fix this one https://bugreports.qt.io/browse/COIN-381 (Out of 
source builds are broken), which is currently under work.


Br
Heikki


From: Development  On Behalf Of Simon 
Hausmann
Sent: torstai 19. syyskuuta 2019 10.15
To: development@qt-project.org; Giuseppe D'Angelo 
Subject: Re: [Development] INTEGRITY

Hi,

Unfortunately that will not work out of the box :-(. The tests are only 
compiled when runinng tests. It is not feasible to run tests on Integrity for 
every qtbase integration.


There is a flag in Coin to build tests are module build time instead of before 
testing. Perhaps that can somehow be combined with the DisableTests feature 
flag in Coin. Aapo, do you think that would be possible?

That said, while I've seen this type of failure before (change went into qtbase 
that affected only static builds and only visible at link time), it happens - 
in my experience - perhaps twice a year and it _does_ get noticed fairly 
quickly after all. So I'm not sure if it's worth a hack in the CI system.


Simon

From: Development 
mailto:development-boun...@qt-project.org>> 
on behalf of Giuseppe D'Angelo via Development 
mailto:development@qt-project.org>>
Sent: Wednesday, September 18, 2019 14:00
To: development@qt-project.org 
mailto:development@qt-project.org>>
Subject: Re: [Development] INTEGRITY

Il 18/09/19 13:52, Simon Hausmann ha scritto:
> Since the problem seems urgent to you, do you have any suggestion what
> kind of target built binary you'd add to qtbase's build coverage that
> includes linkage?


Random suggestion: build (if not even *run*) the autotests?

My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com 
| Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Network problems in Finland - CI is down

[Heikki Halmet]

Great work Tony and IT!



From: Tony Sarajärvi 
Sent: tiistai 27. elokuuta 2019 22.33
To: development@qt-project.org
Subject: RE: Network problems in Finland - CI is down

The CI is coming back up. I’m surprised if it works though. I most likely 
forgot to fix or start some service 
Not all infra services are back up and running, but the critical ones should be 
if we remembered them correctly.
Work continues in the morning.

Good luck!
-Tony

From: Tony Sarajärvi
Sent: tiistai 27. elokuuta 2019 19.02
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: RE: Network problems in Finland - CI is down

Hi

IT found out the root cause for our problems. Unfortunately our entire infra 
practically went down along with locking the hard drives our infra machines 
use. The problem that caused all is fixed, but getting everything up and 
running again takes time. We have dozens of servers that are locked that need 
to be fixed. We have people working on it all evening now, and hopefully we get 
things working by tomorrow morning. Local time is now 19:00.

Cheers,
-Tony

From: Development 
mailto:development-boun...@qt-project.org>> 
On Behalf Of Heikki Halmet
Sent: tiistai 27. elokuuta 2019 15.12
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] Network problems in Finland - CI is down

Hi,

We are having network problems in Finland, which affecting to our CI. People 
are working on this with high priority.



Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Network problems in Finland - CI is down

[Heikki Halmet]

Hi,

We are having network problems in Finland, which affecting to our CI. People 
are working on this with high priority.



Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CI is in maintenance break

[Heikki Halmet]

Hi,

CI is up and running again.


Br
Heikki

From: Heikki Halmet
Sent: maanantai 19. elokuuta 2019 8.43
To: development@qt-project.org; Qt Development 
Subject: CI is in maintenance break

Hi,

CI is in maintenance break and will be down approximately 1 hour. We are 
redeploying our hosts.



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI is in maintenance break

[Heikki Halmet]

Hi,

CI is in maintenance break and will be down approximately 1 hour. We are 
redeploying our hosts.



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI is back online

[Heikki Halmet]

Hi,

We had some issues in Gerrit during this weekend. Gerrit started to sent extra 
emails on merge builds during Friday evening. That's why CI was shut down on 
Friday evening.

Now issues are fixed and CI is back online.




Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CI is down

[Heikki Halmet]

Hi,

As you may have noticed CI has been up and running again for a while now. We 
had some dhcp problems which are solved now.


Br
Heikki

From: Heikki Halmet
Sent: sunnuntai 19. toukokuuta 2019 21.25
To: Qt Development ; development@qt-project.org
Subject: CI is down

Hi,

CI environment is currently broken. We don't know exact problem yet. Hopefully 
we have more answers tomorrow.



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI is down

[Heikki Halmet]

Hi,

CI environment is currently broken. We don't know exact problem yet. Hopefully 
we have more answers tomorrow.



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CI is down - HW problems

[Heikki Halmet]

Hi,

CI is up and running again. Sorry about the downtime.



Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu



From: Heikki Halmet 
Sent: keskiviikko 15. toukokuuta 2019 8.44
To: Qt Development ; development@qt-project.org
Subject: CI is down - HW problems

Hi,

CI environment has been broke during last night. We seems to have some problems 
with our HW.

We are currently fixing the issue with IT.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI is down - HW problems

[Heikki Halmet]

Hi,

CI environment has been broke during last night. We seems to have some problems 
with our HW.

We are currently fixing the issue with IT.


Ystävällisin terveisin / Kind regards,

Heikki Halmet
Software Engineer | CI Lead
Release and Test Automation | CI Team
The Qt Company | Finland | Oulu


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Maintenance break this morning

[Heikki Halmet]

Hi,

Apparently there hasn't been any email notification about maintenance break 
made by IT this morning. Sorry about that.
Our whole network was down so nothing has been working for a while. Everything 
should be back online now, but we are still checking if there's something that 
didn't come back online.


Br
Heikki
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] CI and firewall

[Heikki Halmet]

Hi,

IT has been reconfigured our network and firewall settings today. Because of it 
CI hasn't been available or there has been unstable functionality with it.
All issues should be solved now and CI should work normally.


Br
Heikki Halmet


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Short CI status

[Heikki Halmet]

Hi,

As you may have noticed we still have several issues in our CI system which 
needs fixes.
Below is the frontline of CI teams battlefield:


  *   Windows 10 machines are freezing time to time and the logging suddenly 
stops.
 *   https://bugreports.qt.io/browse/QTQAINFRA-2253
*   We are trying to fix this by upgrading Hosts kernel version. 
Correction is almost there but we got some unexpected problems during the test. 
Hopefully we'll get back on the track soon.
*   You can follow the process from here: 
https://bugreports.qt.io/browse/QTQAINFRA-2299
  *   Lots of Configure/Qmake timeouts during builds
 *   https://bugreports.qt.io/browse/QTQAINFRA-2051
 *   https://bugreports.qt.io/browse/QTQAINFRA-2052
 *   We assume that kernel update will help with this one.
  *   When cancelling e.g. Qt5 build COIN scheduler goes stuck for a long time
 *   https://bugreports.qt.io/browse/QTQAINFRA-2257
 *   We are currently making change(s) to fix this.
  *   Windows VM randomly freezes and need user input before able to continue 
building
 *   https://bugreports.qt.io/browse/QTQAINFRA-2263
 *   We have fix for this which we hope to resolve this issue - 
https://codereview.qt-project.org/#/c/242149/
  *   In packaging site macos 10.13 keeps on disconnecting from Jenkins
 *   https://bugreports.qt.io/browse/QTQAINFRA-2310
 *   We have two plan for this
*   A. Changing Jenkins-pkg to use Coin's virtual machines. Work on 
going.
*   B. Upgrade Host's hypervisor (This is a long shot and we hope that 
plan A will resolve this)

We feel your pain and frustration. We are working hard to have more stable CI 
and hopefully soon we'll have most of these problems resolved.


Br
Heikki Halmet
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Note! CI will maintenance

[Heikki Halmet]

Hi,

Because of problems with build machines in CI we are recreating our HOSTs. This 
means that there won't be any build machines available for one hour.
After that first hosts should be available. However it will take whole day 
before we get full capacity available for CI.

Br
Heikki Halmet

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Problems in CI

[Heikki Halmet]

Hi,

You may have noticed that CI is having problems to get build machines and 
builds seems to be in stuck. This is because machines aren't booting up at all 
or the booting time is very slow.

CI team is investigating the problem



Br
Heikki Halmet

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Coin maintenance notification

[Heikki Halmet]

Coin production was updated today at Mon Aug 6 13:27:20 EEST 2018 with new 
baseline.

For CI related issues, you may create bug report as instructed in 
https://wiki.qt.io/Reporting_Bugs#Reporting_bugs_for_Coin and/or consult the 
internal #qtci IRC-channel.

See change-list attached for related patches.


Kind regards
Heikki Halmet



product_baseline_20180808.log
Description: product_baseline_20180808.log
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Proposal for Qt 5.10 platforms and configurations changes - SUMMARY

[Heikki Halmet]

Hi,

First of all thank you for all these comments!


There was few changes to the ‘proposal changes list’ and here is the summary:

32-bit iOS: will be dropped from CI and will be no longer supported by Qt
OSX 10.10: will be dropped from CI, but will be supported by Qt
GCC 7: When released it will be tested with some linux distro in CI
Clang 4: Do we really need this to be tested with Linux in CI? If yes, then 
which configuration it will be replaced?



Br
Heikki Halmet






-Original Message-
From: Development 
[mailto:development-bounces+heikki.halmet=qt...@qt-project.org] On Behalf Of 
Tuukka Turunen
Sent: 2. toukokuuta 2017 10:23
To: Jake Petroules <jake.petrou...@qt.io>; Lars Knoll <lars.kn...@qt.io>
Cc: Qt development mailing list <development@qt-project.org>
Subject: Re: [Development] Proposal for Qt 5.10 platforms and configurations 
changes


Hi,

While I do agree that having a platform in CI and supporting it for those who 
have purchased support are not 1:1, in case of dropping the 32-bit iOS from CI 
for Qt 5.10 it also means that this configuration should no longer be used and 
not be supported. I do not see much problems with that as we continue to 
support 32 bit iOS for earlier platforms (until Apple drops it) and the 32 bit 
iOS devices are already quite old.

Yours,

Tuukka


On 28/04/2017, 19.58, "Jake Petroules" <jake.petrou...@qt.io> wrote:


> On Apr 27, 2017, at 11:28 PM, Lars Knoll <lars.kn...@qt.io> wrote:
> 
> 
>> On 27 Apr 2017, at 16:59, Jake Petroules <jake.petrou...@qt.io> wrote:
>> 
>>> 
>>> On Apr 27, 2017, at 7:07 AM, Tuukka Turunen <tuukka.turu...@qt.io> 
wrote:
>>> 
>>> 
>>> Hi,
>>> 
>>> Related to the Apple platforms, could we consider the following for Qt 
5.10:
>>> - Drop the older iPhone support by removing ARMv7 from iOS 
(http://dorianroy.com/blog/wp-content/uploads/2016/09/iOS_Support_Matrix_v4.2.pdf)
>>> - Consider also dropping ARMv7s support, which would allow dropping 
i386 simulator support
>> 
>> I really don't like how we use the term "support" in these emails 
because it's rather misleading. We use it to mean "tested in CI", whereas I 
(and most of the world, as far as I can tell) read it as "the code exists and 
is functional". "Removing support" to me means actively removing the code which 
makes something functional.
> 
> Agree, there is a difference between the two. 
> 
> What I think we should however do for 5.10 is remove 32bit support for 
iOS from CI and our binary packages. And that means that things will be 
untested on 32bit iOS, and thus is likely to break at some point.

I think 32-bit support on iOS is kind of unlikely to break accidentally, 
but I agree we should remove it from our binary packages. The iPhone 5 is dead.

>> 
>> As an Open Source project, we need to keep in mind that dropping first 
party "support" for something means little to nothing unless we actually delete 
the associated code as well and refuse patches to re-add it, because people can 
always build their own copy of Qt, and commercial support will obviously still 
answer queries for most definitions of "unsupported", making the term 
"unsupported" a little meaningless. Perhaps we can start using the term "tier 1 
support" as a synonym for what we actually mean by "support", in order to be 
more clear? I really liked the notion of tiered support that we used to have 
but it seems to have gone missing…
> 
> For the commercial version, it’s to a large extent up to TQtC to define 
the support offering. The open source project anyway does not offer any 
official support for the Qt versions released. All you can do is ask on the 
mailing lists or file a bug report and hope for the best. Or of course sit 
down, fix it yourself and submit a patch :)

My point was that if a commercial customer goes to support with a bug in a 
32-bit build of Qt for iOS, support won't say "we do not support that, go 
away". They will fix the problem, regardless of the fact that it isn't part of 
a reference configuration.

If a customer sets the minimum deployment target of Qt for iOS to 5.0 and 
then goes to support saying Qt doesn't work, support WILL tell them "we do not 
support that (because we deliberately broke it), we can't help you and you'll 
have to talk to Services and pay money if you want it working that badly".

That's the real-world outcome, which is why I don't like using the term 
"supported" as a synonym for "is a reference configuration in CI".

A reference configuration in CI always constitute

[Development] Proposal for Qt 5.10 platforms and configurations changes

[Heikki Halmet]

Hi,



Below we have proposal for changes in supported platforms and configurations 
from Qt 5.9 to 5.10.

Please comment if the proposal is insufficient or the changes are unacceptable 
somehow.



Please refer to Qt 5.9 Supported platforms -> 
http://doc-snapshots.qt.io/qt5-5.9/supported-platforms.html



LIST OF PROPOSAL CHANGES FROM 5.9 TO 5.10:

RHEL 7.2 -> RHEL 7.3 (Any benefits?)

OpenSUSE 42.1 -> OpenSUSE 42.2

Ubuntu 17.04 (Ubuntu 16.04 lts will stay in CI)

macOS 10.11 xcode 8.2 -> xcode 8.2.1 (or the latest available)

macOS 10.12 xcode 8.2.1 -> xcode 8.3.1 (or the latest available)

Windows 7 MinGW 5.3.0 -> MinGW 6.3.0

Embedded Linux (Boot2Qt) Yocto 2.2.1 & gcc 6.2 -> Yocto 2.3 & gcc 6.3

INTEGRITY GHS 2016.5.4 -> 2017.1.x

Support for Android 8 (if available on time)

iOS 11 support (if available on time. Current rumors -> september)



MacOS 10.13 will be released September 2017 hopefully. Feature Freeze for 5.10 
is at the beginning of August.

This means that we can only use Preview release of 10.13 for testing before 
final official release is out.

That can cause situation that we don't have enough time to get 10.13 in before 
5.10 release so we can't give guarantees that 10.13 will be supported in 5.10.



NOTE! We will commit to wanted platform and software changes as long as those 
are available straight after 5.9 release is out in the end of the May.
With all others we'll do the best we can but we can't commit that those will be 
supported in 5.10.



Best regards
Heikki Halmet

The Qt Company, Elektroniikkatie 13, 90590 Oulu, Finland
Email: heikki.hal...@qt.io
Phone: +358408672112
www.qt.io<http://www.qt.io/> | Qt Blog: http://blog.qt.io/ | Twitter: 
@qtproject, @Qtproject Facebook: www.facebook.com/qt<http://www.facebook.com/qt>

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] RHEL 7.2 added to Coin

[Heikki Halmet]

>>Is there any other config running tests with a gtk3 plugin? 
I don't think so

>>What desktop environment is that RH 7.2 using?
gnome-classic

- Heikki
-Original Message-
From: Development 
[mailto:development-bounces+heikki.halmet=qt...@qt-project.org] On Behalf Of 
Thiago Macieira
Sent: 28. kesäkuuta 2016 17:49
To: development@qt-project.org
Subject: Re: [Development] RHEL 7.2 added to Coin

On terça-feira, 28 de junho de 2016 07:58:29 PDT Liang Qi wrote:
> Could we disable RHEL 7.2? at least for QtScript. There is a failure 
> in qt5.git dev integration. It is the only blocker for it now.
> 
> 
> https://codereview.qt-project.org/162195

Is there any other config running tests with a gtk3 plugin? What desktop 
environment is that RH 7.2 using?

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Proposal For Qt 5.8 Platforms And SW Updates

[Heikki Halmet]

Hi,

Below is our proposal for target platforms and sw updates in Qt 5.8 release.
Some might come after feature freeze or some changes might not happen at all.

OpenSUSE 42.1 x86_64 ( - OpenSUSE 13.1 will be dropped after 42.1 is in)
* Openssl: 1.0.2h
Rhel 6.6 (build's packages) & Rhel 7.2 x86_64 (will appear as a developer build)
* Openssl: 1.0.2h
* Android ndk r10e
* Android sdk 25.1.7
* Python-devel (or python-dev)
Ubuntu 16.04 x86_64 ( - Will drop Ubuntu 14.04 and 15.04 when it's in)
* Openssl: 1.0.2h
* Python-devel (or python-dev)
OS X 10.12 beta
* Xcode 8 beta & command line tools
* Android ndk r10e
* Android sdk 25.1.7
OS X 10.11.5 x86_64
* Xcode 7.3.1 & command line tools
* Android ndk r10e
* Android sdk 25.1.7
OS X 10.10 x86_64
OS X 10.9 x86_64
OSX 10.8 will be dropped!
Windows 10 x86
* Openssl: 1.0.2h
* Visual Studio 2015 update 2
Windows 10 x86_64
* Openssl: 1.0.2h
* Visual Studio 2015 update 2
Windows 7 x86
* Openssl: 1.0.2h
* Android ndk r10e
* Android sdk 25.1.7
* MinGw 5.3.0
Windows 8.1 x86
* Openssl: 1.0.2h
* Visual Studio 2013 update 5
Windows 8.1 x86_64
* Openssl: 1.0.2h (latest)
* Visual Studio 2013 update 5


Best regards
Heikki Halmet

The Qt Company, Elektroniikkatie 13, 90590 Oulu, Finland
Email: heikki.hal...@qt.io
Phone: +358408672112
www.qt.io<http://www.qt.io/> | Qt Blog: http://blog.qt.io/ | Twitter: 
@qtproject, @Qtproject Facebook: www.facebook.com/qt<http://www.facebook.com/qt>


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development