umakanta75 / caliper

Automatically exported from code.google.com/p/caliper
Apache License 2.0
0 stars 0 forks source link

caliper build on windows fails #272

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Build caliper from the command line using the command
mvn eclipse:configure-workspace eclipse:eclipse install

What is the expected output? A successful build

What do you see instead? Build fails because it's unable to get a lock for a 
junit log file. See attached file for the full output.

What version of the product are you using? I did a git clone on 8/11/2013
Gitk says ac32d3ecb5e8a8cb42bcd41d772da12177ad3def

On what operating system? Windows 7 Professional

Please provide any additional information below.

Original issue reported on code.google.com by steven.l...@gmail.com on 11 Aug 2013 at 9:08

Attachments:

GoogleCodeExporter commented 9 years ago
I'd be glad to help test caliper on Windows.

Original comment by steven.l...@gmail.com on 11 Aug 2013 at 9:13

GoogleCodeExporter commented 9 years ago
The first build.txt that I attached was simply wrong. Attaching a new 
build2.txt that correctly illustrates this issue.

Original comment by steven.l...@gmail.com on 11 Aug 2013 at 9:23

Attachments:

GoogleCodeExporter commented 9 years ago
Interesting.  There was an issue before with path separators, but now I'm 
wondering if the :s in the file name are giving it issues.  Can you do a quick 
test to see if making a file with a : in the name works or not?

Original comment by gak@google.com on 16 Aug 2013 at 6:32

GoogleCodeExporter commented 9 years ago
You are correct about the colon in the file name. Here is an interaction from 
the command shell

c:\Users\Steven>echo "some great stuff" > 
C:\Users\Steven\AppData\Local\Temp\2013-08-11T21_18_21.288Z.5d1ea2ac-c1ce-4598-9
c97-19aa659c030f.log

c:\Users\Steven>echo "some great stuff" > 
C:\Users\Steven\AppData\Local\Temp\2013-08-11T21:18:21.288Z.5d1ea2ac-c1ce-4598-9
c97-19aa659c030f.log
The filename, directory name, or volume label syntax is incorrect.

And here is the relevant log entry from SysInternals Procmon.exe while running 
the mvn command again. Note the result was "NAME INVALID"

7:08:42.9153421 
PM  java.exe    5364    CreateFile  C:\Users\Steven\AppData\Local\Temp\junit681063672646
083106\junit8741959677784653729\log\2013-08-17T00:08:42.646Z.6524c0e0-0e99-45f0-
9221-fd02ccfbf3f5.log.lck   NAME INVALID    Desired Access: Generic Write, Read 
Attributes, Disposition: OverwriteIf, Options: Synchronous IO Non-Alert, 
Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: 0

Attaching the full log file (caliper_build.XML)  from PROCMON.EXE in case you 
want to look at other things. The filter was set to look at events in my temp 
directory only.

Original comment by steven.l...@gmail.com on 17 Aug 2013 at 12:20

Attachments:

GoogleCodeExporter commented 9 years ago
Awesome.  Thanks for looking into it.  That makes this an easy fix.

Original comment by gak@google.com on 17 Aug 2013 at 12:26

GoogleCodeExporter commented 9 years ago
This is fixed in HEAD.

Original comment by gak@google.com on 23 Aug 2013 at 11:43

GoogleCodeExporter commented 9 years ago
Issue 265 has been merged into this issue.

Original comment by gak@google.com on 23 Aug 2013 at 11:44

GoogleCodeExporter commented 9 years ago
I did a git pull just now to get the fix that's been made. It now builds clean 
on my machine. Thanks.

Original comment by steven.l...@gmail.com on 24 Aug 2013 at 2:35

GoogleCodeExporter commented 9 years ago
No problem.

Original comment by gak@google.com on 24 Aug 2013 at 3:15