windows test broken

[Jason Moxham]

It look like one of the windows tests is broken

1>..\..\tests\memory.c(95) : warning C4311: 'type cast' : pointer truncation
fro
m 'void *' to 'unsigned long'
1>..\..\tests\memory.c(103) : warning C4311: 'type cast' : pointer
truncation fr
om 'void *' to 'unsigned long'
1>..\..\tests\memory.c(127) : warning C4311: 'type cast' : pointer
truncation fr
om 'void *' to 'unsigned long'
Generating Code...
Creating library...
Build log was saved at
"file://c:\Users\jasonadmin\mpir\mpir\trunk\build.vc9\mpi
r-tests\Win32\Release\BuildLog.htm"
add-test-lib - 0 error(s), 22 warning(s)
Error: project file
'C:\Users\jasonadmin\mpir\mpir\trunk\build.vc9\mpir-tests\mp
n.mullow_basecase.vcproj' was not found or not a valid project file.
Project file
'C:\Users\jasonadmin\mpir\mpir\trunk\build.vc9\mpir-tests\mpn.mullo
w_basecase.vcproj' could not be loaded.
The project is either missing from disk or access was denied.
Testing project in Win32\Release
No executable test files for this configuration

[Cactus]

[Cactus]

On Jul 31, 5:17 pm, "Jason Moxham" <ja...@njkfrudils.plus.com> wrote:

> It look like one of the windows tests is broken

Thanks for the report Jason - its a file I forgot to add before a
commit.

I update this shortly.

Brian

[Cactus]

The Windows test build should be OK now.

Something very odd is going on with SVN in that it keeps downloading
all the YASM files over and over. This is a real pain as it takes a
very long time.

This time it actually deleted all the YASM directory that I already
had and then proceeded to download these files all over again!! A
complete waste of bandwidth.

Any idea why this might be happening?

If I move to GIT will I be able to avoid this sort of behaviour?

Brian

[Jason Moxham]

Yeah , I know why it's happening , svn is fine , I updated yasm to fix a few
problems, so I deleted yasm and put the new one in it's place , GIT wouldn't
have made any difference , there is no chance that it could tell that I only
changed some files . What I should of done is to take a diff of yasm svn and
our yasm and apply that patch. I'll do that next time.

Sorry
Jason