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.

Sign up for GitHub

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

Jump to bottom

AppVeyor spuriously killing a dist- job with message "Build exceeded allowed resource quotas" #58025

Closed
pnkfelix opened this issue Jan 31, 2019 · 4 comments
Closed

AppVeyor spuriously killing a dist- job with message "Build exceeded allowed resource quotas" #58025

pnkfelix opened this issue Jan 31, 2019 · 4 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@pnkfelix
Copy link
Member

pnkfelix commented Jan 31, 2019 •
edited by kennytm
Loading

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.
@pnkfelix pnkfelix added the T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. label Jan 31, 2019
@mati865
Copy link
Contributor

mati865 commented Jan 31, 2019 •
edited
Loading

#57514 passed after retry.

When comparing logs:

Both get to the point:

Successful compile (288.031 sec). Resulting Setup program filename is:
C:\projects\rust\build\tmp\dist\exe\rust-nightly-x86_64-pc-windows-gnu.exe
rust.wxs
ui.wxs
rustwelcomedlg.wxs
RustcGroup.wxs
DocsGroup.wxs
CargoGroup.wxs
StdGroup.wxs
ClippyGroup.wxs
MiriGroup.wxs
AnalysisGroup.wxs
GccGroup.wxs

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:

Somehow build succeed but AppVeyor detected it as a fail:

Builds seems to freeze.

@kennytm kennytm mentioned this issue Feb 6, 2019
Merged
@kennytm kennytm added A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC labels Feb 6, 2019
@kennytm kennytm changed the title CI: Appveyor misclassifying tool failures on successful builds as build errors AppVeyor spuriously killing a dist- job with message "Build exceeded allowed resource quotas" Feb 7, 2019
@kennytm
Copy link
Member

kennytm commented Feb 7, 2019 •
edited
Loading

I've replaced the issue description and title with the actual problem.

@mati865 mati865 mentioned this issue Feb 11, 2019
Merged
@pietroalbini
Copy link
Member

Contacted AppVeyor support about this.

@pietroalbini
Copy link
Member

According to AppVeyor support the problem was disk space, and they increased our quota by 10Gb. Closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kennytm @pnkfelix @mati865 @pietroalbini