So, on the Windows-2003 buildbot one of my mercurial workspaces is behaving strangely, i.e. the install sets show none of the changes in the workspace and the logs suggest that there were no changes in the cws, e.g.
http://buildbot.go-oo.org/buildbot/builders/Windows-2003/builds/367/steps/CWS/logs/stdio Getting CWS branch named 'pythonssl' Restore workdir.hg... cleaning workdir Pull /cws/pythonssl to workdir Update workdir 0 files updated, 0 files merged, 0 files removed, 0 files unresolved Mercurial exited with status 0 Comparison against another of my workspaces... http://buildbot.go-oo.org/buildbot/builders/Windows-2003/builds/362/steps/CWS/logs/stdio Getting CWS branch named 'cmcfixes65' cleaning workdir Pull /cws/cmcfixes65 to workdir Update workdir 17 files updated, 0 files merged, 0 files removed, 0 files unresolved i.e. the pythonssl has an additional "Restore workdir.hg" in it and 0 files updated. Now if I do a cws fetch -c pythonssl pythonssl I do get the changes I expect i.e. I didn't just commit and then forget to push for example. Anyone know what I may have cocked up here ? C. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
