Re: Ledger 3.1.1 release candidate

[Alexis]

Hi Bruce,
> It looks to me like that 'if not line' test is invalid... consider
> read_test() is called from a loop inside run_tests(). Eventually it hits
> the end of the file and the readline() test fails. That has no bearing on
> whether the test case is passing or failing.

You are right the test did not make much sense.


> What if you try the verbose output for one of the tests as above?

Then I also see the warnings, thanks for pointing this out.

I've pushed a fix for this issue to the next branch.
The test/RegressTests.py scripts now checks the test filesize
and properly fails if it is empty.

Let me know if this works for you.


Cheers,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[Bruce Schultz]

Hi Alexis,

On Sun, Sep 20, 2015 at 7:48 PM, Alexis  wrote:

> Hello Bruce,
> > Here's the output for all of the failing tests. Not sure what's going on
> > with the "WARNING: Empty testfile detected" errors.
>
> I've added the code below to test/RegressTests.py a little while ago:
>   line = self.fd.readline() # self.fd is a file object created with open()
>   if not line:
> print >>sys.stderr, "WARNING: Empty testfile detected: %s" %
> (self.filename)
> return False
>
> I thought it would only fail for testfiles that are empty,
> as it seems that is not the case.
>
> I wonder what readline() returns that the `if not line:` test succeeds,
> even though the file isn't empty.
>

It looks to me like that 'if not line' test is invalid... consider
read_test() is called from a loop inside run_tests(). Eventually it hits
the end of the file and the readline() test fails. That has no bearing on
whether the test case is passing or failing. Consider this verbose ctest
output:

$ ctest --verbose --output-on-failure -R 012ADB60
UpdateCTestConfiguration  from
:/c/Users/schultzb/src/ledger/DartConfiguration.tcl
UpdateCTestConfiguration  from
:/c/Users/schultzb/src/ledger/DartConfiguration.tcl
Test project /c/Users/schultzb/src/ledger
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
Checking test dependency graph end
test 215
Start 215: RegressTest_012ADB60

215: Test command: /usr/bin/python2.7.exe
"/c/Users/schultzb/src/ledger/test/RegressTests.py"
"/c/Users/schultzb/src/ledger/ledger.exe" "/c/Users/schultzb/src/ledger"
"/c/Users/schultzb/src/ledger/test/regress/012ADB60.test"
215: Environment variables:
215:  TZ=America/Chicago
215: Test timeout computed to be: 9.99988e+06
215: .
215: OK (1)
215: WARNING: Empty testfile detected:
/c/Users/schultzb/src/ledger/test/regress/012ADB60.test
1/1 Test #215: RegressTest_012ADB60 .   Passed0.73 sec

The following tests passed:
RegressTest_012ADB60

100% tests passed, 0 tests failed out of 1

Total Test time (real) =   0.83 sec

This is a passing test, but the warning is still there...


$ ctest --verbose --output-on-failure -R 3FE26304
UpdateCTestConfiguration  from
:/c/Users/schultzb/src/ledger/DartConfiguration.tcl
UpdateCTestConfiguration  from
:/c/Users/schultzb/src/ledger/DartConfiguration.tcl
Test project /c/Users/schultzb/src/ledger
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
Checking test dependency graph end
test 251
Start 251: RegressTest_3FE26304

251: Test command: /usr/bin/python2.7.exe
"/c/Users/schultzb/src/ledger/test/RegressTests.py"
"/c/Users/schultzb/src/ledger/ledger.exe" "/c/Users/schultzb/src/ledger"
"/c/Users/schultzb/src/ledger/test/regress/3FE26304.test"
251: Environment variables:
251:  TZ=America/Chicago
251: Test timeout computed to be: 9.99988e+06
251: .
251: E[3FE26304.test]
251: OK (1)  FAILED (1)
251: WARNING: Empty testfile detected:
/c/Users/schultzb/src/ledger/test/regress/3FE26304.test
1/1 Test #251: RegressTest_3FE26304 .***Failed1.30 sec
.
E[3FE26304.test]
OK (1)  FAILED (1)
WARNING: Empty testfile detected:
/c/Users/schultzb/src/ledger/test/regress/3FE26304.test


0% tests passed, 1 tests failed out of 1

