New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: C:\Temp\RoundhousE may not exist #7

Closed
ferventcoder opened this Issue May 26, 2011 · 8 comments

Comments

Projects
None yet
2 participants
@ferventcoder
Member

ferventcoder commented May 26, 2011

Writing the log file out will fail if it can't reach the folder above.

@PascalMestdach

This comment has been minimized.

Show comment
Hide comment
@PascalMestdach

PascalMestdach Jun 9, 2011

Even a bigger problem with the c:\temp\roundhouse\roundhouse.changes.log is that when RoundhousE is executed on a buildserver for multiple projects at the same time, then one of the builds fail. Because the logging file is in use by another process. A better solution would be to make the output folder required, and always log there, instead of first logging to c:\temp and then copying the file.

Even a bigger problem with the c:\temp\roundhouse\roundhouse.changes.log is that when RoundhousE is executed on a buildserver for multiple projects at the same time, then one of the builds fail. Because the logging file is in use by another process. A better solution would be to make the output folder required, and always log there, instead of first logging to c:\temp and then copying the file.

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Jun 9, 2011

Member

Yep - to do that I need to actually set up logging configuration that
explicitly points to that folder.


Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

On Thu, Jun 9, 2011 at 4:08 PM, PascalMestdach <
reply@reply.github.com>wrote:

Even a bigger problem with the c:\temp\roundhouse\roundhouse.changes.log is
that when RoundhousE is executed on a buildserver for multiple projects at
the same time, then one of the builds fail. Because the logging file is in
use by another process. A better solution would be to make the output folder
required, and always log there, instead of first logging to c:\temp and then
copying the file.

Reply to this email directly or view it on GitHub:
#7 (comment)

Member

ferventcoder commented Jun 9, 2011

Yep - to do that I need to actually set up logging configuration that
explicitly points to that folder.


Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

On Thu, Jun 9, 2011 at 4:08 PM, PascalMestdach <
reply@reply.github.com>wrote:

Even a bigger problem with the c:\temp\roundhouse\roundhouse.changes.log is
that when RoundhousE is executed on a buildserver for multiple projects at
the same time, then one of the builds fail. Because the logging file is in
use by another process. A better solution would be to make the output folder
required, and always log there, instead of first logging to c:\temp and then
copying the file.

Reply to this email directly or view it on GitHub:
#7 (comment)

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Jun 9, 2011

Member

And that would be a better solution. I am not a fan of having it go one place and then moving it somewhere. Perhaps I can grab the logger and point it to the correct directory to ease the configuration pain.

Member

ferventcoder commented Jun 9, 2011

And that would be a better solution. I am not a fan of having it go one place and then moving it somewhere. Perhaps I can grab the logger and point it to the correct directory to ease the configuration pain.

@PascalMestdach

This comment has been minimized.

Show comment
Hide comment
@PascalMestdach

PascalMestdach Jun 9, 2011

Yes, that would solve it. And maybe give the outputfolder a default to c:\temp\roundhouse so that it's no breaking change?

Yes, that would solve it. And maybe give the outputfolder a default to c:\temp\roundhouse so that it's no breaking change?

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Jun 10, 2011

Member

Actually no one knows/cares about that folder. It started as a dropping point for the log prior to moving it to the change drop folder. It was meant to be temporary at the time it was added...

Member

ferventcoder commented Jun 10, 2011

Actually no one knows/cares about that folder. It started as a dropping point for the log prior to moving it to the change drop folder. It was meant to be temporary at the time it was added...

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
Member

ferventcoder commented Aug 16, 2011

Fixed in 9250541

GoogleCodeExporter pushed a commit to google-code-export/roundhouse that referenced this issue Mar 13, 2015

@ferventcoder ferventcoder modified the milestone: 0.8.5 Jun 3, 2015

@ferventcoder ferventcoder added Bug and removed Bug labels Jun 3, 2015

ChrisMissal pushed a commit to ChrisMissal/roundhouse that referenced this issue Jul 30, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment