Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set SSG Test Names #1687

Merged
merged 6 commits into from
Apr 4, 2017
Merged

Conversation

jasonwalker80
Copy link
Member

  • a command to set test names on all SSG results (excluding aligner index, etc.)
  • wait to abandon builds until we have a complete list and test names are set

Copy link
Member

@ebelter ebelter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 🐇

},
abandon_builds => {
is => 'Boolean',
doc => 'attempt to abando all of the builds used by these results',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

abandon is short its final n.

my @results_to_set_test_name;
for my $build ( $self->builds ) {
my @results = $build->results;
push @results_to_set_test_name, grep { $result_classes_to_set_test_name->{$_->class} } @results;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The database/UR can do this restriction for us, e.g.:

$build->results(subclass_name => [
  'Genome::Qc::Result',
  'Genome::InstrumentData::AlignmentResult::Speedseq',
  'Genome::InstrumentData::AlignmentResult::Merged::Speedseq',
  'Genome::Model::SingleSampleGenotype::Result::HaplotypeCaller'
]);

…turned when evaluating storage or software results that require a test name when invalidating a build.
@jasonwalker80
Copy link
Member Author

@tmooney will the latest commit work for "whitelisting" result classes?

Copy link
Member

@tmooney tmooney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Is the idea that eventually disk_usage_allocations might decide what allocations to get in part based on disk_usage_results?

my $abandon_cmd = Genome::Model::Build::Command::Abandon->create(
builds => \@builds,
header_text => 'Build Abandoned - SR Test Name',
body_text => 'Software result '. $software_result->id .' has new test name '. $self->new_test_name,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this pulled out of the loop $software_result is no longer available.

@jasonwalker80
Copy link
Member Author

Yes, the intent is to eventually define _disk_usage_result_subclass_names for all model types and disk_usage_allocations could then rely on that instead. I have a feeling there will be issues with backward compatibility for old Workflow/Flow builds and such, but at some point we can ignore that.

@jasonwalker80 jasonwalker80 merged commit 7924a0f into genome:master Apr 4, 2017
@jasonwalker80 jasonwalker80 deleted the ssg_test_names branch April 4, 2017 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants