5.11.0 is fine. Latest one is successful, 
https://testresults.qt.io/coin/integration/qt/qt5/tasks/1525572833

But looks like there are issues in qt5 dev integration, please check 
https://codereview.qt-project.org/#/c/227670/  and 
https://testresults.qt.io/coin/integration/qt/qt5/tasks/1525573813 .

My proposal is switch qtdeclarative back to 
913dc3f4f2be7c2c23237bcb9bffb3192cb10d60 . The new patch set PS5 is pushed 
there, and have a background build(status check) running, looks good by now.

— Liang

> On 27 Apr 2018, at 12:28, Tuukka Turunen <[email protected]> wrote:
> 
>  
> Hi,
>  
> So we should probably restart https://codereview.qt-project.org/#/c/227410/ 
> and re-run other qt5.git runs to make sure all tests are properly run in 
> those?
>  
> Yours,
>  
>                 Tuukka
>  
> From: Development <[email protected]> 
> on behalf of Sami Nurmenniemi <[email protected]>
> Date: Friday, 27 April 2018 at 13.06
> To: Simon Hausmann <[email protected]>, "[email protected]" 
> <[email protected]>
> Cc: Qt CI <[email protected]>
> Subject: Re: [Development] CI "wave-through"
>  
> Hi,
> 
>  
> 
> Increasing the "non-zero change" there a bit, the "wave-through window" was 
> from "25th of April 15:30 CET" to "27th of April 12:00 CET".
> 
>  
> 
> Best Regards,
> 
> Sami
> 
> Lähettäjä: Development 
> <[email protected]> käyttäjän Simon 
> Hausmann <[email protected]> puolesta
> Lähetetty: 27. huhtikuuta 2018 12:54:11
> Vastaanottaja: [email protected]
> Kopio: Qt CI
> Aihe: [Development] CI "wave-through"
>  
> Hi,
> 
>  
> 
> Since yesterday afternoon around 15:30 central european time the CI has 
> experienced a "failure" that resulted in each and all tests being skipped. So 
> if a change broke the build, the CI would reject it. But if the change would 
> normally result in a test failing, then the CI waved the change through 
> regardless as it did not run any tests at all (apart from the BIC tests).
> 
>  
> 
> The issue has been corrected as of a few minutes ago, but there is a non-zero 
> chance that faulty changes may have slipped through and may result in test 
> failures that are not related to changes you're trying to integrate.
> 
>  
> 
>  
> 
> Simon
> 
> _______________________________________________
> Development mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/development

_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to