Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-02-11 Thread Igor Filippov
Not that I use it or recommend it but a bit of googling brought me this:
http://www.appveyor.com/

Also, perhaps something is possible with azure cloud and visual studio
online?

HTH,
Igor


On Tue, Feb 10, 2015 at 11:52 PM, Greg Landrum 
wrote:

> This particular problem was my fault. It had been a while since I did a
> windows build, so I hadn't caught the problem you point out below. I just
> fixed it and checked in the changes.
>
> Apologies that you ended up wasting time on this.
>
> If anyone knows of an online continuous-integration providers (like
> Travis) that support Windows, I would be very, very happy to hear about it.
>
> -greg
>
>
> On Tue, Feb 10, 2015 at 7:14 PM, James Davidson 
> wrote:
>
>>  Hi Paolo, Greg, et al.
>>
>>
>>
>> I have also been having some problems recently building (64-bit Windows)
>> from recent github versions, but I don’t know if this is related to what
>> you see, Paolo…
>>
>> My environment is Win 7 64-bit, CMake 3.0.0, boost_1_55_0-msvc-11.0-64,
>> MS Visual Studio Express 2012.
>>
>>
>>
>> I have done a bit of version rolling-back and forwards to see if I can
>> pinpoint the last version that builds with no errors, and this is what I
>> have found so far (sorted by revision, not by sequence of attempts!):
>>
>>
>>
>> 4577   - compiles fine, - passes all tests
>>
>> *4618*   - as above
>>
>> 4649   - some errors during compile, -passes all tests except the
>> molDraw2D bits (which are also involved in the errors)
>>
>> 4651   - as above
>>
>> 4743   - as above
>>
>> *4765*   - as above
>>
>> 4780   - pyGraphMolWrap now fails test
>>
>> 4826   - this is where significant problems start (for me at least).
>> pyGraphMolWrap still fails, but now with a segfault
>>
>> 4859   - same segfault as above.  Also pymolDraw2D test fails…
>>
>>
>>
>>
>>
>> The errors I start to see for molDraw2D are this sort of thing (is this
>> expected?):
>>
>>
>>
>> Error  49   error C2668: 'boost::tuples::tie' : ambiguous
>> call to overloaded function
>> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   341
>> 1  MolDraw2D
>>
>> Error  50   error C2668: 'boost::tuples::tie' : ambiguous
>> call to overloaded function
>> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   353
>> 1  MolDraw2D
>>
>> Error  51   error C2668: 'boost::tuples::tie' : ambiguous
>> call to overloaded function
>> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   357
>> 1  MolDraw2D
>>
>> Error  61   error C2668: 'boost::tuples::tie' : ambiguous
>> call to overloaded function
>> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   544
>> 1  MolDraw2D
>>
>> Error  63   error C2668: 'boost::tuples::tie' : ambiguous
>> call to overloaded function
>> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   591
>> 1  MolDraw2D
>>
>> Error  131 error LNK1181: cannot open input file
>> '..\..\..\lib\Release\MolDraw2D.lib'
>> C:\RDKit\build\Code\GraphMol\MolDraw2D\LINK  moldraw2DTest1
>>
>> Error  149 error LNK1181: cannot open input file
>> '..\..\..\lib\Release\MolDraw2D.lib'
>> C:\RDKit\build\Code\GraphMol\Wrap\LINK   rdmolops
>>
>>
>>
>>
>>
>> If I see the above errors when building ‘ALL_BUILD’, I also see the
>> following error when building the ‘INSTALL’ section:
>>
>>
>>
>> Error  41   error MSB3073: The command "setlocal
>>
>> "C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P
>> cmake_install.cmake
>>
>> if %errorlevel% neq 0 goto :cmEnd
>>
>> :cmEnd
>>
>> endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
>>
>> :cmErrorLevel
>>
>> exit /b %1
>>
>> :cmDone
>>
>> if %errorlevel% neq 0 goto :VCEnd
>>
>> :VCEnd" exited with code 1.C:\Program Files
>> (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets
>> 134 5  INSTALL
>>
>>
>>
>>
>>
>>
>>
>> Anyway, 4618 is the latest revision that I have tested where I see no
>> build errors, and 4765 is the latest revision I’ve found before I start to
>> see pyGraphMolWrap tests failing (or segfaults).  For now, I have
>> rolled-back my installation to 4618 (but would be very happy if anyone can
>> figure-out what causes the problems with later revisions).
>>
>>
>>
>> Kind regards
>>
>>
>>
>> James
>>
>> __
>> PLEASE READ: This email is confidential and may be privileged. It is
>> intended for the named addressee(s) only and access to it by anyone else is
>> unauthorised. If you are not an addressee, any disclosure or copying of the
>> contents of this email or any action taken (or not taken) in reliance on it
>> is unauthorised and may be unlawful. If you have received this email in
>> error, please notify the sender or postmas...@vernalis.com. Email is not
>> a secure method of communication and the Company 

Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-02-10 Thread James Davidson
Hi Greg

Thanks for the fix – I can confirm that rev4861 builds and passes all the tests 
under my environment now.

Kind regards

James

__
PLEASE READ: This email is confidential and may be privileged. It is intended 
for the named addressee(s) only and access to it by anyone else is 
unauthorised. If you are not an addressee, any disclosure or copying of the 
contents of this email or any action taken (or not taken) in reliance on it is 
unauthorised and may be unlawful. If you have received this email in error, 
please notify the sender or postmas...@vernalis.com. Email is not a secure 
method of communication and the Company cannot accept responsibility for the 
accuracy or completeness of this message or any attachment(s). Please check 
this email for virus infection for which the Company accepts no responsibility. 
If verification of this email is sought then please request a hard copy. Unless 
otherwise stated, any views or opinions presented are solely those of the 
author and do not represent those of the Company.

The Vernalis Group of Companies
100 Berkshire Place
Wharfedale Road
Winnersh, Berkshire
RG41 5RD, England
Tel: +44 (0)118 938 

To access trading company registration and address details, please go to the 
Vernalis website at www.vernalis.com and click on the "Company address and 
registration details" link at the bottom of the page..
__
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss


Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-02-10 Thread Greg Landrum
This particular problem was my fault. It had been a while since I did a
windows build, so I hadn't caught the problem you point out below. I just
fixed it and checked in the changes.

Apologies that you ended up wasting time on this.

If anyone knows of an online continuous-integration providers (like Travis)
that support Windows, I would be very, very happy to hear about it.

-greg


On Tue, Feb 10, 2015 at 7:14 PM, James Davidson 
wrote:

>  Hi Paolo, Greg, et al.
>
>
>
> I have also been having some problems recently building (64-bit Windows)
> from recent github versions, but I don’t know if this is related to what
> you see, Paolo…
>
> My environment is Win 7 64-bit, CMake 3.0.0, boost_1_55_0-msvc-11.0-64, MS
> Visual Studio Express 2012.
>
>
>
> I have done a bit of version rolling-back and forwards to see if I can
> pinpoint the last version that builds with no errors, and this is what I
> have found so far (sorted by revision, not by sequence of attempts!):
>
>
>
> 4577   - compiles fine, - passes all tests
>
> *4618*   - as above
>
> 4649   - some errors during compile, -passes all tests except the
> molDraw2D bits (which are also involved in the errors)
>
> 4651   - as above
>
> 4743   - as above
>
> *4765*   - as above
>
> 4780   - pyGraphMolWrap now fails test
>
> 4826   - this is where significant problems start (for me at least).
> pyGraphMolWrap still fails, but now with a segfault
>
> 4859   - same segfault as above.  Also pymolDraw2D test fails…
>
>
>
>
>
> The errors I start to see for molDraw2D are this sort of thing (is this
> expected?):
>
>
>
> Error  49   error C2668: 'boost::tuples::tie' : ambiguous call
> to overloaded function
> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   341
> 1  MolDraw2D
>
> Error  50   error C2668: 'boost::tuples::tie' : ambiguous call
> to overloaded function
> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   353
> 1  MolDraw2D
>
> Error  51   error C2668: 'boost::tuples::tie' : ambiguous call
> to overloaded function
> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   357
> 1  MolDraw2D
>
> Error  61   error C2668: 'boost::tuples::tie' : ambiguous call
> to overloaded function
> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   544
> 1  MolDraw2D
>
> Error  63   error C2668: 'boost::tuples::tie' : ambiguous call
> to overloaded function
> C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   591
> 1  MolDraw2D
>
> Error  131 error LNK1181: cannot open input file
> '..\..\..\lib\Release\MolDraw2D.lib'
> C:\RDKit\build\Code\GraphMol\MolDraw2D\LINK  moldraw2DTest1
>
> Error  149 error LNK1181: cannot open input file
> '..\..\..\lib\Release\MolDraw2D.lib'
> C:\RDKit\build\Code\GraphMol\Wrap\LINK   rdmolops
>
>
>
>
>
> If I see the above errors when building ‘ALL_BUILD’, I also see the
> following error when building the ‘INSTALL’ section:
>
>
>
> Error  41   error MSB3073: The command "setlocal
>
> "C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P
> cmake_install.cmake
>
> if %errorlevel% neq 0 goto :cmEnd
>
> :cmEnd
>
> endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
>
> :cmErrorLevel
>
> exit /b %1
>
> :cmDone
>
> if %errorlevel% neq 0 goto :VCEnd
>
> :VCEnd" exited with code 1.C:\Program Files
> (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets
> 134 5  INSTALL
>
>
>
>
>
>
>
> Anyway, 4618 is the latest revision that I have tested where I see no
> build errors, and 4765 is the latest revision I’ve found before I start to
> see pyGraphMolWrap tests failing (or segfaults).  For now, I have
> rolled-back my installation to 4618 (but would be very happy if anyone can
> figure-out what causes the problems with later revisions).
>
>
>
> Kind regards
>
>
>
> James
>
> __
> PLEASE READ: This email is confidential and may be privileged. It is
> intended for the named addressee(s) only and access to it by anyone else is
> unauthorised. If you are not an addressee, any disclosure or copying of the
> contents of this email or any action taken (or not taken) in reliance on it
> is unauthorised and may be unlawful. If you have received this email in
> error, please notify the sender or postmas...@vernalis.com. Email is not
> a secure method of communication and the Company cannot accept
> responsibility for the accuracy or completeness of this message or any
> attachment(s). Please check this email for virus infection for which the
> Company accepts no responsibility. If verification of this email is sought
> then please request a hard copy. Unless otherwise stated, any views or
> opinions presented are solely those of the author and do not represent
> those of the Company.
>
>

Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-02-10 Thread James Davidson
Hi Paolo, Greg, et al.

I have also been having some problems recently building (64-bit Windows) from 
recent github versions, but I don't know if this is related to what you see, 
Paolo...
My environment is Win 7 64-bit, CMake 3.0.0, boost_1_55_0-msvc-11.0-64, MS 
Visual Studio Express 2012.

I have done a bit of version rolling-back and forwards to see if I can pinpoint 
the last version that builds with no errors, and this is what I have found so 
far (sorted by revision, not by sequence of attempts!):

4577   - compiles fine, - passes all tests
4618   - as above
4649   - some errors during compile, -passes all tests except the molDraw2D 
bits (which are also involved in the errors)
4651   - as above
4743   - as above
4765   - as above
4780   - pyGraphMolWrap now fails test
4826   - this is where significant problems start (for me at least).  
pyGraphMolWrap still fails, but now with a segfault
4859   - same segfault as above.  Also pymolDraw2D test fails...


The errors I start to see for molDraw2D are this sort of thing (is this 
expected?):

Error  49   error C2668: 'boost::tuples::tie' : ambiguous call to 
overloaded function
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   341 1  
MolDraw2D
Error  50   error C2668: 'boost::tuples::tie' : ambiguous call to 
overloaded function
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   353 1  
MolDraw2D
Error  51   error C2668: 'boost::tuples::tie' : ambiguous call to 
overloaded function
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   357 1  
MolDraw2D
Error  61   error C2668: 'boost::tuples::tie' : ambiguous call to 
overloaded function
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   544 1  
MolDraw2D
Error  63   error C2668: 'boost::tuples::tie' : ambiguous call to 
overloaded function
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp   591 1  
MolDraw2D
Error  131 error LNK1181: cannot open input file 
'..\..\..\lib\Release\MolDraw2D.lib'
C:\RDKit\build\Code\GraphMol\MolDraw2D\LINK  moldraw2DTest1
Error  149 error LNK1181: cannot open input file 
'..\..\..\lib\Release\MolDraw2D.lib'
C:\RDKit\build\Code\GraphMol\Wrap\LINK   rdmolops


If I see the above errors when building 'ALL_BUILD', I also see the following 
error when building the 'INSTALL' section:

Error  41   error MSB3073: The command "setlocal
"C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P 
cmake_install.cmake
if %errorlevel% neq 0 goto :cmEnd
:cmEnd
endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
:cmErrorLevel
exit /b %1
:cmDone
if %errorlevel% neq 0 goto :VCEnd
:VCEnd" exited with code 1.C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets   
 134 5  INSTALL



Anyway, 4618 is the latest revision that I have tested where I see no build 
errors, and 4765 is the latest revision I've found before I start to see 
pyGraphMolWrap tests failing (or segfaults).  For now, I have rolled-back my 
installation to 4618 (but would be very happy if anyone can figure-out what 
causes the problems with later revisions).

Kind regards

James

__
PLEASE READ: This email is confidential and may be privileged. It is intended 
for the named addressee(s) only and access to it by anyone else is 
unauthorised. If you are not an addressee, any disclosure or copying of the 
contents of this email or any action taken (or not taken) in reliance on it is 
unauthorised and may be unlawful. If you have received this email in error, 
please notify the sender or postmas...@vernalis.com. Email is not a secure 
method of communication and the Company cannot accept responsibility for the 
accuracy or completeness of this message or any attachment(s). Please check 
this email for virus infection for which the Company accepts no responsibility. 
If verification of this email is sought then please request a hard copy. Unless 
otherwise stated, any views or opinions presented are solely those of the 
author and do not represent those of the Company.

The Vernalis Group of Companies
100 Berkshire Place
Wharfedale Road
Winnersh, Berkshire
RG41 5RD, England
Tel: +44 (0)118 938 

To access trading company registration and address details, please go to the 
Vernalis website at www.vernalis.com and click on the "Company address and 
registration details" link at the bottom of the page..
__--
Dive into the World of Paralle

Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-02-10 Thread Paolo Tosco

Hi James,

investigating what is going wrong in the Windows build is on my to-do 
list for 21-22 Feb; I'll let you know if I manage to find something.


Kind regards,
Paolo

On 02/10/2015 06:14 PM, James Davidson wrote:


Hi Paolo, Greg, et al.

I have also been having some problems recently building (64-bit 
Windows) from recent github versions, but I don’t know if this is 
related to what you see, Paolo…


My environment is Win 7 64-bit, CMake 3.0.0, 
boost_1_55_0-msvc-11.0-64, MS Visual Studio Express 2012.


I have done a bit of version rolling-back and forwards to see if I can 
pinpoint the last version that builds with no errors, and this is what 
I have found so far (sorted by revision, not by sequence of attempts!):


4577   - compiles fine, - passes all tests

*4618*   - as above

4649   - some errors during compile, -passes all tests except the 
molDraw2D bits (which are also involved in the errors)


4651   - as above

4743   - as above

*4765*   - as above

4780   - pyGraphMolWrap now fails test

4826   - this is where significant problems start (for me at 
least).  pyGraphMolWrap still fails, but now with a segfault


4859   - same segfault as above.  Also pymolDraw2D test fails…

The errors I start to see for molDraw2D are this sort of thing (is 
this expected?):


Error  49   error C2668: 'boost::tuples::tie' : ambiguous 
call to overloaded function 
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp 341 
1  MolDraw2D


Error  50   error C2668: 'boost::tuples::tie' : ambiguous 
call to overloaded function 
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp 353 
1  MolDraw2D


Error  51   error C2668: 'boost::tuples::tie' : ambiguous 
call to overloaded function 
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp 357 
1  MolDraw2D


Error  61   error C2668: 'boost::tuples::tie' : ambiguous 
call to overloaded function 
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp 544 
1  MolDraw2D


Error  63   error C2668: 'boost::tuples::tie' : ambiguous 
call to overloaded function 
C:\RDKit\Code\GraphMol\MolDraw2D\MolDraw2D.cpp 591 
1  MolDraw2D


Error  131 error LNK1181: cannot open input file 
'..\..\..\lib\Release\MolDraw2D.lib' 
C:\RDKit\build\Code\GraphMol\MolDraw2D\LINK moldraw2DTest1


Error  149 error LNK1181: cannot open input file 
'..\..\..\lib\Release\MolDraw2D.lib' 
C:\RDKit\build\Code\GraphMol\Wrap\LINK   rdmolops


If I see the above errors when building ‘ALL_BUILD’, I also see the 
following error when building the ‘INSTALL’ section:


Error  41   error MSB3073: The command "setlocal

"C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P 
cmake_install.cmake


if %errorlevel% neq 0 goto :cmEnd

:cmEnd

endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone

:cmErrorLevel

exit /b %1

:cmDone

if %errorlevel% neq 0 goto :VCEnd

:VCEnd" exited with code 1. C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets 
134 5  INSTALL


Anyway, 4618 is the latest revision that I have tested where I see no 
build errors, and 4765 is the latest revision I’ve found before I 
start to see pyGraphMolWrap tests failing (or segfaults).  For now, I 
have rolled-back my installation to 4618 (but would be very happy if 
anyone can figure-out what causes the problems with later revisions).


Kind regards

James


__
PLEASE READ: This email is confidential and may be privileged. It is 
intended for the named addressee(s) only and access to it by anyone 
else is unauthorised. If you are not an addressee, any disclosure or 
copying of the contents of this email or any action taken (or not 
taken) in reliance on it is unauthorised and may be unlawful. If you 
have received this email in error, please notify the sender or 
postmas...@vernalis.com. Email is not a secure method of communication 
and the Company cannot accept responsibility for the accuracy or 
completeness of this message or any attachment(s). Please check this 
email for virus infection for which the Company accepts no 
responsibility. If verification of this email is sought then please 
request a hard copy. Unless otherwise stated, any views or opinions 
presented are solely those of the author and do not represent those of 
the Company.


The Vernalis Group of Companies
100 Berkshire Place
Wharfedale Road
Winnersh, Berkshire
RG41 5RD, England
Tel: +44 (0)118 938 

To access trading company registration and address details, please go 
to the Vernalis website at www.vernalis.com and click on the "Company 
address and registration details" link at the bottom of the page..

__


---

Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-01-24 Thread Paolo Tosco
Thanks Greg. I'll investigate more and try to understand what's going wrong 
here.

Cheers,
p.



> On 25 Jan 2015, at 08:37, Greg Landrum  wrote:
> 
> A quick one: it's not windows in general. I just built and tested the current 
> github version on my window7 machine using my usual visual studio 2010 setup.
> 
> On Fri, Jan 23, 2015 at 7:11 PM, Paolo Tosco  wrote:
>> Dear Igor,
>> 
>> Thank for your suggestion. Indeed, all of my environment variables are 
>> correctly set. I have just verified that I can build the latest released 
>> version 2014_09_2 with MSVC 2013 without issues, all tests are passed.
>> Instead, with the development version,
>> 
>> The following tests FAILED:
>>  4 - pyDiscreteValueVect (Failed)
>>  5 - pySparseIntVect (Failed)
>> 32 - testMolSupplier (Failed)
>> 48 - pyPartialCharges (Failed)
>> 69 - pyGraphMolWrap (Failed)
>> 75 - pyRanker (Failed)
>> 77 - pyFeatures (Failed)
>> 78 - pythonTestDbCLI (Failed)
>> 79 - pythonTestDirML (Failed)
>> 84 - pythonTestDirChem (Failed)
>> 
>> More specifically, testMolSupplier.exe crashes ("testMolSupplier.exe has 
>> stopped working"), while
>> Python tests fail because of Python modules failing to load:
>> 
>> c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe 
>> testFeatures.py
>> Testing ChemicalFeatures Wrapper code:
>> .E
>> ==
>> ERROR: testPickle (__main__.TestCase)
>> --
>> Traceback (most recent call last):
>>  File "testFeatures.py", line 81, in testPickle
>>ffeat2=cPickle.load(inF, encoding='bytes')
>>  File "C:\build\rdkit\rdkit\_py2_pickle.py", line 5, in load
>>def load(f, **kwargs): return _load(f)
>> ImportError: No module named rdChemicalFeatures
>> 
>> --
>> Ran 2 tests in 0.001s
>> 
>> FAILED (errors=1)
>> 
>> However, the following works fine:
>> 
>> c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe
>> Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)] on 
>> win32
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import rdkit
>> >>> from rdkit import Chem
>> >>> from rdkit.Chem import rdChemicalFeatures
>> >>>
>> 
>> Thanks in advance to anybody who has an idea of what might be going wrong 
>> with the development version.
>> Kind regards,
>> Paolo
>> 
>> 
>> --
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>> ___
>> Rdkit-discuss mailing list
>> Rdkit-discuss@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
> 
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss


Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-01-24 Thread Greg Landrum
A quick one: it's not windows in general. I just built and tested the
current github version on my window7 machine using my usual visual studio
2010 setup.

On Fri, Jan 23, 2015 at 7:11 PM, Paolo Tosco  wrote:

> Dear Igor,
>
> Thank for your suggestion. Indeed, all of my environment variables are
> correctly set. I have just verified that I can build the latest released
> version 2014_09_2 with MSVC 2013 without issues, all tests are passed.
> Instead, with the development version,
>
> The following tests FAILED:
>  4 - pyDiscreteValueVect (Failed)
>  5 - pySparseIntVect (Failed)
> 32 - testMolSupplier (Failed)
> 48 - pyPartialCharges (Failed)
> 69 - pyGraphMolWrap (Failed)
> 75 - pyRanker (Failed)
> 77 - pyFeatures (Failed)
> 78 - pythonTestDbCLI (Failed)
> 79 - pythonTestDirML (Failed)
> 84 - pythonTestDirChem (Failed)
>
> More specifically, testMolSupplier.exe crashes ("testMolSupplier.exe has
> stopped working"), while
> Python tests fail because of Python modules failing to load:
>
> c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe
> testFeatures.py
> Testing ChemicalFeatures Wrapper code:
> .E
> ==
> ERROR: testPickle (__main__.TestCase)
> --
> Traceback (most recent call last):
>  File "testFeatures.py", line 81, in testPickle
>ffeat2=cPickle.load(inF, encoding='bytes')
>  File "C:\build\rdkit\rdkit\_py2_pickle.py", line 5, in load
>def load(f, **kwargs): return _load(f)
> ImportError: No module named rdChemicalFeatures
>
> --
> Ran 2 tests in 0.001s
>
> FAILED (errors=1)
>
> However, the following works fine:
>
> c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe
> Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)]
> on win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import rdkit
> >>> from rdkit import Chem
> >>> from rdkit.Chem import rdChemicalFeatures
> >>>
>
> Thanks in advance to anybody who has an idea of what might be going wrong
> with the development version.
> Kind regards,
> Paolo
>
>
>
> --
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> ___
> Rdkit-discuss mailing list
> Rdkit-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
>
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss


Re: [Rdkit-discuss] Tests failing on Windows: more info

2015-01-23 Thread Greg Landrum
Hi Paolo,

I haven't built and tested with Windows in a while, so it could be that
there's a problem in the code. I will give it a try when I'm back in Basel
this weekend (I'm travelling now) and let you know if I can build it.

-greg


On Fri, Jan 23, 2015 at 1:11 PM, Paolo Tosco  wrote:

> Dear Igor,
>
> Thank for your suggestion. Indeed, all of my environment variables are
> correctly set. I have just verified that I can build the latest released
> version 2014_09_2 with MSVC 2013 without issues, all tests are passed.
> Instead, with the development version,
>
> The following tests FAILED:
>  4 - pyDiscreteValueVect (Failed)
>  5 - pySparseIntVect (Failed)
> 32 - testMolSupplier (Failed)
> 48 - pyPartialCharges (Failed)
> 69 - pyGraphMolWrap (Failed)
> 75 - pyRanker (Failed)
> 77 - pyFeatures (Failed)
> 78 - pythonTestDbCLI (Failed)
> 79 - pythonTestDirML (Failed)
> 84 - pythonTestDirChem (Failed)
>
> More specifically, testMolSupplier.exe crashes ("testMolSupplier.exe has
> stopped working"), while
> Python tests fail because of Python modules failing to load:
>
> c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe
> testFeatures.py
> Testing ChemicalFeatures Wrapper code:
> .E
> ==
> ERROR: testPickle (__main__.TestCase)
> --
> Traceback (most recent call last):
>  File "testFeatures.py", line 81, in testPickle
>ffeat2=cPickle.load(inF, encoding='bytes')
>  File "C:\build\rdkit\rdkit\_py2_pickle.py", line 5, in load
>def load(f, **kwargs): return _load(f)
> ImportError: No module named rdChemicalFeatures
>
> --
> Ran 2 tests in 0.001s
>
> FAILED (errors=1)
>
> However, the following works fine:
>
> c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe
> Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)]
> on win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import rdkit
> >>> from rdkit import Chem
> >>> from rdkit.Chem import rdChemicalFeatures
> >>>
>
> Thanks in advance to anybody who has an idea of what might be going wrong
> with the development version.
> Kind regards,
> Paolo
>
>
>
> --
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> ___
> Rdkit-discuss mailing list
> Rdkit-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
>
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss


[Rdkit-discuss] Tests failing on Windows: more info

2015-01-23 Thread Paolo Tosco
Dear Igor,

Thank for your suggestion. Indeed, all of my environment variables are 
correctly set. I have just verified that I can build the latest released 
version 2014_09_2 with MSVC 2013 without issues, all tests are passed.
Instead, with the development version,

The following tests FAILED:
 4 - pyDiscreteValueVect (Failed)
 5 - pySparseIntVect (Failed)
32 - testMolSupplier (Failed)
48 - pyPartialCharges (Failed)
69 - pyGraphMolWrap (Failed)
75 - pyRanker (Failed)
77 - pyFeatures (Failed)
78 - pythonTestDbCLI (Failed)
79 - pythonTestDirML (Failed)
84 - pythonTestDirChem (Failed)

More specifically, testMolSupplier.exe crashes ("testMolSupplier.exe has 
stopped working"), while
Python tests fail because of Python modules failing to load:

c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe testFeatures.py
Testing ChemicalFeatures Wrapper code:
.E
==
ERROR: testPickle (__main__.TestCase)
--
Traceback (most recent call last):
 File "testFeatures.py", line 81, in testPickle
   ffeat2=cPickle.load(inF, encoding='bytes')
 File "C:\build\rdkit\rdkit\_py2_pickle.py", line 5, in load
   def load(f, **kwargs): return _load(f)
ImportError: No module named rdChemicalFeatures

--
Ran 2 tests in 0.001s

FAILED (errors=1)

However, the following works fine:

c:\build\rdkit\Code\ChemicalFeatures\Wrap>c:\Python27\python.exe
Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)] on 
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import rdkit
>>> from rdkit import Chem
>>> from rdkit.Chem import rdChemicalFeatures
>>>

Thanks in advance to anybody who has an idea of what might be going wrong with 
the development version.
Kind regards,
Paolo


--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss