lowRISC / lowRISC/opentitan

[ci] investigate moving airgapped build test to GCP runner (instead of azure runner)

Open
#19,512 0 comments 0 reactions 0 assignees View on GitHub
Component:CI Earlgrey-PROD Candidate Good First Issue Type:Bug
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

### Description

The airgapped build test job has run out of space several times on both integrated (see https://github.com/lowRISC/opentitan-integrated/pull/321) and discrete branches. We should investigate how to move this job to a GCP runner. IIRC, it was not as simple as just updating the CI YAML file, as there were issues with instantiating the network namespace it uses in the containerized environment on the GCP runners (but further investigation is required).

Contributor guide

Open the contributing guide

Research direction

Start with the CI YAML for the airgapped build test and inspect how its containerized environment creates the network namespace on GCP runners. Compare the existing Azure runner configuration with GCP runner constraints, then verify that the job runs successfully without exhausting disk space and that the airgapped networking behavior is preserved.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, gcp, github-actions
Domain
ci-cd, cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.