Total Test time (real) =   1.40 sec

The following tests FAILED:
251 - RegressTest_3FE26304 (Failed)
Errors while running CTest


This is from one of the problem tests. In this case there are 2 tests in
the .test file. It looks like one passes, the other fails. Unfortunately
the only output from the test is the empty testfile warning. But its not
empty, and I've added enough print line statements to convince myself that
it has read the whole file correctly. so its something else. I'll keep
digging...


> In a previous message you mentioned Python 2.7.10 is used on Cygwin,
> I use the same version on Mac OS X 10.11 El Capitan, yet I do not see
> the issues.
>

What if you try the verbose output for one of the tests as above?


>
> Maybe you could rerun the tests with the following slight modification
> of test/RegressTests.py to aid in debugging:
>   line = self.fd.readline() # self.fd is a file object created with open()
>   if not line:
> print >>sys.stderr, "WARNING: Empty testfile detected: %s »%s«" %
> (self.filename, line)
> return False
>

The line was empty at that point. But it had already correctly read the
rest of the file by that stage...



>
> And just to be safe please provide the SHA256 sums of those files, e.g.:
> % $SHELL --version
> zsh 5.0.8 (x86_64-apple-darwin15.0)
> % for t in
> test/baseline/{cmd-price{s,db},feat-fixated-prices,opt-{datetime-format,gain,historical,market,price,revalued,time-report}}.test;
> do \
>   echo -n "$t: "; openssl dgst -sha256 < $t; \
> done | column -t
> test/baseline/cmd-prices.test:
>  dbee77184f7355ba172a672bd6ed21ffd3dfdc995508fdcfea8d7c61f13b4ff7
> test/baseline/cmd-pricedb.test:
> 

Re: Ledger 3.1.1 release candidate

[Sharon Kimble]

Alexis  writes:

> Hello Sharon,
> I'm uncertain about what is going on.
>
> The commit you mentioned:
>> v3.1-464-gfd6fabb
>
> I cannot find it within the ledger repository.
> Could it be that there are changes local to your repository?
>
>> Seeing the link you gave I can see immediately why it failed, I don't
>> have anything labelled as a "liability"! I have one credit card with no
>> debts on it, and no payments being made to it, hence no liabilities.
>
> Maybe running the following command sheds some light onto the issue:
> % git log  git log test/baseline/feat-fixated-prices.test
>
> In the meantime I'll try to reproduce the issue
> with a virtualized Debian 8 on my side.
>
--8<---cut here---start->8---
git log test/baseline/feat-fixated-prices.test
commit 8d6bf11334562d7781b339cf822a93ff42fee2b5
Author: John Wiegley 
Date:   Mon Mar 5 01:48:21 2012 -0600

All tests are working again but one

commit 9c62463f84dc398b41b387fbacce31abed7e4839
Author: John Wiegley 
Date:   Sat Feb 12 17:31:49 2011 -0500

Changed testing format to aid with debugging

commit 61f11bab1791dc0d0a308750f26414662e6f654d
Author: John Wiegley 
Date:   Sat Feb 12 16:45:49 2011 -0500

Removed needless "=== 0" and ">>>2" lines from test files

commit 0648c2f6dccb5c56e66d50a255177c92e46d5fea
Author: John Wiegley 
Date:   Tue Jun 22 21:03:04 2010 -0400

Extended feat-fixated-prices.test

commit 9c5c1eb7763d4bc38a6be579da03c349fb35e93d
Author: John Wiegley 
Date:   Sat Jun 13 17:42:24 2009 +0100

Renamed the fixated-prices test
--8<---cut here---end--->8---

Nope, I haven't done any hacking on ledger, I'm just grateful that it
works so well. I've put the most recent commits that "mr" has picked up
when it last checked at the very end. 

Thanks
Sharon.

--8<---cut here---start->8---
[boudiccas:Mon Sep 21 18:38:05 @~/git/ledger]$ [10337]>; git log
commit fd6fabbedcea479b2af7c166bb977ac51c317317
Merge: 88ad616 075ac7d
Author: Alexis Hildebrandt 
Date:   Sat Sep 19 20:38:56 2015 +0200

Merge pull request #430 from thdox/documentation

Documentation

[ci skip]

commit 075ac7d4d01e9b317540e7d2d6de92b2848afee0
Author: thdox 
Date:   Fri Sep 18 20:51:33 2015 +0200

Restoring @code as this is an keyword external to ledger itself.

commit 3e605f677fcfaa3bec83b9c770f386428ab9d902
Author: thdox 
Date:   Fri Sep 18 20:43:00 2015 +0200

For consistency with description of --subtotal that is line 7067.

commit 76379c4886e7420ce8954b845ec85d3bc01f7591
Author: thdox 
Date:   Fri Sep 18 20:34:59 2015 +0200

Bring back UNDOCUMENTED tag as the CODE has not yet been documented.

commit 88ad616d18b69eb03bc14eaa9ce6b32be90867a6
Merge: 36de186 92aead0
Author: Craig Earls 
Date:   Fri Sep 18 06:51:18 2015 -0700

Merge pull request #429 from paulbdavis/fontify-recurring

Wow!  Thank you.  I didn't know anyone was using this feature besides 
myself.

commit 92aead05ffba1966216e0cb40bf0ae192f001747
Author: paulbdavis 
Merge: 88ad616 075ac7d
Author: Alexis Hildebrandt 
Date:   Sat Sep 19 20:38:56 2015 +0200

Merge pull request #430 from thdox/documentation

Documentation

[ci skip]

commit 075ac7d4d01e9b317540e7d2d6de92b2848afee0
Author: thdox 
Date:   Fri Sep 18 20:51:33 2015 +0200

Restoring @code as this is an keyword external to ledger itself.

commit 3e605f677fcfaa3bec83b9c770f386428ab9d902
Author: thdox 
Date:   Fri Sep 18 20:43:00 2015 +0200

For consistency with description of --subtotal that is line 7067.

commit 76379c4886e7420ce8954b845ec85d3bc01f7591
Author: thdox 
Date:   Fri Sep 18 20:34:59 2015 +0200

Bring back UNDOCUMENTED tag as the CODE has not yet been documented.

commit 88ad616d18b69eb03bc14eaa9ce6b32be90867a6
Merge: 36de186 92aead0
Author: Craig Earls 
Date:   Fri Sep 18 06:51:18 2015 -0700

Merge pull request #429 from paulbdavis/fontify-recurring

Wow!  Thank you.  I didn't know anyone was using this feature besides 
myself.

commit 92aead05ffba1966216e0cb40bf0ae192f001747
Author: paulbdavis 
:

--8<---cut here---end--->8---

-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.0, fluxbox 1.3.7, emacs 24.5.50.3

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc

Re: Ledger 3.1.1 release candidate

[Alexis]

Hello Sharon,
I'm uncertain about what is going on.

The commit you mentioned:
> v3.1-464-gfd6fabb

I cannot find it within the ledger repository.
Could it be that there are changes local to your repository?

> Seeing the link you gave I can see immediately why it failed, I don't
> have anything labelled as a "liability"! I have one credit card with no
> debts on it, and no payments being made to it, hence no liabilities.

Maybe running the following command sheds some light onto the issue:
% git log  git log test/baseline/feat-fixated-prices.test

In the meantime I'll try to reproduce the issue
with a virtualized Debian 8 on my side.


Cheers,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[Alexis]

Hello Sharon,
just a quick update from my side.

I ran the tests on a Debian 8 in a VirtualBox on my workstation.
All tests passed except one DocTests (namely 82150D9) and I
assume it failed due to an encoding error.

The tests uses the Euro-Sign ('€'), yet I had set LC_ALL to C,
in order to work around another issue in Boost facets.


Cheers,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[Alexis]

Hello Bruce,
> Here's the output for all of the failing tests. Not sure what's going on
> with the "WARNING: Empty testfile detected" errors.

I've added the code below to test/RegressTests.py a little while ago:
  line = self.fd.readline() # self.fd is a file object created with open()
  if not line:
print >>sys.stderr, "WARNING: Empty testfile detected: %s" % (self.filename)
return False

I thought it would only fail for testfiles that are empty,
as it seems that is not the case.

I wonder what readline() returns that the `if not line:` test succeeds,
even though the file isn't empty.

In a previous message you mentioned Python 2.7.10 is used on Cygwin,
I use the same version on Mac OS X 10.11 El Capitan, yet I do not see
the issues.

