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

Attach the history to workspaces during workflow algorithms. #680

Closed

Conversation

martyngigg
Copy link
Member

Fixes issue #11656

Tester
This is most easily tested by running the SNSPowderReduction algorithm and looking at the generated python script - it should contain the list of algorithms that were run.

This enables GeneratePythonScript to be run as part of a
workflow algorithm since the history up to that point has been recorded
properly on the workspace and not just in the parent algorithm.
Refs #11656
@martyngigg martyngigg added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Bug Issues and pull requests that are regressions or would be considered a bug by users (e.g. crashing) labels Apr 30, 2015
@martyngigg martyngigg added this to the Release 3.4 milestone Apr 30, 2015
@martyngigg
Copy link
Member Author

This is not the right way to got with this.

@martyngigg martyngigg closed this Apr 30, 2015
@martyngigg martyngigg deleted the 11656_empty_history_inside_workflow_algorithm branch September 15, 2015 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues and pull requests that are regressions or would be considered a bug by users (e.g. crashing) High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants