Interpretation of Travis checks errors

From GO Wiki
Revision as of 07:27, 17 October 2023 by Pascale (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Term should not have a superclass

Example of the error 'Term should not have a superclass':

  http://purl.obolibrary.org/obo/GO_0022889,Obsolete term should not have a superclass.

Troubleshooting:

  • Check the diff to see if the go-catalytic-activities-participants.owl file (located in the src/ontology/imports/ folder) was modified when the go-edit.obo ontology file was saved. This happens when a term cross-references a RHEA term and reaction participants are automatically loaded.

Fixing the error:

  • OPTION 1: Delete the 'has participant' classes from the go-edit.obo file.
    • Commit changes and push to master (same procedure as for the go-edit.obo file).
    • Note that you must move to the /imports directory to commit the file
  • OPTION 2: Delete the problematic class in the go-catalytic-activities-participants.owl file.
    • Commit changes and push to master (same procedure as for the go-edit.obo file).
    • Note that you must move to the /imports directory to commit the file

Obsolete term should not have a superclass

Example of the error 'Obsolete term should not have a superclass':

  http://purl.obolibrary.org/obo/GO_0000328,Obsolete term should not have a superclass

Troubleshooting:

  • Check the diff to see if the go_taxon_constraints.owl file (located in the src/ontology/imports/ folder) was modified go-edit.obo ontology file was saved.

Fixing the error:

  • Check if the taxon constraint is present in the only_in_taxon.tsv or in the never_in_taxon.tsv file.
  • Delete the taxon constraint as described in the [Adding_Taxon_Restrictions#Removing_a_taxon_constraint] instructions.

Review Status

Last reviewed: In progress

Reviewed by

Back to: Ontology Editing Guide