Maybe you could rerun the tests with the following slight modification
of test/RegressTests.py to aid in debugging:
  line = self.fd.readline() # self.fd is a file object created with open()
  if not line:
print >>sys.stderr, "WARNING: Empty testfile detected: %s »%s«" % 
(self.filename, line)
return False

And just to be safe please provide the SHA256 sums of those files, e.g.:
% $SHELL --version
zsh 5.0.8 (x86_64-apple-darwin15.0)
% for t in 
test/baseline/{cmd-price{s,db},feat-fixated-prices,opt-{datetime-format,gain,historical,market,price,revalued,time-report}}.test;
 do \
  echo -n "$t: "; openssl dgst -sha256 < $t; \
done | column -t
test/baseline/cmd-prices.test:   
dbee77184f7355ba172a672bd6ed21ffd3dfdc995508fdcfea8d7c61f13b4ff7
test/baseline/cmd-pricedb.test:  
e6e8ca3e914ae90ca34b9f4ca32075af456b2526a41a7882bb6cf5bc11d9b45c
test/baseline/feat-fixated-prices.test:  
0d7040bd96d527345c890b3844382893afecece997957291de2208c053c56fd5
test/baseline/opt-datetime-format.test:  
2acaef081ad742ae1ad05544e08ad863ed539599d717e5195ef15c9beebae3b3
test/baseline/opt-gain.test: 
36b11c393ee915cedcbf7c9d6eafdbce3c22c30e0cc68f0e4810926ebfec4155
test/baseline/opt-historical.test:   
6a408b24917e409fdf18745f708eaa7e94b3ed95700cc9e98ae9c0194b7823bf
test/baseline/opt-market.test:   
110ce3bf772460149b4832090b630fc71df55bdd54ef1fa38daf76ed1f6cb6c1
test/baseline/opt-price.test:
0dad7401c8e28bf9a604c5f2cab52a4ed9c4ea61827a519649b3979c0ddaf8f0
test/baseline/opt-revalued.test: 
e8792ae0bc1b47e4d2d76851a122944be7d89eb65a2be0493b227be1c4337d72
test/baseline/opt-time-report.test:  
87582cbb559735558bc9041ab53517d4f8e187bafa550fe41843bdd0935cbbcd

>  - the sort order for pricedb is different (I tried changing the input
> order, but the output came out in a different order again)

I've seen this happen in Travis CI too.
Who has an idea what might be happening here?

>  - the time report output has an extra line with a single *

That's odd. If timelog entries are cleared, using a capital oh ('O')
for the check-out time,they are marked with an asterisk ('*') in the output.
But none of the entries in the opt-datetime-format.test are cleared.

Basically the --time-report option is just an alias for the
--balance-format option with a pre-defined format string.
The code can be found in src/report.h:973 (ff).

I'm doing some experiments to get a better idea what might be going wrong.


Cheers,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[Sharon Kimble]

Alexis  writes:

> Hello Sharon,
> thank you for you report.
>
>> Built and 'sudo make install' and tests done on a stock default debian
>> jessie and passed all tests except one
>
> What did you exactly build?  The following commands might be helpful:
> % git rev-parse --short HEAD
> % git describe
>
I built ledger from a git clone of the source git repo, and updated
daily with "mr" since I downloaded on 16/9/15. I have not built ledger
since my initial build. 

--8<---cut here---start->8---
git describe
v3.1-464-gfd6fabb
--8<---cut here---end--->8---


>> WARNING: Empty testfile detected: 
>> /home/boudiccas/git/ledger/test/baseline/feat-fixated-prices.test
>
> That's odd, on my side (git revision 88ad616) the file is 731 bytes
> in size and its SHA256 is:
> 0d7040bd96d527345c890b3844382893afecece997957291de2208c053c56fd5
>
> Here's a link to what it should look like:
> https://github.com/ledger/ledger/blob/next/test/baseline/feat-fixated-prices.test
>
>
> Best,
> Alexis

Seeing the link you gave I can see immediately why it failed, I don't
have anything labelled as a "liability"! I have one credit card with no
debts on it, and no payments being made to it, hence no liabilities.

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.0, fluxbox 1.3.7, emacs 24.5.50.3

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: Ledger 3.1.1 release candidate

[Alexis]

Hello Sharon,
thank you for you report.

> Built and 'sudo make install' and tests done on a stock default debian
> jessie and passed all tests except one

What did you exactly build?  The following commands might be helpful:
% git rev-parse --short HEAD
% git describe

> WARNING: Empty testfile detected: 
> /home/boudiccas/git/ledger/test/baseline/feat-fixated-prices.test

That's odd, on my side (git revision 88ad616) the file is 731 bytes
in size and its SHA256 is:
0d7040bd96d527345c890b3844382893afecece997957291de2208c053c56fd5

Here's a link to what it should look like:
https://github.com/ledger/ledger/blob/next/test/baseline/feat-fixated-prices.test


Best,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[Bruce Schultz]

On Wed, Sep 16, 2015 at 1:45 PM, Bruce Schultz  wrote:

>
>
> On Wed, Sep 16, 2015 at 12:29 PM, Alexis  wrote:
>
>> Hello Bruce,
>> thank you for the report!
>>
>> > 92% tests passed, 28 tests failed out of 353
>>
>> Not too bad, yet there seems to be room improvement :)
>>
>> > The python support is broken (running ledger python gives a segfault) so
>> > I'm not surprised by the _py test failures
>>
>> Which Python version do you use?
>> Currently only Python 2.x is supported.
>>
>
> Python 2.7.10 (python 2 is default on cygwin)
>
>
>> Can you provide a stacktrace?
>> It would be interesting to see what is going on.
>>
>
> I will have a play with gdb & see how I go. Will get back if I run into
> difficulty.
>

I haven't been able to get anything meaningful on this. I've rebuilt
without the python stuff for now


>
>
>> > How do I run individual tests to investigate further?
>>
>> To run individual tests use:
>> % ctest --output-on-failure -R ${REGEX_FOR_TESTS_TO_RUN_HERE}
>
>
Here's the output for all of the failing tests. Not sure what's going on
with the "WARNING: Empty testfile detected" errors. All of the reported
files which I've checked have looked valid, definitely not empty. The other
failures fall into 2 categories:

 - the sort order for pricedb is different (I tried changing the input
order, but the output came out in a different order again)
 - the time report output has an extra line with a single *


$ ctest --output-on-failure -R
'cmd-price(s|db)|feat-fixated-prices|opt-(datetime-format|gain|historical|market|price|revalued|time-report)|14DB77E7|3FE26304|7C44010B|999-b|9E0E606D|9EB10714|EA18D948'
Test project /c/Users/schultzb/src/ledger
  Start  29: BaselineTest_cmd-pricedb
 1/21 Test  #29: BaselineTest_cmd-pricedb ...***Failed0.51 sec

FAILURE in output from
/c/Users/schultzb/src/ledger/test/baseline/cmd-pricedb.test:
--
$ledger -f "/c/Users/schultzb/src/ledger/test/baseline/cmd-pricedb.test"
pricedb
--
  @@ -1,3 +1,3 @@
  +P 2012/01/03 00:00:00 EUR 1.316667 USD
   P 2012/01/02 00:00:00 GBP 1.20 EUR
  -P 2012/01/03 00:00:00 EUR 1.316667 USD
   P 2012/01/04 00:00:00 USD 0.63 GBP
E[cmd-pricedb.test]STDERR:


OK (4)  FAILED (1)

  Start  31: BaselineTest_cmd-prices
 2/21 Test  #31: BaselineTest_cmd-prices ***Failed0.49 sec

FAILURE in output from
/c/Users/schultzb/src/ledger/test/baseline/cmd-prices.test:
--
$ledger -f "/c/Users/schultzb/src/ledger/test/baseline/cmd-prices.test"
prices
--
  @@ -1,3 +1,3 @@
  +2012/01/03 EUR  1.316667 USD
   2012/01/02 GBP  1.20 EUR
  -2012/01/03 EUR  1.316667 USD
   2012/01/04 USD  0.63 GBP
E[cmd-prices.test]STDERR:


OK (4)  FAILED (1)

  Start  57: BaselineTest_feat-fixated-prices
 3/21 Test  #57: BaselineTest_feat-fixated-prices ...***Failed0.52 sec

