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

Fix Appveyor error with deploying MINGW build #4823

Open
Web-eWorks opened this issue Feb 28, 2020 · 4 comments
Open

Fix Appveyor error with deploying MINGW build #4823

Web-eWorks opened this issue Feb 28, 2020 · 4 comments
Assignees
Labels

Comments

@Web-eWorks
Copy link
Member

@Web-eWorks Web-eWorks commented Feb 28, 2020

@fluffyfreak I'm kicking this one your way because (IIRC) you're the one most knowledgeable about appveyor builds.

Our MINGW appveyor build is throwing a false positive error because it is unable to upload the generated build artifact due to a 500 internal server error response code during the deployment step. We need to figure out what is causing this error and if necessary disable deploying MINGW builds; it's far too easy to miss that a pull request has a serious issue with it when every pull request is showing as failing due to a single AppVeyor build instance running into an issue.

@impaktor

This comment has been minimized.

Copy link
Member

@impaktor impaktor commented Feb 29, 2020

you're the one most knowledgeable about appveyor builds.

I think @pcercuei have helped us a lot with appveyor in the past. Hopefully also in the future/now, 😃 and @fluffyfreak has been the MINGW expert.

I hope I got that right.

@fluffyfreak

This comment has been minimized.

Copy link
Contributor

@fluffyfreak fluffyfreak commented Feb 29, 2020

I think I might be the least knowledgable about Appveyor builds 🤔

@pcercuei

This comment has been minimized.

Copy link
Contributor

@pcercuei pcercuei commented Feb 29, 2020

Same problem as usual: appveyor/ci#2005 (comment)

@fluffyfreak

This comment has been minimized.

Copy link
Contributor

@fluffyfreak fluffyfreak commented Mar 1, 2020

Oh it's that again, we should have a note somewhere to remind me what it is because it comes up so infrequently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.