tentative tarballs

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

tentative tarballs

Luigi Ballabio-2
Hi all,
        0.3.7 tarballs are now available in <http://quantlib.org/gm/>.  
You're welcome to download and try them on your system(s). Three notes:

a) for all: you'll need a working Boost installation.

b) for packagers:
"make" now creates two libraries, namely, libQuantLib-0.3.7 (as usual)  
and libQuantLibFunctions-0.3.7, which is a functional rib taken out of  
the main library. You may choose to package them together or  
separately; in any case, note that the test-suite links to both, while  
SWIG-generated bindings only link to the main library.

c) for Dirk :)
these are NOT the final tarballs.

Later,
        Luigi


Reply | Threaded
Open this post in threaded view
|

tentative tarballs

Luigi Ballabio-2
Hi all,
        0.3.7 tarballs are now available in <http://quantlib.org/gm/>.  
You're welcome to download and try them on your system(s). Three notes:

a) for all: you'll need a working Boost installation.

b) for packagers:
"make" now creates two libraries, namely, libQuantLib-0.3.7 (as usual)  
and libQuantLibFunctions-0.3.7, which is a functional rib taken out of  
the main library. You may choose to package them together or  
separately; in any case, note that the test-suite links to both, while  
SWIG-generated bindings only link to the main library.

c) for Dirk :)
these are NOT the final tarballs.

Later,
        Luigi


Reply | Threaded
Open this post in threaded view
|

Re: tentative tarballs

mrtreibe
In reply to this post by Luigi Ballabio-2
On Jun 11, 2004, at 5:50 AM, Luigi Ballabio wrote:
>
> a) for all: you'll need a working Boost installation.
>

Perfect timing, my boost package just went into boost 10.3/unstable on
friday.

> b) for packagers:
> "make" now creates two libraries, namely, libQuantLib-0.3.7 (as usual)
> and libQuantLibFunctions-0.3.7, which is a functional rib taken out of
> the main library. You may choose to package them together or
> separately; in any case, note that the test-suite links to both, while
> SWIG-generated bindings only link to the main library.
>

Everything compiles fine, although the new -release linking caught me
out (although it makes sense).  The only problem is that I'm getting a
single failure in the test suite.

Exception in "StatisticsTest::testStatistics": std::exception:
incrementalstatistics.hpp:173: Real
QuantLib::IncrementalStatistics::max() const: empty sample set

The detailed report level doesn't really add any additional information:

  Test suite "Statistics tests" failed with:
   1 test case out of 2 passed
   1 test case out of 2 failed
   0 assertions out of 0 passed
   0 assertions out of 0 failed

     Test case "StatisticsTest::testStatistics" failed with:
     0 assertions out of 0 passed
     0 assertions out of 0 failed
     Test case "StatisticsTest::testStatistics" was aborted due to
uncaught exception, user assert or system error

     Test case "StatisticsTest::testSequenceStatistics" passed with:
     0 assertions out of 0 passed
     0 assertions out of 0 failed

Mark.



Reply | Threaded
Open this post in threaded view
|

Re: tentative tarballs

Dirk Eddelbuettel
In reply to this post by Luigi Ballabio-2
On Mon, Jun 14, 2004 at 09:36:41AM +0200, Luigi Ballabio wrote:
>
> Hi all,
> 0.3.7 tarballs are now available in <http://quantlib.org/gm/>.  
> You're welcome to download and try them on your system(s). Three notes:

QuantLib itself built fine yesterday, and the build daemons have built ia64,
s390, hppa, powerpc, arm, sparc and m68k.  

So I turned to QL-Python and QL-Ruby. QL-Python built, but has now been
hanging for 30 minutes at
        Testing observability of stocks ...
when running 'python2.3 setup test'.  Any idea?

For what it's worth, QL-Ruby doesn't have the issue.

> c) for Dirk :)
> these are NOT the final tarballs.

Thanks for that :)  I called them 0.3.6.rc.20040611 to ensure the final
0.3.7 will sort higher.

Dirk


--
FEATURE:  VW Beetle license plate in California


Reply | Threaded
Open this post in threaded view
|

Re: tentative tarballs

Luigi Ballabio-2
On 2004.06.18 05:36, Dirk Eddelbuettel wrote:

> On Mon, Jun 14, 2004 at 09:36:41AM +0200, Luigi Ballabio wrote:
> QuantLib itself built fine yesterday, and the build daemons have  
> built ia64, s390, hppa, powerpc, arm, sparc and m68k.
>
> So I turned to QL-Python and QL-Ruby. QL-Python built, but has now
> been hanging for 30 minutes at
> Testing observability of stocks ...
> when running 'python2.3 setup test'.  Any idea?
>
> For what it's worth, QL-Ruby doesn't have the issue.

Hmm, I don't know. I never saw it happen in Python. I did see this  
behavior in Ruby, but you didn't, so I'm officially puzzled.
Unfortunately I don't have much time to investigate the thing (next  
week I'm undergoing some minor surgery---nothing to be worried of, but  
I won't have a computer nearby :) so I think I'll disable that specific  
test in the final tarball and add the problem to the known bug list.

Later,
        Luigi


Reply | Threaded
Open this post in threaded view
|

Re: tentative tarballs

Dirk Eddelbuettel
On Fri, Jun 18, 2004 at 04:24:46PM +0200, Luigi Ballabio wrote:

> On 2004.06.18 05:36, Dirk Eddelbuettel wrote:
> >On Mon, Jun 14, 2004 at 09:36:41AM +0200, Luigi Ballabio wrote:
> >QuantLib itself built fine yesterday, and the build daemons have  
> >built ia64, s390, hppa, powerpc, arm, sparc and m68k.
> >
> >So I turned to QL-Python and QL-Ruby. QL-Python built, but has now
> >been hanging for 30 minutes at
> > Testing observability of stocks ...
> >when running 'python2.3 setup test'.  Any idea?
> >
> >For what it's worth, QL-Ruby doesn't have the issue.
>
> Hmm, I don't know. I never saw it happen in Python. I did see this  
> behavior in Ruby, but you didn't, so I'm officially puzzled.
> Unfortunately I don't have much time to investigate the thing (next  
> week I'm undergoing some minor surgery---nothing to be worried of, but  
> I won't have a computer nearby :) so I think I'll disable that specific  
> test in the final tarball and add the problem to the known bug list.

Can you point me to the smallest possible alteration of the tarball so that
I could make it locally and get this shipped, and thus tested on other arches?

Shall I just remove/rename/comment tests/instruments.py ?

Dirk

--
FEATURE:  VW Beetle license plate in California


Reply | Threaded
Open this post in threaded view
|

Re: tentative tarballs

Luigi Ballabio-2
On 2004.06.18 16:30, Dirk Eddelbuettel wrote:
> Can you point me to the smallest possible alteration of the tarball  
> so that I could make it locally and get this shipped, and thus tested  
> on other arches?

In QuantLibTestSuite.py, remove the relevant suite.addTest(...) line.

Later,
        Luigi


Reply | Threaded
Open this post in threaded view
|

Re: tentative tarballs

Dirk Eddelbuettel
On Fri, Jun 18, 2004 at 05:59:26PM +0200, Luigi Ballabio wrote:
> On 2004.06.18 16:30, Dirk Eddelbuettel wrote:
> >Can you point me to the smallest possible alteration of the tarball  
> >so that I could make it locally and get this shipped, and thus tested  
> >on other arches?
>
> In QuantLibTestSuite.py, remove the relevant suite.addTest(...) line.

Thanks!  Had to do the same for TermStructureTests, and then it built fine.
Uploaded now, so we have the candidate releases of QL, QL-P and QL-R in
Debian.

Bye, Dirk

[ off-topic: what's the word on Totti in Italy?  There was a fabulous NY
Times article on him a few days before the tournament, chronicling his rise
in popularity with the two books of Totti jokes he wrote/issued. Can resend
the article if there is interest. Boy do I ever miss the tv coverage :-/ ]

--
FEATURE:  VW Beetle license plate in California