Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qt 5.3 msvc2013 opengl release buid failures on AppVeyor #61

Closed
pcolby opened this issue Dec 7, 2015 · 2 comments
Closed

Qt 5.3 msvc2013 opengl release buid failures on AppVeyor #61

pcolby opened this issue Dec 7, 2015 · 2 comments

Comments

@pcolby
Copy link
Owner

pcolby commented Dec 7, 2015

This is presumed to be a bug specific to that (unsupported) environment, so allowed to fail for now. Just creating an issue to allow it to be tracked by anyone that might be interested (which I don't expect will be anyone).

pcolby added a commit that referenced this issue Dec 7, 2015
This specific corner combination is currently experiencing a fatal
error when executing unit tests.  This is presumed to be a bug
specific to that (unsupported) environment, so allowedd to fail for
now (issue #61).
@pcolby pcolby changed the title 5.3\msvc2013_opengl Qt 5.3 msvc2013 opengl release buid failures on AppVeyor Dec 7, 2015
@pcolby pcolby closed this as completed Dec 7, 2015
@Squirell1
Copy link

Hi Paul,
thank you for the explanation on githib.
I'll test the hook latest by tomorrow because it's my wifes birthday today.
I'll give you feedback after the test.
(We are around 12 hours behind )
Cheers Thomas

Am 7. Dezember 2015 23:10:14 MEZ, schrieb Paul Colby [email protected]:

Closed #61.


Reply to this email directly or view it on GitHub:
#61 (comment)

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

@pcolby
Copy link
Owner Author

pcolby commented Dec 8, 2015

Thanks @Squirell1 😄 (For anyone following along, @Squirell1's response was to issue #60).

pcolby added a commit that referenced this issue Dec 8, 2015
The previous commit (9ee8e0e)
accidentally allowed the wrong (64-bit) build to fail, whereas this
change allows the 32-bit build to fail instead (issue #61).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants