Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
Failed to run command: accurev mkws -H accurev:5050 -w qb-buildsrv3-246 -b RDM-Longview_RC -l /opt/quickbuild-5.0.18/workspace/root/RDM/12.0/Staging/RC
Command return code: 1
Command error output: Workspace qb-buildsrv3-246_build already exists .
That workspace name appears to have some problem. How can I get QuickBuild to increment the workspace number to use a new name instead?
-
replies
12
-
views
5819
-
stars
0
-
You may manually specify the workspace name by choosing option "specify workspace name".
As a quick workaround, I did just manually put in an Accurev workspace name, but it would be nice to have some way to just tell the system to increment to a new number instead.
Could you put in a feature request to fix this issue with Accurev? It is a real pain when the repository gets associated with the wrong accurev stream and the only way to fix it is to change the name of the configuration so that it will create a new workspace. Accurev allows workspaces to be "rebased" to a different stream, so this really shouldn't be a problem.
Before going further, I'd like to know why this is happening. For now, QB only tries to create the workspace if the workspace does not exist. Taking your case for instance, before calling command " accurev mkws -H accurev:5050 -w qb-buildsrv3-246 ...", it will issue below command to see if workspace "qb-buildsrv3-246_build" (workspace appended with user name) already exists:
accurev show -fix wspaces
So at your side, can you please help to run this command manually as the same user running QB to see if the output contains the problematic workspace?
<Element
Name="donotuse--qb-buildsrv3-246_kevint"
hidden="true"
Storage="/opt/quickbuild-5.0.18/workspace/root/RDM/12.0/Staging/1234780912347890"
Host="buildsrv3.seattlead.bstep.us"
Stream="1082"
depot="RDMe"
Target_trans="124422"
Trans="124422"
fileModTime="1375806575"
Type="1"
EOL="0"
user_id="21"
user_name="build"/>
So if you're just parsing the output to see if that name still exists in the list, then my quick-fix should be to just rename it so that string no longer appears.
However, the deeper issue is that once you've created a workspace and associated it with a stream based on the repository name for a configuration, if the stream name that the repository should use is changed, then the workspace is now based on the wrong stream and should be re-parented. If you try to delete the workspace and make a new one, Accurev's time-safe technology prevents this because the workspace still exists, it's just hidden and is still associated with that path and it's based on a different stream. In this case we need to do:
Reparent your workspace to a new development stream:
> accurev chws -w amber_dvt_mary -b q2_project_dev
That way the workspace name stays the same, the configuration name and path stay the same, but the repository can be changed to point to a different stream.
Yes, we will make this change (call "chws" to point the workspace to new backing stream if changed), but what I am curious is why QB reports below error:
Command error output: Workspace qb-buildsrv3-246_build already exists .
As QB already has the logic of checking existance of workspace before calling "mkws", and if exist, QB will proceed to modify the workspace instead of creating the new one. Can you please do below test to help with my investigation?
1. edit QB server "conf/log4j.properties" to enable debug logging.
2. create a configuration to checkout from Accurev in QB server, edit general setting of this configuration to enable debug logging.
3. reproduce the error again, and show me the build log as well as QB server log.
I did the steps you asked and the log files are available here: ftp://ftp.raima.com/outgoing/qb-accurev-issue.zip.
I copied everything in the logs directory. I hope that includes the debug output from the step, if not, please let me know where to find that file.
Sorry I did not find relevant errors in these log files. Maybe the log containing the error resides on some agent, or maybe errors in the server log has been flushed out. I still suggest to follow steps posted earlier to reproduce the issue again and get me the files. Below are the steps:
1. edit QB server "conf/log4j.properties" to enable debug logging.
2. create a configuration to checkout from Accurev in QB server, edit general setting of this configuration to enable debug logging.
3. reproduce the error again, and show me the build log as well as QB server log.
Uploaded another zip file with the same name containing the log files from the node where accurev is being run.
But I can not download this file now. Possibly under a different name?
yes, there was a typo, please try again.
Still any of these log files contain the "already exists" error. What I am looking for is to get the log containing this error and I suggested the approach in previous posts. That will help me to find out cause of the issue.
