Repository navigation
doc: how the simulated-GPU CI job works - #112
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As you suggested on #110: a page in doc/ that explains simulated-gpu.yml. It covers what the job does, what a green run does and does not tell you, why the first run after a quiet week takes about 15 minutes (the simulator is rebuilt, then cached), what to do when it fails, and how the version pin works.
It is only documentation: one new file, no change to the workflow. The numbers in it come from the run on master from 2026-10-26 (setup about 15 min on a cold cache, build 33 s, tests 72 s). Link it from the README or a CI.md, whichever you prefer.
Disclosure: we maintain PantheonSim.