-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)Area: Spurious failures in builds (spuriously == for no apparent reason)C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.
Description
Symptom: A job on AppVeyor (currently all are dist-x86_64-mingw
) is killed while creating the setup EXE, with the AppVeyor message
Build exceeded allowed resource quotas. Fix your build to consume less resources or contact AppVeyor support to request quotas increase.
We guess the quota mentioned is the disk space.
#57514 (comment) (2019-01-30T21:04:02Z) is the first known instance. This error is occurring once to twice per day.
Metadata
Metadata
Assignees
Labels
A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)Area: Spurious failures in builds (spuriously == for no apparent reason)C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
mati865 commentedon Jan 31, 2019
#57514 passed after retry.
When comparing logs:
Both get to the point:
Then failed job output stops (process hangs?) while successful job prints warnings for
.wsx
objects and finishes the build.EDIT: Also taking back my words:
Builds seems to freeze.
[-]CI: Appveyor misclassifying tool failures on successful builds as build errors[/-][+]AppVeyor spuriously killing a dist- job with message "Build exceeded allowed resource quotas"[/+]kennytm commentedon Feb 7, 2019
I've replaced the issue description and title with the actual problem.
pietroalbini commentedon Feb 19, 2019
Contacted AppVeyor support about this.
pietroalbini commentedon Feb 20, 2019
According to AppVeyor support the problem was disk space, and they increased our quota by 10Gb. Closing this.