Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 3418 by rbt post for perforce changelist on windows fails when files are located on different drive than rbt.exe

*** You must complete this form in its entirety, or your bug report will be
*** rejected.
*** If you have a security issue to report, please send it confidentially
*** Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
*** For customer support, please post to
*** If you have a patch, please submit it to
*** This bug tracker is public. Please check that any logs or other
*** that you include has been stripped of confidential information.

What version are you running?
Review Board Tools 0.6

What's the URL of the page containing the problem?

What steps will reproduce the problem?
1. Install Python and rbt on C drive of windows machine
2. From P4V, create workspace mapped to E: drive
3. use rbt post to attempt to request a code review

What is the expected output? What do you see instead?
- to be able to create a review request as one would for perforce workspaces on the C drive

- got "System cannot find the path specified" error; could not make review request

What operating system are you using? What browser?
Windows 8 (browser NA)

Please provide any additional information below.

When I created a workspace mapped to the C drive, it worked as it should.
When I moved rbt.exe to the E drive and attempted to request a code review with rbt post for a workspace whos files are on the E drive, and that worked as it should.

the problem arises when the drive of the location of the files being diff-ed is different than the drive of rbt.exe

I think that the perforce component or rbt uses p4 describe to get the list of affected files. I checked the output of 'p4 describe <changelist number> and it does not include the drive. This would explain why the system gives the error that it cannot find the specified path - if it assumes the same drive as rbt.exe, and that's the wrong drive, the files won't exist.

My workaround is to use a wrapper script for rbt. We configure the drive letter of the workspace mapping once, and the wrapper script copies rbt.exe and the other dependancies from \Python27\Scripts onto the workspace drive. Then it executes rbt.exe from that drive.

This isn't idea because it means there is a copy of rbt.exe on potentially many drives, and of course that the wrapper script has to be used instead of rbt.exe itself.

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to