feedback on most useful CI and the most useful tests to run

[podhrmic]

Please provide your feedback on how to structure the CloudGFE CI so it suits your requirements.

Here is a smoketest structure (this is a rough outline what we have right now):

• you push changes into your repo containing CloudGFE HW design on github
• the repo will be mirrored in gitlab-ext in ~30min (that is the current interval)
• after the new commit is detected in gitlab-ext our CI will spin up a docker container and starts building new bitstream to reflect the changes in the HW design
• after the new bitstream is finished, it is converted into an AFI
• after the AFI is built, FETT-target is used to spin up a F1 instance, load AFI, AMI, and run ISA tests
• after the ISA tests finish, a log file and exit code is obtained, then the F1 instance is shut down
• you can review the results in gitlab-ext pipeline

Some additional questions to think about:

• what tests beyond ISA tests should be performed? (FreeRTOS,FreeBSD, Debian...?)
• do you prefer building the bitstream/AFI manually, or should this be a part of the CI?

[charlie-bluespec]

@kiniry, this question from @rsnikhil @dhand-galois and @joestoy came up in today's standup meeting: Is a specifc AMI required for FETT, or can Connectal, Firesim and AWSteria use different AMIs?

[kiniry]

They can and will use different AMIs.

[kurthopfer]

@kiniry speaking of AMIs when can we expect a couple of AMIs/AFIs that we can use on the cloud CI front? I expect we will become blocked sometime middle of next week without these bits.

[dhand-galois]

A FireSim-based P2 build should be available later today (if all goes well with reproducing my setup on a fresh instance).

[kurthopfer]

Great, sounds good - doesn't need to be fully fleshed out by any means. just something that is close enough so we can dial in CI.

[kiniry]

Where do we sit wrt tests that are integrated into the AWS CI? As I understand it, the AWS CI is not yet fully spun up?

[podhrmic]

I think the FETT-target tests are up and running - instead of running CI in each individual repository, we run integration tests only in FETT-target as that makes CI management much easier. @rtadros-Galois or @jared-w can provide more color.

[rtadros125]

@kiniry AWS CI is down.