You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2020. It is now read-only.
Exome ref-align builds seem to generate a discreet error in the reference_alignment_coverage_stats step. The build still proceeds to completion and success but the error shows up in the logs in the reference_alignment_coverage_stats.*.err file.
277 2015-05-04 14:51:18-0500 clia1: DBD::Pg::st execute failed: ERROR: insert or update on table "instance" violates foreign key constraint "instance_peer_instance_id_fkey"
278 2015-05-04 14:51:18-0500 clia1: DETAIL: Key (peer_instance_id)=(6dfd26945f1b4213b27d90d28ea44500) is not present in table "instance". at /opt/gms/B3W1Y66/sw/ur/lib/UR/DBI.pm line 888.
279 2015-05-04 14:51:18-0500 clia1: 2015/05/04 14:51:18 Workflow::DataSource::InstanceSchema id(Workflow::DataSource::InstanceSchema): Workflow::DataSource::InstanceSchema: Error executing SQL:
280 2015-05-04 14:51:18-0500 clia1: INSERT INTO workflow.instance (workflow_plan_id,workflow_instance_id,peer_instance_id,parent_instance_id,parent_execution_id,parallel_index, output_stored,name,intention,input_stored,current_execution_id) VALUES (?,?,?,?,?,?,?,?,?,?,?)
281 2015-05-04 14:51:18-0500 clia1: PARAMS: 'c8aec8328be74a13ba49673970c388dc', '218d63b56e4d4da0b5fcb5b618414cfd', '6dfd26945f1b4213b27d90d28ea44500', '98424092236d44c580deaba9e9d7f5a2', (undef), '1', '^E^H^C^@^@^@^@', 'Coverage', (undef), '^E^H^C^@^@^@^G^D^Q^XWorkflow::Link::Instance^C^@^@^@^F
282 2015-05-04 14:51:18-0500 clia1: ^D6065^@^@^@^L__get_serial^H<81>^@^@^@^M_change_count^H<80>^@^@^@^Fbroken
The text was updated successfully, but these errors were encountered:
Exome ref-align builds seem to generate a discreet error in the
reference_alignment_coverage_stats
step. The build still proceeds to completion and success but the error shows up in the logs in the reference_alignment_coverage_stats.*.err file.The text was updated successfully, but these errors were encountered: