Skip to main content

Troubleshooting

This page lists common problems of maintenance work, grouped by where they appear, with their cause and fix. For findings in the extraction report, see Diagnostic Codes instead.

Local runs​

Message or symptomCauseFix
No local Artemis checkout is configured.Gradle does not know where Artemis isPass -PartemisPath, or set artemisPath or ARTEMIS_PATH, see Setup
… has uncommitted changes, so this run would not describe commit …The checkout has local changesUse a clean, separate checkout; never clean the one you work in
… is at commit … but this run expects …The checkout points to another commit than -PexpectedArtemisShaCheck out the expected commit, or leave out the expectation
The model stage did not produce model-result.json; run the upstream command before this one.You started a later stage without the earlier onesRun buildFeatureModelSnapshot, or the named stage first
The model artifact was produced with manifest digest … but this run requires …An input changed after the earlier stage ranRun the earlier stage again
Unsupported manifestVersion … or … contains unknown field(s) …The manifest has a wrong version or a typoFix the manifest entry that the message names
… was removed in manifestVersion …The manifest uses a section or field that the pipeline derives or reads elsewhereFollow the instruction in the message, see The Feature Manifest
Missing -PsnapshotPath=<snapshot-directory> …A snapshot task needs the path of a snapshotPass -PsnapshotPath=build/feature-extraction/<source-revision>/snapshot
The snapshot directory is missing after a runThe run had a blocking findingOpen report/index.html, see Fix a Failed Run

Pull request checks​

SymptomCauseFix
Model delivery gates fails after a manifest changeThe change leaves a gap at the pinned commitDownload the report artifact and fix the findings
Model delivery gates passes, but the poller failsThe pin is older than the commit the poller deliversMove the pin to the failing commit in your fix, see Fix a Failed Run
Server tests fail after a fixture refreshA new selectable feature has no binding classificationClassify it, see Update Ansible Bindings
A documentation-only pull request shows no application checksci.yml ignores changes in documentation/Nothing to fix; the documentation build checks the change

Delivery runs​

SymptomCauseFix
The poller summary says Delivery short-circuitedThe snapshot was already published from the current commit of this repositoryNothing to fix
The poller passes but opens no pull requestThe fixture and the pin are already currentNothing to fix
The delivery pull request is not createdWorkflows may not open pull requestsAllow it in the repository settings, see Repository Settings
A publish or promote job waitsThe environment requires an approvalA reviewer approves it on the run page
Promotion fails with No published image exists at …The digest is wrong or the image was deletedCopy the digest again from the publication summary or the ledger
Promotion fails with Malformed … labelThe image was not built by the delivery workflowsPromote only images that the publication workflow published

Retention​

SymptomCauseFix
Discovery tag retention fails without deleting anythingThe repository lacks admin access to the container packageGrant it, see Repository Settings

Documentation site​

SymptomCauseFix
The documentation build fails with broken linksA link points to a missing page or headingFix the link; run npm run build in documentation/ before you push
The site does not update after a mergeOnly changes in documentation/ on develop deploy the siteStart Deploy documentation by hand on develop
Search documentation