History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-1982
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: 3 3
Assignee: jason
Reporter: Daniel Ostermeier
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Directory renames failing during artifact collection

Created: 21/May/09 03:25 AM   Updated: 23/Feb/10 10:13 PM
Component/s: Build
Affects Version/s: 2.0.30
Fix Version/s: 2.1.4, 2.0.31

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
20-05-09 00:51:25 CEST: Artifacts compressed.
20-05-09 00:51:25 CEST: Recipe 'LM-X VCNET2003' completed with status success
20-05-09 00:51:25 CEST: Collecting recipe artifacts...
20-05-09 00:51:26 CEST: Recipe 'LM-X VCNET2003' completed with status error
20-05-09 00:51:26 CEST: Collection complete
20-05-09 00:51:26 CEST: Cleaning up agent work area...
20-05-09 00:51:26 CEST: Clean up complete.
20-05-09 00:51:26 CEST: Running post stage hooks...
20-05-09 00:51:26 CEST: Post stage hooks complete (0 hooks run).

Pulse then posts:

Error executing recipe LM-X VCNET2003
build stage :: Run :: LM-X VCNET2003@Windows XP - 32 bit
Unable to rename result directory to 'c:\pulsedata\projects\19791874\00006681\113311761\output'



 All   Comments   Work Log   Change History      Sort Order:
Daniel Ostermeier - 21/May/09 03:25 AM
> Ok, so we know that in this case the agent data directory was correct
> > and that this occured on the server. In light of that information,
> > there are a number of possible external factors that may have caused
> > this error. The most likely cause is usually that one of the files in
> > the directory being renamed is open / being accessed. This often shows
> > up locally if I am browsing the the output directories for some reason.
> > Another cause might be a virus scanner holding a lock to a file. Are
> > either of these possibilities?.
> >

There are no scanners or other external tools that can be holding files. We
don't have any virus scanner on the machine. The previous version worked
fine in the same environment for several years also. There has been no
browsing going on either.

Maybe it's possible to see any locked files from a log?

> > Assuming that this is not the case, the next question would be: is this
> > problem / failure consistent. Consistent for the project and consistent
> > on that particular agent?.
> >

So far we get a lot of errors at random and are unable to build a single app
without random failures... so I would not consider it to be consistent. Once
some of the other problems will go away then this might too.

Daniel Ostermeier - 21/May/09 03:25 AM
In any case this is a problem we have with our windows builds. Essentially
everything is fine except the artifacts collection which then causes the
build to fail.

jason - 29/May/09 09:37 AM
Candidate fix in change 5944. More feedback required before we can resolve or further progress this issue.

jason - 30/May/09 01:01 PM
Candidate fix merged to trunk in change 5947.

jason - 10/Jun/09 08:06 AM
Candidate fix appears to have resolved this issue.