Unit Testing Error – Rosetta Commons

This topic has 6 replies, 2 voices, and was last updated 7 years, 10 months ago by Anonymous.

Viewing 3 reply threads

Author

Posts
- January 2, 2017 at 5:02 am #2555
  Anonymous
  I am getting the foloowing testing error when I setup Rosetta 3.7. It seems to be limited to one protocol. Is there a solution to fix this?
  
  Error Output as follows. Thank You
  
  failed tests:
  
      core.test: AtomTypeDatabaseIOTests:test_atom_type_set_name
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_AA_SET_command
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_vector_NPD_PROPERTY_command
  
      protocols.test: AlignResiduesMoverTests:test_align_theozyme
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_missing_correspondence_file
  
      protocols.test: AntibodyTaskOps:test_AddCDRProfilesOperation
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_varname_duplicated
  
      protocols.test: StructureDataTests:test_delete_segment
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_EXPRESSION_command_nocap_IN
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command_missing_listfile2
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_POSE_ENERGY_into_VECTOR_VARIABLE_command
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_VARIABLE_command_func_vecvarname
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_mean_of_vector_variable_command
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command_duplicate_varname
  
      protocols.test: AntibodyTaskOps:test_AddCDRProfileSetsOperation
  
      protocols.test: AlignResiduesMoverTests:test_tomponent_cstfile
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command_missing_listfile
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command_missing_varname2
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_AA_SET_command_missing_right_curly_brace
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_SET_CONDITION_command_from_AA_SET
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_EXPRESSION_command_two_local_variables
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command_function_varname
  
      protocols.test: StructureDataTests:test_enzdes_remarks
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_EXPRESSION_command_duplicated_local_varname
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_VARIABLE_command_bad_vecvarname
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_varname_function_name
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_missing_pdb_file
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_SET_CONDITION_command_from_aa_list_missing_lcurly
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command_missing_varname
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_VARIABLE_command
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_SET_CONDITION_command_from_aa_list
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_EXPRESSION_command_two_local_variables_misplaced_comma
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_SET_CONDITION_command_from_AA_SET_bad_name
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_POSE_ENERGY_command
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_varname_illegal_name
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_missing_pdb_file2
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_scalar_NPD_PROPERTY_command
  
      protocols.test: StructureDataTests:test_move_segments
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_missing_secondary_resfile2
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_EXPRESSION_command
  
      protocols.test: StructureDataTests:test_non_peptidic_bonds
  
      protocols.test: DynamicAggregateFunctionTests:test_initialize_empty_DAF
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_SUB_EXPRESSION_command
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_AA_SET_command_missing_equals_sign
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_read_simple_file
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_SET_CONDITION_command_from_aa_list_missing_comma
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_VECTOR_command_illegal_varname
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_missing_correspondence_file2
  
      protocols.test: DynamicAggregateFunctionTests:test_EntityFunc_AA_SET_command_missing_commas
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_VECTOR_VARIABLE_command_bad_varname
  
      protocols.test: DynamicAggregateFunctionTests:test_daf_STATE_command_missing_secondary_resfile
- January 2, 2017 at 4:09 pm #12047
  Anonymous
  The DynamicAggregateFunctionTests and the AntibodyTaskOps failures are known to be due to bugs in the tests (or the underlying code) – in either case it’s not your system, it’s just that our testing server doesn’t expose those errors and nobody has gotten around to fixing it. It’s basically a portability problem; something about that code is not portable across systems.
  
  The other errors have been recently reported by another (?) user, independent of the two I just mentioned (https://www.rosettacommons.org/comment/9533#comment-9533) – this makes me think that it’s another portability issue.
  
  I’ve raised the issue for the developers; unless you know this touches code you want to use. Only core.test: AtomTypeDatabaseIOTests:test_atom_type_set_name is really concerning. If you want to paste that error set I’ll take a deeper look at it specifically. Try “test/run.py –one AtomTypeDatabaseIOTests” to run just it.
- January 2, 2017 at 4:09 pm #12568
  Anonymous
  The DynamicAggregateFunctionTests and the AntibodyTaskOps failures are known to be due to bugs in the tests (or the underlying code) – in either case it’s not your system, it’s just that our testing server doesn’t expose those errors and nobody has gotten around to fixing it. It’s basically a portability problem; something about that code is not portable across systems.
  
  The other errors have been recently reported by another (?) user, independent of the two I just mentioned (https://www.rosettacommons.org/comment/9533#comment-9533) – this makes me think that it’s another portability issue.
  
  I’ve raised the issue for the developers; unless you know this touches code you want to use. Only core.test: AtomTypeDatabaseIOTests:test_atom_type_set_name is really concerning. If you want to paste that error set I’ll take a deeper look at it specifically. Try “test/run.py –one AtomTypeDatabaseIOTests” to run just it.
- January 2, 2017 at 4:09 pm #13089
  Anonymous
  The DynamicAggregateFunctionTests and the AntibodyTaskOps failures are known to be due to bugs in the tests (or the underlying code) – in either case it’s not your system, it’s just that our testing server doesn’t expose those errors and nobody has gotten around to fixing it. It’s basically a portability problem; something about that code is not portable across systems.
  
  The other errors have been recently reported by another (?) user, independent of the two I just mentioned (https://www.rosettacommons.org/comment/9533#comment-9533) – this makes me think that it’s another portability issue.
  
  I’ve raised the issue for the developers; unless you know this touches code you want to use. Only core.test: AtomTypeDatabaseIOTests:test_atom_type_set_name is really concerning. If you want to paste that error set I’ll take a deeper look at it specifically. Try “test/run.py –one AtomTypeDatabaseIOTests” to run just it.
- January 2, 2017 at 4:16 pm #12048
  Anonymous
  Actually, I checked our tests more extensively – the AtomTypeDatabaseIOTests issue is also harmless (it’s a bug in the test, not a bug in the code). You are probably safe to ignore these, but I am using your report as leverage to try to get people to fix them
- January 2, 2017 at 4:16 pm #12569
  Anonymous
  Actually, I checked our tests more extensively – the AtomTypeDatabaseIOTests issue is also harmless (it’s a bug in the test, not a bug in the code). You are probably safe to ignore these, but I am using your report as leverage to try to get people to fix them
- January 2, 2017 at 4:16 pm #13090
  Anonymous
  Actually, I checked our tests more extensively – the AtomTypeDatabaseIOTests issue is also harmless (it’s a bug in the test, not a bug in the code). You are probably safe to ignore these, but I am using your report as leverage to try to get people to fix them
Author

Posts

Viewing 3 reply threads

You must be logged in to reply to this topic.