E[feat-fixated-prices.test]
FAILED (1)
WARNING: Empty testfile detected:
/c/Users/schultzb/src/ledger/test/baseline/feat-fixated-prices.test

  Start 100: BaselineTest_opt-datetime-format
 4/21 Test #100: BaselineTest_opt-datetime-format ...***Failed0.53 sec

FAILURE in output from
/c/Users/schultzb/src/ledger/test/baseline/opt-datetime-format.test:
--
$ledger -f
"/c/Users/schultzb/src/ledger/test/baseline/opt-datetime-format.test" bal
--time-report --datetime-format '%m/%d/%y %I:%M %p'
--
  @@ -5,4 +5,4 @@
 04/05/13 12:00 PM04/05/13 01:30 PM   1.50hLunch
 04/05/13 11:30 AM04/05/13 12:00 PM   30.0mWalk
   --
  -
  +  *
E[opt-datetime-format.test]STDERR:


FAILED (1)

  Start 126: BaselineTest_opt-gain
 5/21 Test #126: BaselineTest_opt-gain ..***Failed0.77 sec

E[opt-gain.test]..
OK (2)  FAILED (1)

  Start 130: BaselineTest_opt-historical
 6/21 Test #130: BaselineTest_opt-historical ***Failed3.72 sec

E[opt-historical.test]
E[opt-historical.test]..
E[opt-historical.test]
E[opt-historical.test]..
OK (20)  FAILED (4)
WARNING: Empty testfile detected:
/c/Users/schultzb/src/ledger/test/baseline/opt-historical.test

  Start 145: BaselineTest_opt-market
 7/21 Test #145: BaselineTest_opt-market ***Failed0.49 sec

E[opt-market.test]
FAILED (1)
WARNING: Empty testfile detected:
/c/Users/schultzb/src/ledger/test/baseline/opt-market.test

  Start 172: BaselineTest_opt-price-db
 8/21 Test #172: BaselineTest_opt-price-db ..   Passed0.30 sec
  Start 173: BaselineTest_opt-price
 9/21 Test #173: BaselineTest_opt-price .***Failed1.21 sec
..
E[opt-price.test]
E[opt-price.test].
OK (3)  FAILED (2)
WARNING: Empty testfile detected:
/c/Users/schultzb/src/ledger/test/baseline/opt-price.test

  Start 174: BaselineTest_opt-pricedb-format
10/21 Test #174: BaselineTest_opt-pricedb-format    Passed0.31 sec
  Start 175: BaselineTest_opt-prices-format
11/21 

Re: Ledger 3.1.1 release candidate

[Sharon Kimble]

Alexis  writes:

> Hi everyone,
> ledger has seen several improvements and lately also some bitrot
> (especially with newer boost version, namely 1.58 and 1.59).
>
> So I think a new release is in order.
>
> I pushed the latest changes to the next and the release/3.1.1 branch
> and kindly ask that anyone willing to spend some time and effort
> test those changes and report any issues.
>
> Hopefully there are no (or only minor) issues and we can publish
> ledger 3.1.1 by the end of September.
>
> To test ledger please:
>   * build the release/3.1.1 branch
>   * run the tests (make test)
>   * do your own test with your personal workflow
>   * report success or any issues to this mailing list,
> be sure to include the operating system,
> boost version, and build output
>

Built and 'sudo make install' and tests done on a stock default debian
jessie and passed all tests except one

--8<---cut here---start->8---
99% tests passed, 1 tests failed out of 344

Total Test time (real) =  81.53 sec

The following tests FAILED:
191 - BaselineTest_feat-fixated-prices (Failed)
Errors while running CTest
Makefile:137: recipe for target 'test' failed
make: *** [test] Error 8
--8<---cut here---end--->8---

and then run with 'ctest --output-on-failure
Test project /home/boudiccas/git/ledger'

and it failed on the same test number with this error message

--8<---cut here---start->8---
Start 191: BaselineTest_feat-fixated-prices
191/344 Test #191: BaselineTest_feat-fixated-prices ***Failed
0.15 sec

WARNING: Empty testfile detected: 
/home/boudiccas/git/ledger/test/baseline/feat-fixated-prices.test
E[feat-fixated-prices.test]
FAILED (1)
--8<---cut here---end--->8---

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.0, fluxbox 1.3.7, emacs 24.5.50.3

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: Ledger 3.1.1 release candidate

[Alexis]

Hello Bruce,
thank you for the report!

> 92% tests passed, 28 tests failed out of 353

Not too bad, yet there seems to be room improvement :)

> The python support is broken (running ledger python gives a segfault) so
> I'm not surprised by the _py test failures

Which Python version do you use?
Currently only Python 2.x is supported.

Can you provide a stacktrace?
It would be interesting to see what is going on.

> How do I run individual tests to investigate further?

To run individual tests use:
% ctest --output-on-failure -R ${REGEX_FOR_TESTS_TO_RUN_HERE}

To see which tests would be run add the -N flag, e.g.:
% ctest --output-on-failure -R BaselineTest_feat -N
Test project /Volumes/Users/afh/src/ledger/build
  Test #52: BaselineTest_feat-annotations
  Test #53: BaselineTest_feat-balance-assignments
  Test #54: BaselineTest_feat-balance_assert-off
  Test #55: BaselineTest_feat-balance_assert
  Test #56: BaselineTest_feat-balance_assert_split
  Test #57: BaselineTest_feat-check
  Test #58: BaselineTest_feat-convert-with-directives
  Test #59: BaselineTest_feat-fixated-prices
  Test #60: BaselineTest_feat-import_py
  Test #61: BaselineTest_feat-option_py
  Test #62: BaselineTest_feat-value-expr
  Test #63: BaselineTest_feat-value_py

Total Tests: 12


Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[Bruce Schultz]

On Wed, Sep 16, 2015 at 12:29 PM, Alexis  wrote:

> Hello Bruce,
> thank you for the report!
>
> > 92% tests passed, 28 tests failed out of 353
>
> Not too bad, yet there seems to be room improvement :)
>
> > The python support is broken (running ledger python gives a segfault) so
> > I'm not surprised by the _py test failures
>
> Which Python version do you use?
> Currently only Python 2.x is supported.
>

Python 2.7.10 (python 2 is default on cygwin)


> Can you provide a stacktrace?
> It would be interesting to see what is going on.
>

I will have a play with gdb & see how I go. Will get back if I run into
difficulty.


> > How do I run individual tests to investigate further?
>
> To run individual tests use:
> % ctest --output-on-failure -R ${REGEX_FOR_TESTS_TO_RUN_HERE}
>
>
Ok, baby steps here... If I am interpreting this correctly, the output is
out of order:

$ ctest --output-on-failure -R cmd-price
Test project /c/Users/schultzb/src/ledger
Start 29: BaselineTest_cmd-pricedb
1/3 Test #29: BaselineTest_cmd-pricedb .***Failed0.48 sec

FAILURE in output from
/c/Users/schultzb/src/ledger/test/baseline/cmd-pricedb.test:
--
$ledger -f "/c/Users/schultzb/src/ledger/test/baseline/cmd-pricedb.test"
pricedb
--
  @@ -1,3 +1,3 @@
  +P 2012/01/03 00:00:00 EUR 1.316667 USD
   P 2012/01/02 00:00:00 GBP 1.20 EUR
  -P 2012/01/03 00:00:00 EUR 1.316667 USD
   P 2012/01/04 00:00:00 USD 0.63 GBP
E[cmd-pricedb.test]STDERR:


OK (4)  FAILED (1)

Start 30: BaselineTest_cmd-pricemap
2/3 Test #30: BaselineTest_cmd-pricemap    Passed0.30 sec
Start 31: BaselineTest_cmd-prices
3/3 Test #31: BaselineTest_cmd-prices ..***Failed0.50 sec

FAILURE in output from
/c/Users/schultzb/src/ledger/test/baseline/cmd-prices.test:
--
$ledger -f "/c/Users/schultzb/src/ledger/test/baseline/cmd-prices.test"
prices
--
  @@ -1,3 +1,3 @@
  +2012/01/03 EUR  1.316667 USD
   2012/01/02 GBP  1.20 EUR
  -2012/01/03 EUR  1.316667 USD
   2012/01/04 USD  0.63 GBP
E[cmd-prices.test]STDERR:


OK (4)  FAILED (1)


