WIP: Rebuild CI/CD, F2 & local FireSim bitstream autobuild, general infra

[jimfangx]

WIP - drafting so no one accidentally does duplicate work;

features:

• bring back docker containers; now set to build nightly, used for testing
  • working here: https://github.com/jimfangx/chipyard-working/pkgs/container/chipyard-working
• bring back CI/CD -- baremetal tests for each generator + firesim through golden gate compiler + verilator sim on transformed rtl + build-setup on rhel & ubuntu x86 machines (arm coming soon, see below)
  • working here: Copilot/re run generator tests job jimfangx/chipyard-working#8
  • all generator ci complete in ~30mins, firesim tests are 60-90 mins
• move prebuilt firesim bitstreams to cloudflare R2 instead of github (trialing)
  • github repos have a 10gb limit that includes histories (.git <= 10gb), this will eventually fill up and is not sustainable under a bitstream autobuild structure
  • example: https://bitstreams.ucb.bar/xilinx_alveo_u250/alveo_u250_firesim_boom_singlecore_no_nic.tar.gz
• automated building of f2 and local (currently u250 & vcu118) bitstreams
  • working for local, see /tools/C/chipyard-cicd on bwrc machines

planned:

• ci/cd testing docs build (should be easy)
• some fast CI based on changes PRed and limited test suite, aiming for <= 10 min runs.
• linux arm support for chipyard (will be tested on Ampere A1 machines) [in progress]
• A/B testing/impact monitoring for bumping riscv-tools/toolchain [in progress]
• chisel 7 support A/B testing/impact monitoring
• some sort of dashboard showing up to date bitstream version, isa support, etc for each of the major CY IPs; once VLSI flow is up this will show PPA as well.
• script for constructing release notes (salvaged from the old script)
• (extra, if deemed to save some time when deploying) some sort of slack bot integration?

cost estimate:

• all ci/cd is free (github actions are free for public repos + education discount of 3000 build mins/month for private repos), github container registry is free for public images, R2 is free (10gb/month forever free tier, no ingress/egress costs)
• aws f2 bitstream builds is estimated to be at worst ~$20-30/month, rebuilding all current AGFIs once/month (m6a.xlarge as the manager instance on demand + m8i.4xlarge spot for build machines)

Component	Formula	Cost
Orchestrator	8 hr * $0.1728/hr	$1.38
10 bitstreams, 1 hr each	10 * 1 hr * $0.368/hr	$3.68
10 bitstreams, 3 hr each	10 * 3 hr * $0.368/hr	$11.04
10 bitstreams, 5 hr each	10 * 5 hr * $0.368/hr	$18.40

(for context: on m8i.4xlarge instances, single core rocket no nic takes ~50 mins to complete)
spot prices in table are average; max spot price is set to 0.5

Related PRs / Issues:

Type of change:

• Bug fix
• New feature
• Other enhancement

Impact:

• RTL change
• Software change (RISC-V software)
• Build system change
• Other

Contributor Checklist:

• Did you set main as the base branch?
• Is this PR's title suitable for inclusion in the changelog and have you added a changelog:<topic> label?
• Did you state the type-of-change/impact?
• Did you delete any extraneous prints/debugging code?
• Did you mark the PR with a changelog: label?
• (If applicable) Did you update the conda .conda-lock.yml file if you updated the conda requirements file?
• (If applicable) Did you add documentation for the feature?
• (If applicable) Did you add a test demonstrating the PR?

• (If applicable) Did you mark the PR as Please Backport?

CI Help:
Add the following labels to modify the CI for a set of features.
Generally, a label added only affect subsequent changes to the PR (i.e. new commits, force pushing, closing/reopening).
See ci:* for full list of labels:

• ci:fpga-deploy - Run FPGA-based E2E testing
• ci:local-fpga-buildbitstream-deploy - Build local FPGA bitstreams for platforms that are released
• ci:disable - Disable CI

[jimfangx]

temp; need to point back

[jimfangx]

why is this removed?

[jimfangx]

remove unless a resolve is absolutely needed