A task's path can have redundant slashes if they are in the task name. I'm not sure if the correct response is to enforce no double slashed etc in the task name, or to just fix the path.
I think Beaker needs to reject tasks where the name contains redundant slashes (either a trailing slash, or multiple adjacent slashes) because they could lead to tasks with distinct names but mapping to the same filesystem path. We've already had a very similar problem in the past with logs (bug 865265).
On Gerrit: http://gerrit.beaker-project.org/2042
1. Failed to import job because of: Invalid task(s): /distribution/reservesys/ 2. Failed to import job because of: Invalid task(s): /distribution//reservesys 3. Failed to import job because of: Invalid task(s): /distribution\//reservesys
(In reply to xjia from comment #5) > 1. Failed to import job because of: Invalid task(s): > /distribution/reservesys/ > 2. Failed to import job because of: Invalid task(s): > /distribution//reservesys > 3. Failed to import job because of: Invalid task(s): > /distribution\//reservesys This error message just indicates that your job is referencing a task not known to Beaker. This bug is about refusing to allow tasks to be uploaded which have redundant slashes in their name. See the test cases linked in comment 3.
Beaker 0.14.1 has been released.