Appveyor Status

Everything about development and the OpenMW source code.
Post Reply
User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Appveyor Status

Post by Zini »

We are getting random failed builds from appveyor for quite a while now. At this point appveyor is basically useless. I am currently ignoring it, because there are just too many false positives. IMHO it would be better to remove appveyor if we can't get this fixed.
User avatar
psi29a
Posts: 5355
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Appveyor Status

Post by psi29a »

I've been ignoring it for awhile. Almost all of the failures stems from msvc2015 and the logging thingy.... can you confirm that Zini? It's the reason why I ask to disable msvc2015 builds, but ace wanted to keep the last 2 versions of msvc building...

Is there a way to 'allow failures' on appveyor like we do with clang builds on travis?
User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Re: Appveyor Status

Post by Zini »

can you confirm that Zini?
No idea. As I said I don't even look at that stuff anymore.
User avatar
psi29a
Posts: 5355
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Appveyor Status

Post by psi29a »

Going to give it a try here:
https://github.com/OpenMW/openmw/pull/1855
User avatar
psi29a
Posts: 5355
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Appveyor Status

Post by psi29a »

msvc2015 failed as expected, but since we now allow it to fail... so long as msvc2017 succeeds, we're good to go.

We're green, so I merged the branch. Appveyor should be less chatty now for you Zini, good to go?
User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Re: Appveyor Status

Post by Zini »

Sounds reasonable.

Thanks.
Post Reply