33% tests passed, 2 tests failed out of 3

Total Test time (real) =   1.31 sec

The following tests FAILED:
 29 - BaselineTest_cmd-pricedb (Failed)
 31 - BaselineTest_cmd-prices (Failed)
Errors while running CTest

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[Bruce Schultz]

I got the following test results on cygwin:

$ make test
...
92% tests passed, 28 tests failed out of 353

Total Test time (real) = 145.29 sec

The following tests FAILED:
 29 - BaselineTest_cmd-pricedb (Failed)
 31 - BaselineTest_cmd-prices (Failed)
 48 - BaselineTest_dir-import_py (Failed)
 50 - BaselineTest_dir-python_py (Failed)
 59 - BaselineTest_feat-fixated-prices (Failed)
 60 - BaselineTest_feat-import_py (Failed)
 61 - BaselineTest_feat-option_py (Failed)
 63 - BaselineTest_feat-value_py (Failed)
105 - BaselineTest_opt-datetime-format (Failed)
131 - BaselineTest_opt-gain (Failed)
135 - BaselineTest_opt-historical (Failed)
150 - BaselineTest_opt-market (Failed)
178 - BaselineTest_opt-price (Failed)
190 - BaselineTest_opt-revalued-only (Failed)
191 - BaselineTest_opt-revalued (Failed)
202 - BaselineTest_opt-time-report (Failed)
240 - RegressTest_14DB77E7 (Failed)
256 - RegressTest_3FE26304 (Failed)
260 - RegressTest_4D9288AE_py (Failed)
289 - RegressTest_786A3DD0 (Failed)
290 - RegressTest_78AB4B87_py (Failed)
292 - RegressTest_7C44010B (Failed)
303 - RegressTest_9188F587_py (Failed)
307 - RegressTest_999-b (Failed)
308 - RegressTest_9E0E606D (Failed)
309 - RegressTest_9EB10714 (Failed)
346 - RegressTest_EA18D948 (Failed)
353 - RegressTest_xact_code_py (Failed)
Errors while running CTest
Makefile:72: recipe for target 'test' failed
make: *** [test] Error 8

The python support is broken (running ledger python gives a segfault) so
I'm not surprised by the _py test failures

$ uname -a
CYGWIN_NT-6.1 31569L 2.2.1(0.289/5/3) 2015-08-20 11:42 x86_64 Cygwin

Boost is 1.57

How do I run individual tests to investigate further?

Bruce


On Wed, Sep 16, 2015 at 1:17 AM, Alexis  wrote:

> Hi everyone,
> ledger has seen several improvements and lately also some bitrot
> (especially with newer boost version, namely 1.58 and 1.59).
>
> So I think a new release is in order.
>
> I pushed the latest changes to the next and the release/3.1.1 branch
> and kindly ask that anyone willing to spend some time and effort
> test those changes and report any issues.
>
> Hopefully there are no (or only minor) issues and we can publish
> ledger 3.1.1 by the end of September.
>
> To test ledger please:
>   * build the release/3.1.1 branch
>   * run the tests (make test)
>   * do your own test with your personal workflow
>   * report success or any issues to this mailing list,
> be sure to include the operating system,
> boost version, and build output
>
>
> Thanks,
> Alexis
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Ledger" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ledger-cli+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ledger 3.1.1 release candidate

[Alexis]

Hi everyone,
ledger has seen several improvements and lately also some bitrot
(especially with newer boost version, namely 1.58 and 1.59).

So I think a new release is in order.

I pushed the latest changes to the next and the release/3.1.1 branch
and kindly ask that anyone willing to spend some time and effort
test those changes and report any issues.

Hopefully there are no (or only minor) issues and we can publish
ledger 3.1.1 by the end of September.

To test ledger please:
  * build the release/3.1.1 branch
  * run the tests (make test)
  * do your own test with your personal workflow
  * report success or any issues to this mailing list,
be sure to include the operating system,
boost version, and build output


Thanks,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ledger 3.1.1 release candidate

[John Wiegley]

> Alexis   writes:

> I pushed the latest changes to the next and the release/3.1.1 branch and
> kindly ask that anyone willing to spend some time and effort test those
> changes and report any issues.

Thank you, Alexis!

John

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.