Ticket #7341 (closed: fixed)
Give better job names to remote jobs
Reported by: | Mathieu Doucet | Owned by: | Mathieu Doucet |
---|---|---|---|
Priority: | major | Milestone: | Release 2.6 |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Vickie Lynch |
Description
At the moment the reduction UIs use the name of the instrument as the name of a job submitted to a compute resource. If the user has loaded their reduction parameters from file, append the file name (without the extension) to the name of the instrument and use that as the job name instead.
Change History
comment:2 Changed 7 years ago by Mathieu Doucet
- Status changed from new to accepted
To test:
- Compile with -DMAKE_REMOTE_JOBS=TRUE
- Run Mantidplot on an analysis machine (but not on biganalysis06)
- Submit a new EQSANS job from a previously saved XML file.
- Go to the Remote Jobs tab and see that your job has a sane name (not just "EQSANS").
comment:3 Changed 7 years ago by Mathieu Doucet
- Status changed from accepted to verify
- Resolution set to fixed
comment:4 Changed 7 years ago by Vickie Lynch
- Status changed from verify to verifying
- Tester set to Vickie Lynch
comment:5 Changed 7 years ago by Vickie Lynch
- Status changed from verifying to closed
It has the name that I used to save the xml file
comment:6 Changed 7 years ago by Mathieu Doucet
Re #7341 Add proper name to remote jobs
Changeset: 399f9b7daaa4820f971b47be1e31e722849041aa
Note: See
TracTickets for help on using
tickets.
Re #7341 Add proper name to remote jobs
Changeset: 326b94543d6cc6131cbc70f5e63d1da0536d32ee