-
Notifications
You must be signed in to change notification settings - Fork 57
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
Set SSG Test Names #1687
Conversation
jasonwalker80
commented
Mar 24, 2017
- 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
There was a problem hiding this 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', |
There was a problem hiding this comment.
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; |
There was a problem hiding this comment.
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.
@tmooney will the latest commit work for "whitelisting" result classes? |
There was a problem hiding this 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, |
There was a problem hiding this comment.
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.
Yes, the intent is to eventually define |