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

Bug - website build failure #2427

Closed
2 of 6 tasks
favoyang opened this issue Sep 15, 2021 · 2 comments
Closed
2 of 6 tasks

Bug - website build failure #2427

favoyang opened this issue Sep 15, 2021 · 2 comments
Assignees

Comments

@favoyang
Copy link
Member

favoyang commented Sep 15, 2021

Bug report

The website requires more than 7GB of memory to build, which exceeds the GitHub actions machine memory limitation.

The website will be no longer be updated until the issue gets resolved.

New package submissions WILL NOT be available on the OpenUPM website, but WILL still appear on the OpenUPM registry.

Bug category

  • Website: issues related to browse or discover packages.
  • Pipelines: issues related to publish or manage a package.
  • Registry: issues related to the registry server.
  • Unity Editor: issues related to how OpenUPM works with the Unity Editor.
  • Documentation
  • Others

Steps to reproduce

https://github.com/openupm/openupm/runs/3610593661?check_suite_focus=true

[2387:0x4b4ec20]   579661 ms: Mark-sweep (reduce) 7143.9 (7184.3) -> 7142.9 (7185.3) MB, 28939.6 / 0.1 ms  (average mu = 0.044, current mu = 0.001) allocation failure scavenge might not succeed

What is expected?

Build without the memory allocation failure.

What is actually happening?

Memory allocation failure, due to the 7GB memory limitation of GitHub build machine.

Other relevant information

vuejs/vuepress#2689

@favoyang
Copy link
Member Author

Potential solutions

  1. uses macos-latest build image which runs on a Mac VM with 14GB memory - free, but not sure if the build script can run on a macOS.
  2. rents a Linux VM with more memory +$80/mo - not affordable.
  3. uses netlify's high-performance build service with 36GB memory - needs to contact sales, usually not affordable.
  4. hunt memory leaks in the vuepress build process - harder, takes more time.

Will try 1 then 4.

@favoyang
Copy link
Member Author

Resolved by option 1.

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

1 participant