NM, I figured out how to cancel it :P
On 03/15/2018 11:57 AM, Adam Treat wrote:
Speaking of...
https://codereview.qt-project.org/#/c/223224/
That integration is stuck and I don't know how to stop it and restage
it. Apparently, the Windows 7 (mingw53-x86) VM crashed and COIN is not
aware of t
Speaking of...
https://codereview.qt-project.org/#/c/223224/
That integration is stuck and I don't know how to stop it and restage
it. Apparently, the Windows 7 (mingw53-x86) VM crashed and COIN is not
aware of that due to these:
1. https://bugreports.qt.io/browse/QTQAINFRA-1750
2. https://b
I would not regard this as excess spam at all. It is important to know
when the CI is not available and what the status is. If a restart or
scheduled update of any kind requires to restage commits for COIN,
please include that info.
On 03/15/2018 04:26 AM, Tony Sarajärvi wrote:
Hi
We’re try
On 15/03/2018, 10.33, "Development on behalf of Florian Bruhin"
wrote:
Hi,
On Thu, Mar 15, 2018 at 08:26:21AM +, Tony Sarajärvi wrote:
> How does this sound to you recipients of these e-mails? Enough or would
this be excess spam to some degree?
That sounds like
Hi,
On Thu, Mar 15, 2018 at 08:26:21AM +, Tony Sarajärvi wrote:
> How does this sound to you recipients of these e-mails? Enough or would this
> be excess spam to some degree?
That sounds like useful information to me.
However, I'm wondering: Would it be possible to display some kind of
ann
Hi
We're trying to improve our communication toward you regarding our CI and
what's going on with it. So our suggestion comes as follows:
· - In case of a scheduled update, we send an e-mail to the public
developer mailing list the day before
· - In case of emergency update or pur
