You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugSomething isn't workingdesignDevOpsUnify development and operations practices to shorten systems engineering lifecyclesinvalidThis doesn't seem right
From issue 242, I found the cmake command performs dependency builds that:
Leave files outside the build/repo folder, such as ~/.hunter, which impact future builds.
Takes >10 minutes on an enf-x86-beefy runner, which uses an n2d-standard-224 GCP instance type with 224 cores and >768 GB RAM.
Takes >50 minutes on an enf-x86-lowtier runner, which uses an e2-custom-8-16384 instance type.
Takes ~88 minutes on a free GitHub Actions Ubuntu runner.
This is frankly absurd. Are we building Linux from scratch, and then using it to build all dependencies and the operating system? None of our other ENF or AntelopeIO products take more than ~10 seconds to generate make files, none of them install dependencies to the user's system outside of the build or repo folder without consent, none of them perform git clones, and none of them perform make builds. The fact that an n2d-standard-224 could not complete the entire TrustEVM node build within ten minutes suggests there is a fundamental issue with this project architecture.
Acceptance Criteria
The cmake command completes in 60 seconds or less on any and all of these three runners:
enf-x86-beefy using an n2d-standard-224 GCP instance type.
enf-x86-lowtier using an e2-custom-8-16384 instance type.
Free GitHub Actions Ubuntu runner.
The cmake command does not result in files being left outside of the current directory, subdirectories of the current directory, or the git repo directory.
The cmake command does not result in dependencies being installed to the user's system.
The text was updated successfully, but these errors were encountered:
bugSomething isn't workingdesignDevOpsUnify development and operations practices to shorten systems engineering lifecyclesinvalidThis doesn't seem right
From issue 242, I found the
cmake
command performs dependency builds that:~/.hunter
, which impact future builds.enf-x86-beefy
runner, which uses ann2d-standard-224
GCP instance type with 224 cores and >768 GB RAM.enf-x86-lowtier
runner, which uses ane2-custom-8-16384
instance type.This is frankly absurd. Are we building Linux from scratch, and then using it to build all dependencies and the operating system? None of our other ENF or AntelopeIO products take more than ~10 seconds to generate
make
files, none of them install dependencies to the user's system outside of the build or repo folder without consent, none of them performgit
clones, and none of them performmake
builds. The fact that ann2d-standard-224
could not complete the entire TrustEVM node build within ten minutes suggests there is a fundamental issue with this project architecture.Acceptance Criteria
cmake
command completes in 60 seconds or less on any and all of these three runners:enf-x86-beefy
using ann2d-standard-224
GCP instance type.enf-x86-lowtier
using ane2-custom-8-16384
instance type.cmake
command does not result in files being left outside of the current directory, subdirectories of the current directory, or thegit
repo directory.cmake
command does not result in dependencies being installed to the user's system.The text was updated successfully, but these errors were encountered: