Re: [GNC] Test

> On Apr 24, 2024, at 00:37, ed...@billiau.net wrote: > > On Wed, 24 Apr 2024 17:30:29 +1000 > Liz wrote: > >> Testing Gnucash-dev for a reply. >> > > Good news, Derek has managed to unjam gnucash-devel. > He may be able to let us know what happened, but I found myself > unsubscribed, and

Re: Test

On Wed, 24 Apr 2024 17:30:29 +1000 Liz wrote: > Testing Gnucash-dev for a reply. > Good news, Derek has managed to unjam gnucash-devel. He may be able to let us know what happened, but I found myself unsubscribed, and that may have happened to others as well. If you can't post to

Test

Testing Gnucash-dev for a reply. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Test failure on current master branch

Got a chance to test this yesterday. Your change fixed it indeed. Regards, Geert Op donderdag 2 maart 2023 21:36:00 CET schreef John Ralls: > Found and fixed it. It turns out that string->number isn't locale-sensitive, > std::to_string is. I replaced it with ostringstream a

Re: [GNC-dev] Test failure on current master branch

figured out exactly where it goes wrong, but I did discover >> it's a locale related issue. For some reason this particular test has become >> locale sensitive. >> >> If I run the test as follows: >> LC_ALL=C ctest -V -R test-gnc-option-scheme-output >> it passes.

Re: [GNC-dev] Test failure on current master branch

y where it goes wrong, but I did discover > it's a locale related issue. For some reason this particular test has become > locale sensitive. > > If I run the test as follows: > LC_ALL=C ctest -V -R test-gnc-option-scheme-output > it passes. If however I do this: > LC_ALL

Re: [GNC-dev] Test failure on current master branch

I still haven't figured out exactly where it goes wrong, but I did discover it's a locale related issue. For some reason this particular test has become locale sensitive. If I run the test as follows: LC_ALL=C ctest -V -R test-gnc-option-scheme-output it passes. If however I do this: LC_ALL

Re: [GNC-dev] Test failure on current master branch

Geert, I can't replicate that, tried on Debian 10, Debian Unstable, and Arch. I'm installing a Fedora 37 VM but I'm out of time for today and won't get to the point of a test build of GnuCash. Regards, John Ralls > On Feb 28, 2023, at 2:07 PM, Geert Janssens > wrote: &

[GNC-dev] Test failure on current master branch

Hi, With the current master branch I get the following test failure: ctest --rerun-failed --output-on-failure Test project /home/janssege/Development/gnucash/master/build Start 120: test-gnc-option-scheme-output 1/1 Test #120: test-gnc-option-scheme-output ***Failed0.22 sec

[GNC-dev] Test failure on master

Hi, I ran our test suite a few moments ago and I get a test failure for the finance-quote related tests. Below is the relevant detail from the test logs: [ RUN ] GncQuotesTest.online_wiggle * 22:02:03 WARN [GncFQQuoteSource::GncFQQuoteSource()] No Alpha Vantage API key set, currency

Re: [GNC-dev] Unable to run test on mac os.

I've figured out what's going wrong with the three gncmodule tests but I don't know what to do about it. Those tests depend on some test modules and their fake implementation libraries that are built in libgnucash/gnc-module/test/(foo|bar|baz|misc-mods). The CMakeLists.txt in those directories

Re: [GNC-dev] Unable to run test on mac os.

>> haven't figured out what's wrong yet. >> Regards, >> John Ralls >>> On Mar 23, 2020, at 9:44 AM, Jean Laroche wrote: >>> >>> Yes, I wiped everything out, changed common/test-core/CMakeLists.txt and >>> reran the cmake command that creates th

Re: [GNC-dev] Unable to run test on mac os.

the modules they're supposed to load. It's not a dependency problem, the modules are built. I haven't figured out what's wrong yet. Regards, John Ralls On Mar 23, 2020, at 9:44 AM, Jean Laroche wrote: Yes, I wiped everything out, changed common/test-core/CMakeLists.txt and reran the cmake command

Re: [GNC-dev] Unable to run test on mac os.

. Regards, John Ralls > On Mar 23, 2020, at 9:44 AM, Jean Laroche wrote: > > Yes, I wiped everything out, changed common/test-core/CMakeLists.txt and > reran the cmake command that creates the xcode project. LMK if I can provide > more testing. I'm definitely not familiar w

Re: [GNC-dev] Unable to run test on mac os.

Yes, I wiped everything out, changed common/test-core/CMakeLists.txt and reran the cmake command that creates the xcode project. LMK if I can provide more testing. I'm definitely not familiar with cmake (only started using it at work in the past couple months). J. On 3/23/20 9:34 AM, John

Re: [GNC-dev] Unable to run test on mac os.

Jean, At this point the build messages from libgtest.a are more interesting because that's what we're trying to coerce Xcode into putting somewhere different. I trust that you started fresh from an empty build dir after changing common/test-core/CMakeLists.txt. Regards, John Ralls > On

Re: [GNC-dev] Unable to run test on mac os.

I tried your suggestion, modified common/test-core/CMakeLists.txt (in the src directory I assume). But I'm still getting the same issue trying to build check. Showing Recent Messages Ld /Users/Shari/gnucash-stable/build_xcode/bin/test-gnc-rational normal x86_64 cd /Users/Shari/gnucash

Re: [GNC-dev] Unable to run test on mac os.

> On Mar 22, 2020, at 2:53 PM, jean wrote: > > The RUN_TEST target runs the tests successfully except for 3: > > Showing Recent Messages > The following tests FAILED: >10 - test-app-utils (Failed) >68 - test-load-c (Failed) >71 - te

Re: [GNC-dev] Unable to run test on mac os.

> On Mar 22, 2020, at 2:48 PM, jean wrote: > > clang: error: no such file or directory: > '/Users/Shari/gnucash-stable/build_xcode/common/test-core/libgtest.a' > clang: error: no such file or directory: > '/Users/Shari/gnucash-stable/build_xcode/common/test-core/libgtest.a

Re: [GNC-dev] Unable to run test on mac os.

The RUN_TEST target runs the tests successfully except for 3: Showing Recent Messages The following tests FAILED: 10 - test-app-utils (Failed) 68 - test-load-c (Failed) 71 - test-agedver (Failed) So with the kludge of copying *.a files to the right location, I'm able

Re: [GNC-dev] Unable to run test on mac os.

target, which does build. Despite that, the same error occurs. clang: error: no such file or directory: '/Users/Shari/gnucash-stable/build_xcode/common/test-core/libgtest.a' clang: error: no such file or directory: '/Users/Shari/gnucash-stable/build_xcode/common/test-core/libgtest.a

[GNC-dev] Unable to run test on mac os.

Moving a discussion that started in GitHub. I'm currently unable to build check in xcode with the following error: Showing Recent Messages Ld /Users/Shari/gnucash-stable/build_xcode/bin/test-gnc-path-util normal x86_64 cd /Users/Shari/gnucash-stable/src/gnucash-git export

Re: [GNC-dev] [gnucash-de] Test gnucash-3.7-2019-10-13-git-3.7-131-g57e403b04+.setup.exe (Windows)

> On Oct 13, 2019, at 1:01 PM, Martin Preuss wrote: > > Hi, > > as you know there are hard to debug crashes with current Gnucash GIT > and branch-6 of AqBanking on Windows. These crashes don't seem to happen > under Linux or in other apps. > > Because of that I ran gnucash through valgrind

Re: [GNC-dev] [gnucash-de] Test gnucash-3.7-2019-10-13-git-3.7-131-g57e403b04+.setup.exe (Windows)

Hi, as you know there are hard to debug crashes with current Gnucash GIT and branch-6 of AqBanking on Windows. These crashes don't seem to happen under Linux or in other apps. Because of that I ran gnucash through valgrind (with your gnucash-valgrind script). Valgrind reports multiple problems

[GNC-dev] Test of AqBanking dialogs (DirectOFX etc.)

Dear AqBanking users (DirectOFX etc.) The dialogs were converted and I sent a separate mail already to the FinTS users on the german list. As there are other modules, too, I ask you to test them either on a current built from the Gnucash Git repo or a nightly Windows built [https

Re: [GNC-dev] Test

The mailman output queue got hung up during the upgrades and mail was being received but not sent. I restarted the queue runners and mail started flowing, but it took a while to clear out the queue. The queue was empty when I went to bed. -derek Sent using my mobile device. Please excuse any

Re: [GNC-dev] Test

On Sun, 03 Feb 2019 21:21:22 -0500 Derek Atkins wrote: > Testing mailman... > -derek It's fine, the spam is arriving in a normal fashion. Thanks for the efforts you are making to keep all running. Liz ___ gnucash-devel mailing list

[GNC-dev] Test

Testing mailman... -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ gnucash-devel mailing list gnucash-devel@gnucash.org

Re: [GNC-dev] Test failure

get-barchart > * dpkg etc > > and to revert to main branch: > > * git checkout maint > > Just a quick note before running out the door for the day.  It compiled and passed test 109 (with the 3.4 build patch in place).  I'm presuming you don't have the broken patch in th

Re: [GNC-dev] Test failure

;> On Jan 26, 2019, at 5:55 PM, Stephen M. Butler wrote: >>>>>> >>>>>> On 1/26/19 3:13 AM, Christopher Lam wrote: >>>>>>> Another experiment. Try prefix your build with "TZ=UTC " on current >>>>>>> maint.

Re: [GNC-dev] Test failure

dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/home/steve/Projects/GnuCash/gnucash' debian/rules:24: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Same error --

Re: [GNC-dev] Test failure

=UTC ninja check" >>>> TZ=UTC dpkg- -rfakeroot -b -uc >>>> >>>> >>>> >>>> End testing: Jan 27 01:47 UTC >>>> + exit 2 >>>> debian/rules:65: recipe for target 'override_dh_auto_test' failed >>>> make[1

Re: [GNC-dev] Test failure

Cash/gnucash' debian/rules:24: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Same error -- Test 109 that fails. This is with the patches for 3.4. I verified before Sabbath that 3.4 builds and passes the tes

Re: [GNC-dev] Test failure

nuCash/gnucash' >> debian/rules:24: recipe for target 'build' failed >> make: *** [build] Error 2 >> dpkg-buildpackage: error: debian/rules build subprocess returned exit >> status 2 >> >> Same error -- Test 109 that fails. >> >> >> This is w

Re: [GNC-dev] Test failure

arget 'build' failed > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build subprocess returned exit > status 2 > > Same error -- Test 109 that fails. > > > This is with the patches for 3.4. I verified before Sabbath that 3.4 > builds and passes the

Re: [GNC-dev] Test failure

Thank you Stephen for your results. It would seem that the test-transaction failure is caused by a faulty libicu-dev whereas my failure caused by some other issue related to Time zones. C On Sun., 27 Jan. 2019, 09:55 Stephen M. Butler On 1/26/19 3:13 AM, Christopher Lam wrote: > > A

Re: [GNC-dev] Test failure

turned exit status 2 Same error -- Test 109 that fails. This is with the patches for 3.4.  I verified before Sabbath that 3.4 builds and passes the tests.  Tried your test first thing this evening after git checkout maint and git pull.  I am at 3.4-43-g84d1c3645 which builds but doesn't pass the t

Re: [GNC-dev] Test failure

Another experiment. Try prefix your build with "TZ=UTC " on current maint. Eg if using ninja, it'll be "TZ=UTC ninja check" On Fri., 25 Jan. 2019, 11:52 Stephen M. Butler On 1/24/19 7:36 PM, Christopher Lam wrote: > > Revert is a git terminology, not a gnucash one. Welcome to version > >

Re: [GNC-dev] Test failure

On 1/24/19 7:36 PM, Christopher Lam wrote: > Revert is a git terminology, not a gnucash one. Welcome to version > control. That's the manual to which I referred.  It meant something else to my mind when I first saw your post.  But, after further thought, my previous thought was faulty. My first

Re: [GNC-dev] Test failure

wrote: > >> On 1/24/19 2:32 AM, Christopher Lam wrote: > >>> Stephen this bug is in 3.4 and was fixed in commit 95bee405c > >>> > >>> Could you try "git revert e31f4c3f9" as a test for your "31/12/70" > >>> test-transaction er

Re: [GNC-dev] Test failure

.4 and was fixed in commit 95bee405c >>> >>> Could you try "git revert e31f4c3f9" as a test for your "31/12/70" >>> test-transaction errors? >> >> That worked.  Thank you.  BTW, how did you find that it was fixed?  I >> ask, because there

Re: [GNC-dev] Test failure

is in 3.4 and was fixed in commit 95bee405c Could you try "git revert e31f4c3f9" as a test for your "31/12/70" test-transaction errors? That worked.  Thank you.  BTW, how did you find that it was fixed?  I ask, because there is another one: -rw-r--r-- 1 steve steve 461 Jan 23 1

Re: [GNC-dev] Test failure

On 1/24/19 2:32 AM, Christopher Lam wrote: > Stephen this bug is in 3.4 and was fixed in commit 95bee405c > > Could you try "git revert e31f4c3f9" as a test for your "31/12/70" > test-transaction errors? That worked.  Thank you.  BTW, how did you find th

Re: [GNC-dev] Test failure

Stephen this bug is in 3.4 and was fixed in commit 95bee405c Could you try "git revert e31f4c3f9" as a test for your "31/12/70" test-transaction errors? On 24/1/19 3:05 am, Stephen M. Butler wrote: Found this patch on the debian version for 3.4 Origin: upstream, http

[GNC-dev] Test failure

:28 -0500 Subject: tests: Fix a test failure in test-transaction.scm. With the New Year upon us, a test which was hard-coded to use 2018 now failed. Fixes issue #797008 (see: https://bugs.gnucash.org/show_bug.cgi?id=797008). * gnucash/report/standard-reports/test/test-transaction.scm: (trep-tests

Re: [GNC-dev] GNUCASH Test Data

Should be, via qof_session_begin() and qof_session_load(). It is indeed better for *unit tests* to use data tailored to the *function* under test. But unit tests should be in the same language as the code that their testing. Bindings should do broader integration tests, relying

Re: [GNC-dev] GNUCASH Test Data

There's a good idea, however, I am not sure that the datafile loading mechanism is exposed to python & scheme. If you analyze test-transaction.scm and test-commodity-utils.scm you'll see how each test will generate an in-memory datafile with customized data designed to test asp

Re: [GNC-dev] GNUCASH Test Data

Christoph, Yes, there are test XML files in libgnucash/backend/test/xml2 and libgnucash/backend/sql/test. I don’t think that any of them are comprehensive, but they’re a pretty good start. Regards, John Ralls > On Dec 4, 2018, at 8:50 PM, c.holterm...@gmx.de wrote: > > Hello all,

Re: [GNC-dev] GNUCASH Test Data

Hello all, just reading this. When I started to look into the unit tests for python I wondered if there was some test data to read. I thought it would make more sense to first test reading and then test writing. I wonderes if there was some example date that the c as well as the bindings could

Re: [GNC-dev] GNUCASH Test Data

/master/gnucash_books) so if you have something that may be useful in this respect... Did you already share something on GitHub? Sebastien On Sun, Nov 11, 2018, 03:05 David Cousens Chris Millsap, Chris Good > > There is some limited test and example data in the GnuCash sources > .../gnucas

Re: [GNC-dev] GNUCASH Test Data

Chris Millsap, Chris Good There is some limited test and example data in the GnuCash sources .../gnucash-src/doc/examples. Not very extensive. These days a lot of testing effort is shifted towards unit tests rather than extensive overall functional tests although they still have a place. I would

Re: [GNC-dev] GNUCASH Test Data

copied the developers mailing list. Thanks for the idea, Regards, Chris Good > On 11 Nov 2018, at 4:24 AM, Christopher Millsap > wrote: > > Hey everyone, I started working on a proof of concept for a program that > generates large amounts of test data (various account types

Re: [GNC-dev] gnucash maint: Fix gncInvoice test failure.

6c92d4 > Author: John Ralls > Date: Mon Aug 6 14:49:07 2018 -0700 > > Fix gncInvoice test failure. > > test_suite_gncInvoice sets up the test suite. It's not part of the test > runtime, so stack variables in it have gone out of scope by the time the > tests are

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

> On May 15, 2018, at 11:35 AM, Derek Atkins wrote: > > Hi, > > On Tue, May 15, 2018 1:09 pm, John Ralls wrote: >> >> >>> On May 15, 2018, at 8:03 AM, John Ralls wrote: >>> >>> Browse is broken, searching by component returns “zarro” even if there >>>

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

Interesting... From a non-developer perspective: When logging into gnome.bugzilla.org, the very first link in the center with the ‘circle icons’ is “My Bugs”. As well, in my footer, the *only* thing there is a link “My Bugs” on the left. Both link to the URL John provided. I watch some bugs,

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

Hi, On Tue, May 15, 2018 1:09 pm, John Ralls wrote: > > >> On May 15, 2018, at 8:03 AM, John Ralls wrote: >> >> Browse is broken, searching by component returns “zarro” even if there >> are bugs with that category. > > I figured out what's wrong with "browse": It creates a

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

> On May 15, 2018, at 8:03 AM, John Ralls wrote: > > Browse is broken, searching by component returns “zarro” even if there are > bugs with that category. I figured out what's wrong with "browse": It creates a search that sets Resolution = "---". Editing the search and

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

On Tue, May 15, 2018 11:03 am, John Ralls wrote: > > Browse is broken, searching by component returns “zarro” even if there are > bugs with that category. Are you sure? Browse appears to be working for me. It's just that the default only looks for open bugs, and all the bugs are closed so they

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

> On May 15, 2018, at 8:41 AM, Derek Atkins wrote: > > Hi, > > On Mon, May 14, 2018 11:10 pm, John Ralls wrote: > > I think I can do that. I suppose that means I need to look up the > category and determine who is the pseudo-user that each category. Should > I add the

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

gt;> On May 14, 2018, at 8:56 PM, Adrien Monteleone >> <adrien.montele...@lusfiber.net> wrote: >> >> I suppose you’re still revising things. >> >> Currently, I see components listed, but no bugs found. >> >> I also tried a password reset but never received t

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

John (et al), On Tue, May 15, 2018 11:41 am, Derek Atkins wrote: > Hi, > > On Mon, May 14, 2018 11:10 pm, John Ralls wrote: >> >> Derek, >> >> There are 67 GnuCash bugs in Gnome with something in the See Also field: >> >>

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

Hi, On Mon, May 14, 2018 11:10 pm, John Ralls wrote: > > Derek, > > There are 67 GnuCash bugs in Gnome with something in the See Also field: > > https://bugzilla.gnome.org/buglist.cgi?f1=see_also_id=310012=regexp=Bug%20Number=GnuCash_format=advanced=.%2B >

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

bugs found. > > I also tried a password reset but never received the email. > > Is this only for official developers to test right now, or anyone who has a > Gnome Bugzilla account and participated in bug reports? > > Regards, > Adrien > >> On May 14, 2018, at

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

I suppose you’re still revising things. Currently, I see components listed, but no bugs found. I also tried a password reset but never received the email. Is this only for official developers to test right now, or anyone who has a Gnome Bugzilla account and participated in bug reports

Re: [GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

> On May 14, 2018, at 2:00 PM, Derek Atkins <de...@ihtfp.com> wrote: > > Hi Everyone, > > tl;dr: I have a partial migration up and running (~105 / 8588 bugs) and I > think my migration script is "complete" -- please test. Also, please let > me

[GNC-dev] Bugzilla Migration Status -- phase 2 -- please test

Hi Everyone, tl;dr: I have a partial migration up and running (~105 / 8588 bugs) and I think my migration script is "complete" -- please test. Also, please let me know if you know of any bugs that use the see_also field. Long Version: As you all know, we use Gnome's bugzill

Re: Confusion around qof_instance editlevel and test-account-object

g the conversion some of the tests are failing. One of the > tests that I’m working on fixing is the test-account-object test. > > I’m currently getting the following test failures: > FAILURE end balance matches > /home/carwyn/gnucash/libgnucash/engine/test/test-account-object.cpp:78 &g

Confusion around qof_instance editlevel and test-account-object

is the test-account-object test. I’m currently getting the following test failures: FAILURE end balance matches /home/carwyn/gnucash/libgnucash/engine/test/test-account-object.cpp:78 FAILURE end2 balance matches /home/carwyn/gnucash/libgnucash/engine/test/test-account-object.cpp:80 From

Re: Travis test failure in test-import-map

On zaterdag 11 maart 2017 13:57:52 CEST Robert Fewell wrote: > For information I have added this to my test branch travis.yml file... > > after_failure: for file in $( find . -name 'test*.log' ); do echo -e > "\n## $file"$'\n\n'"$(cat -- "$file")" >

Re: Master gtest-gnc-datetime test fails.

t; >>> Built current master on my Linux VM and tried to run the tests but it >>> fails >>> on the following test, if they are commented out all other tests run >>> successfully. >>> >>> Checked my time zone information to be Europe/L

Re: Master gtest-gnc-datetime test fails.

On zaterdag 15 april 2017 16:15:00 CEST John Ralls wrote: > > On Apr 15, 2017, at 4:27 AM, Robert Fewell <14ubo...@gmail.com> wrote: > > > > Hi, > > > > Built current master on my Linux VM and tried to run the tests but it > > fails > > on the fol

Re: Master gtest-gnc-datetime test fails.

> On Apr 15, 2017, at 4:27 AM, Robert Fewell <14ubo...@gmail.com> wrote: > > Hi, > > Built current master on my Linux VM and tried to run the tests but it fails > on the following test, if they are commented out all other tests run > successfully. > >

Master gtest-gnc-datetime test fails.

Hi, Built current master on my Linux VM and tried to run the tests but it fails on the following test, if they are commented out all other tests run successfully. Checked my time zone information to be Europe/London I think the offset is the difference between local time and utc time, so

Re: Travis test failure in test-import-map

Yes, I have been looking with little success, in the past I have had no failures locally or on travis. This morning I decided to rerun the last travis test and it failed just like Geert's failure, but what I do not understand is that I have modified test-import-map to run more of the same test

Re: Travis test failure in test-import-map

On zaterdag 11 maart 2017 12:33:29 CET Geert Janssens wrote: > On vrijdag 10 maart 2017 21:44:53 CET John Ralls wrote: > > > On Mar 10, 2017, at 12:06 PM, Christoph R > > > <subscriptions+lis...@rohland.net> wrote: > > > > > > I did this,

Re: Travis test failure in test-import-map

On vrijdag 10 maart 2017 21:44:53 CET John Ralls wrote: > > On Mar 10, 2017, at 12:06 PM, Christoph R > > <subscriptions+lis...@rohland.net> wrote: > > > > I did this, but of course the test did not fail this time > > Yeah, I was watching it. Sigh. I

Re: Travis test failure in test-import-map

> On Mar 10, 2017, at 12:06 PM, Christoph R <subscriptions+lis...@rohland.net> > wrote: > > I did this, but of course the test did not fail this time Yeah, I was watching it. Sigh. Anyway, I'll leave the PR to Geert as I think he's already reviewed the changes. R

Re: Travis test failure in test-import-map

I did this, but of course the test did not fail this time Gruß, Christoph > Am 10.03.2017 um 20:37 schrieb John Ralls <jra...@ceridwen.us>: > >> >> On Mar 10, 2017, at 11:27 AM, Christoph R <subscriptions+lis...@rohland.net> >> wrote: >> >>

Re: Travis test failure in test-import-map

> On Mar 10, 2017, at 11:27 AM, Christoph R <subscriptions+lis...@rohland.net> > wrote: > > Hi, > > when creating a pull request against master to fix a bug in the taxinvoice > report I get a test failure in test-import-map. > > This does not seem to be

Travis test failure in test-import-map

Hi, when creating a pull request against master to fix a bug in the taxinvoice report I get a test failure in test-import-map. This does not seem to be at all related to my change. Can somebody confirm that? Cheers, Christoph ___ gnucash-devel

HBCI banking test

Hello all. I was trying to test HBCI with the instructions found here: https://lists.gnucash.org/pipermail/gnucash-devel/2005-January/012520.html But after entering the PIN I get in the log (copy from it does not work for me so I have to type) Waiting for response ...and then immediately

Re: HBCI banking test

I don't the test servers from the 2005 instructions are still operating. Sorry. Regards, Christian Am 10. Dezember 2015 19:23:12 MEZ, schrieb Per Johansson <p...@johansson.name>: >Hello all. > >I was trying to test HBCI with the instructions found here: >https://lists.gnu

Re: Compile test-core in C++

Mr. Rall's suggestion of #ifdef __cplusplus, but it seems cleaner to me to have a separate .hpp file for several reasons. and the original QofCollection_s is replaced with this new class. Module src/libqof/qof is compiled successfully, but failed to compile src/test-core due to C compiler

Re: Compile test-core in C++

understanding is correct. Just to be clear, the gtest (i.e., Google test) framework is for C++ tests. The gtester (GLib test) is C-only and will be upset if you try to feed it C++, as will the legacy tests which use the stuff in src/test-core other than unittest-support. Regards, John Ralls

Re: Compile test-core in C++

/qof is compiled successfully, but failed to compile src/test-core due to C compiler is the one used to compile, and src/test-core/unittest-support.h includes qof.h, then *includes qofid.h*. This is why I considered to compile src/unit-core to solve the problem. After guidance in previous mails from

Re: Compile test-core in C++

/qofid.h, and the original QofCollection_s is replaced with this new class. Module src/libqof/qof is compiled successfully, but failed to compile src/test-core due to C compiler is the one used to compile, and src/test-core/unittest-support.h includes qof.h, then *includes qofid.h*. This is why I

Re: Compile test-core in C++

On Wed, Nov 19, 2014 at 12:17 AM, John Ralls jra...@ceridwen.us wrote: On Nov 18, 2014, at 7:10 AM, Chenxiong Qi qcxh...@gmail.com wrote: Hi, I've converted QofCollection to a C++ class. A side-effect is that I have to make src/test-core be able to compile in C++. I'm an absolute newbie

Re: Compile test-core in C++

On Nov 20, 2014, at 5:37 AM, Chenxiong Qi qcxh...@gmail.com wrote: On Wed, Nov 19, 2014 at 12:17 AM, John Ralls jra...@ceridwen.us wrote: Why do you want to compile test-core in C++? src/test-core/unittest-support.h includes qof.h Lots of code includes qof.h. That's not a good reason

Re: Compile test-core in C++

On Thu, Nov 20, 2014 at 10:36 PM, John Ralls jra...@ceridwen.us wrote: On Nov 20, 2014, at 5:37 AM, Chenxiong Qi qcxh...@gmail.com wrote: On Wed, Nov 19, 2014 at 12:17 AM, John Ralls jra...@ceridwen.us wrote: Why do you want to compile test-core in C++? src/test-core/unittest-support.h

Re: Compile test-core in C++

On Thu, Nov 20, 2014 at 9:58 AM, Chenxiong Qi qcxh...@gmail.com wrote: Is it acceptable that I rename the new class to another name temporarily, such as QofCollectionClass, and keep the new class implementation and original one's existing simultaneously. I know this looks strange, but the

Re: Compile test-core in C++

want to compile test-core in C++? src/test-core/unittest-support.h includes qof.h Lots of code includes qof.h. That's not a good reason to migrate test-core to C++. Yup. also aware of this. As of writing these words, still not figure out a good way. Is it acceptable that I rename

Compile test-core in C++

Hi, I've converted QofCollection to a C++ class. A side-effect is that I have to make src/test-core be able to compile in C++. I'm an absolute newbie to autotools, still not get a workable solution so far after doing some research on this. Could you give some guide how to accomplish

Re: Compile test-core in C++

On Nov 18, 2014, at 7:10 AM, Chenxiong Qi qcxh...@gmail.com wrote: Hi, I've converted QofCollection to a C++ class. A side-effect is that I have to make src/test-core be able to compile in C++. I'm an absolute newbie to autotools, still not get a workable solution so far after doing

Re: Compile test-core in C++

On Tue, Nov 18, 2014 at 10:10 AM, Chenxiong Qi qcxh...@gmail.com wrote: Hi, I've converted QofCollection to a C++ class. A side-effect is that I have to make src/test-core be able to compile in C++. Although QofCollection will be a C++ class, you should be retaining the C interface

Re: gnucash master: Add some initial aqbanking test with example file that should demonstrate the hbci template kvp problem.

...@cstimming.de Date: Fri Aug 29 23:32:40 2014 +0200 Add some initial aqbanking test with example file that should demonstrate the hbci template kvp problem. Not yet working, though - the test, I mean. Hi Christian, I'm delighted you have found some time/energy again to work

Re: gnucash master: Better test for conflict between optimization and FORTIFY_SOURCE

) commit 8cb391b30846f04eb6b874ef6dde723be372b7d0 Author: John Ralls jra...@ceridwen.us Date: Fri May 2 14:02:24 2014 -0700 Better test for conflict between optimization and FORTIFY_SOURCE I pushed this to the maint branch too since the previous changes were there. Mike

Re: gnucash master: Better test for conflict between optimization and FORTIFY_SOURCE

/Gnucash/gnucash/commit/ac9a6ae6 (commit) commit 8cb391b30846f04eb6b874ef6dde723be372b7d0 Author: John Ralls jra...@ceridwen.us Date: Fri May 2 14:02:24 2014 -0700 Better test for conflict between optimization and FORTIFY_SOURCE I pushed

Re: gnucash master: Better test for conflict between optimization and FORTIFY_SOURCE

jra...@ceridwen.us Date: Fri May 2 14:02:24 2014 -0700 Better test for conflict between optimization and FORTIFY_SOURCE I pushed this to the maint branch too since the previous changes were there. Mike ___ gnucash-devel mailing list

Re: gnucash master: Better test for conflict between optimization and FORTIFY_SOURCE

) commit 8cb391b30846f04eb6b874ef6dde723be372b7d0 Author: John Ralls jra...@ceridwen.us Date: Fri May 2 14:02:24 2014 -0700 Better test for conflict between optimization and FORTIFY_SOURCE I pushed this to the maint branch too since the previous changes were there. OK, thanks

Re: gnucash master: Test git.

Il 03/02/2014 21.12, Geert Janssens ha scritto: Congratulations Cristian ! You have found your way into git :) Make yourself comfortable... Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org

  1   2   3   4   5   >