Appveyor Status
Appveyor Status
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.
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Appveyor Status
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?
Is there a way to 'allow failures' on appveyor like we do with clang builds on travis?
Re: Appveyor Status
No idea. As I said I don't even look at that stuff anymore.can you confirm that Zini?
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Appveyor Status
Going to give it a try here:
https://github.com/OpenMW/openmw/pull/1855
https://github.com/OpenMW/openmw/pull/1855
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Appveyor Status
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?
We're green, so I merged the branch. Appveyor should be less chatty now for you Zini, good to go?