| << Back to previous view |
|
[QB-686] util.cleanDir is now failing randomly on QB 3.x
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.0.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Roger Perkins | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | Various Windows versions | ||
| Description |
|
QB 2.x never had any issues when it came to running "util.cleanDir" on our nightly builds to wipe the workspaces clean. Since switching to QB 3.x it seems to be failing at least once a night across the different configurations. One of the folders that threw the exception was checked out the day before but never has anything access from it (as it's part of an art tool-chain not used when building code) so shouldn't have had anything locking that folder (it's possible a virus scanner or windows could have been doing something at exactly the wrong moment in that folder).
This is really serious for us as the cleanDir running partially leaves that agent in an unknown state where Perforce can think a lot of files exist on the hard-drive that have subsequently been manually deleted (so it won't grab them again). |
| Comments |
| Comment by Robin Shen [ 14/Oct/10 01:50 AM ] |
| We will revert back to use 2.x directory cleanup logic in next patch release (although 3.x cleanupDir() is enhanced to eliminate problems of 2.x when dealing with network drives, :( |
| Comment by Robin Shen [ 14/Oct/10 08:14 AM ] |
|
Sorry I was wrong on this. The directory deletion logic is exactly the same between 2.1.x and 3.0.x. Please refer to this forum post to further investigate the issue:
http://forum.pmease.com/viewtopic.php?f=1&t=1334 |
| Comment by Roger Perkins [ 08/Nov/10 02:28 PM ] |
|
I think this may well be the windows defrag on Win7. It's scheduled to run at 1am every Wednesday by default and was possibly causing the failures. I'd moved around some projects when upgrading to 3.x and possibly that's why it started to fail now and again.
This issue can be closed. |
| Comment by Robin Shen [ 08/Nov/10 11:53 PM ] |
| Thanks for the update. Closing it now. |