czt-devel

Re: [CZT-Devel] Building from CZT snapshot

[Andrius V. <and...@ne...>]

Dear Anthony,

The SectionManager did change - mostly internally (we added a support for
"transactions" as a step towards better incremental-checking of Z sections
- so that you could re-check only downstream dependencies without throwing
away all upstream ones). Note, however, that this change enforces a bit
stricter way of how it should be called - so let us assist if you encounter
problems regarding to it.

The change in SectionManager interface you encountered is that it now
explicitly requires to provide a dialect to use (see
net.sourceforge.czt.session.Dialect enum for appropriate values). So in
your case it would be `new SectionManager(Dialect.Z)` for Z checking.

You can generate the JavaDocs yourself by running `mvn javadoc:javadoc` for
some module. They will be put into `target/site/apidocs` of the project (I
think).

I know it is a bit annoying to manually have to generate all this. Since we
now have nightly builds, I think I will just put a "nightly" version of the
website as well - the current one has not been updated for 5 years! :(
 Then all the changes that we add would be reflected immediately. This way
all the up-to-date JavaDocs will also be online soon.

Let me know if there are any problems with the JavaDocs.

Best regards,
Andrius


On Mon, Apr 8, 2013 at 3:31 PM, Anthony Hall <an...@an...>wrote:

>    Part of Z Word tools is the cztinterface program which is built from
> the CZT snapshot. I last built it from CZT SVN Version 8214****
>
> ** **
>
> Now I’ve downloaded and built the latest CZT version from Git and I can no
> longer build cztinterface. I get an error “No suitable constructor found
> for SectionManager()” at a line that says ****
>
> SectionManager manager = new SectionManager();****
>
> ** **
>
> I seem to remember that the SectionManager was changed some time ago. Is
> there an up to date javadocs site that I can look at to see the
> documentation of the classes in the current version?****
>
> ** **
>
> Thanks****
>
> ** **
>
> Anthony****
>

Re: [CZT-Devel] Building from CZT snapshot

[Anthony H. <an...@an...>]

Dear Andrius

 

That is an interesting observation! I am reading myself online now that JUnit does run tests in an arbitrary order.. I did have the same assumption as you.

Bizarre, isn’t it? I particularly like the doctrinaire ignorance of “of course your tests should be totally independent” – what world do these people live in?

 

I am not sure if that is the case in VCG, but Leo's doing an overhaul of it at the moment so hopefully all such issues will be identified and resolved in the nearest future. Some of the flashing errors are corner cases for VCG which require some tuning (if I understand correctly), so they are ignored in the tests but are still producing verbose output at the moment. So that output can be ignored as long as the build does not fail.

Thanks – that’s good to know

 

How is the SectionManager running with the latest CZT version? Are you still getting transaction errors?

No, thank you. That was entirely the fault of maven. All seems well now. I only had to make the one change to the constructor call.

 

Many thanks for your help

 

Anthony

 

Best regards,

Andrius

 

 

On Tue, Apr 9, 2013 at 2:36 PM, Anthony Hall <an...@an...> wrote:

Thanks Andrius

 

I’ve changed the url 

 

When I rebuilt I again got VCG test errors. This time, however, when I tried again the build was successful, although a lot of errors flashed past during the VCG testing they seemed to be handled in some way that didn’t prevent the build working.

 

I’ve just discovered something horrible that may possibly throw light on that. I’m getting a similar problem with my own cztinterface build – tests are failing apparently randomly. The root cause in my case appears to be a feature of JUnit: within a suite it runs tests in whatever order it feels like (and its mood seems to change from run to run). I had assumed and relied on the fact that it ran them in the order I wrote them. I’m surprised that this hasn’t hit me before. Anyway, I wonder if that might be happening in the VCG case as well?

 

All the best

 

Anthony

 

 

From: Andrius Velykis [mailto:and...@ne...] 
Sent: 09 April 2013 13:57


To: Anthony Hall
Cc: CZT-Devel
Subject: Re: [CZT-Devel] Building from CZT snapshot

 

Dear Anthony,

 

On Tue, Apr 9, 2013 at 12:45 PM, Anthony Hall <an...@an...> wrote:

According to git config:

remote.origin.url=git://czt.git.sourceforge.net/gitroot/czt/czt

remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*

The url is what is given in setup.md 

 

 

Yes, sorry, this is the old CZT Git repository path. After the recent move to the new SourceForge platform, the Git repository addresses changed. The read-only access is now `git://git.code.sf.net/p/czt/code` <http://git.code.sf.net/p/czt/code%60> . For write access, check your personal link at http://sourceforge.net/p/czt/code/ when you are logged in to SourceForge.

 

Let me know if this gets the latest version for you. Here's some info on changing the Git remote URL: http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git

 

We will update the instructions accordingly. Sorry the about misleading instructions in setup.md - I forgot to update the documentation after the repository change.

 

Best regards,

Andrius

 


------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
CZT-Devel mailing list
CZT...@li...
https://lists.sourceforge.net/lists/listinfo/czt-devel

 

Re: [CZT-Devel] Building from CZT snapshot

[Tim M. <tm...@un...>]

On 10/04/13 03:18, Anthony Hall wrote:
> That is an interesting observation! I am reading myself online now that
> JUnit does run tests in an arbitrary order.. I did have the same
> assumption as you.
>
I knew that junit reserved the right to run tests in any order, but I 
did not realise it would change from run to run. Very strange. I can see 
the value in have random sequences: if you have independent tests, they 
should run in any order, so trying different sequences each time give 
you different tests; but one would think that should be an option you 
have to turn *on*, rather than off. That makes it incredibly hard to 
replicate when tests fail.

> Bizarre, isn’t it? I particularly like the doctrinaire ignorance of “of
> course your tests should be totally independent” – what world do these
> people live in?
>
Yes, a rule of thumb that is a worthwhile goal, but some people are too 
dogmatic about it -- the Junit authors especially.

TestNG supports test dependencies well. I also recall reading a while 
ago that someone had contributed something to Junit to do this, mainly 
to stop tests running if other tests has failed to prevent cascading 
failures. I don't have the details handy.

It's good to see some activity on this mailing list! And that a lot of 
work is still happening on the project :)

Cheers,
Tim

Re: [CZT-Devel] Building from CZT snapshot

[Mark U. <ma...@cs...>]

Anthony and Andrius,



On 10 April 2013 03:18, Anthony Hall <an...@an...> wrote:

> Dear Andrius****
>
> * *
>
> That is an interesting observation! I am reading myself online now that
> JUnit does run tests in an arbitrary order.. I did have the same assumption
> as you.****
>
> Bizarre, isn’t it? I particularly like the doctrinaire ignorance of “of
> course your tests should be totally independent” – what world do these
> people live in?
>

Actually, it is probably caused by Java 1.7 -- since build 129 of Java SE
the reflection method getMethods() returns the methods in a
non-deterministic order.  (Before that, it returned them in source code
order).  So if you've upgraded to Java 1.7, JUnit has no way of knowing the
original order of the methods any more.

Sun says this is a feature, not a bug. And
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7023180  says:

Filed a request for JUnit to behave predictably irrespective of VM
order: https://github.com/KentBeck/junit/pull/293

2011-09-09




I don't know if this has been implemented in JUnit yet.  I doubt it.
 (Presumably they would have to parse the source code of your Java).

I think relying on the order of test methods is bad style anyway, because
it makes it hard to tools to run tests in isolation, means that test suite
minimisation algorithms do not work, you cannot automatically reorder tests
to run the quick ones first, etc.

Cheers
Mark


*Area:* HotSpot
*Synopsis:* Order of Methods returned by Class.get Methods can Vary
*Description:* In JDK 7, build 129, the following reflective operations in
java.lang.Class changed the fixed order in which they return the methods
and constructors of a class:

   - getMethods
   - getDeclaredMethods
   - getDeclaredConstructors

This may cause issues for code that assumes (contrary to the specification)
a particular order for methods or constructors.

Re: [CZT-Devel] Building from CZT snapshot

[Anthony H. <an...@an...>]

-------------------------------------------------------------------------------
Test set: net.sourceforge.zwordtools.cztinterface.CZTCheckTest
-------------------------------------------------------------------------------
Tests run: 9, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: 0.732 sec <<< FAILURE!
testDBUNoErrors1(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.536 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUNoErrors1.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUNoErrors1.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testDBUNoErrors1(CZTCheckTest.java:43)
testUBDNoFlag(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.009 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\UBDNoErrors.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\UBDNoErrors.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testUBDNoFlag(CZTCheckTest.java:46)
testRecursiveNoFlag(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.038 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\Recursive.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\Recursive.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testRecursiveNoFlag(CZTCheckTest.java:52)
testDBUNoErrors(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.035 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUNoErrors.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUNoErrors.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testDBUNoErrors(CZTCheckTest.java:40)
testRecursiveFlag(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.001 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\Recursive.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\Recursive.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testRecursiveFlag(CZTCheckTest.java:55)
testMissingSectionInCurrent(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.025 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUWithoutStack.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUWithoutStack.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testMissingSectionInCurrent(CZTCheckTest.java:58)
testMissingSectionNoPath(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.024 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUWithoutStack1.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUWithoutStack1.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testMissingSectionNoPath(CZTCheckTest.java:61)
testMissingSectionWithPath(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.019 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUWithoutStack1.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\DBUWithoutStack1.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testMissingSectionWithPath(CZTCheckTest.java:67)
testUBDFlag(net.sourceforge.zwordtools.cztinterface.CZTCheckTest)  Time elapsed: 0.018 sec  <<< ERROR!
net.sourceforge.czt.session.SectionInfoException: There is an ongoing transaction for the given key
	Key............: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\UBDNoErrors.tex,ParseException)
	Transactions...: (D:\anthony\documents\fm\z\word\SVN\Current\cztinterface\target\test-classes\UBDNoErrors.tex,ParseException)
	at net.sourceforge.czt.session.SectionManager.assertNewTransaction(SectionManager.java:808)
	at net.sourceforge.czt.session.SectionManager.startTransaction(SectionManager.java:1014)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:978)
	at net.sourceforge.czt.session.SectionManager.put(SectionManager.java:966)
	at net.sourceforge.czt.parser.util.ParseExceptionCommand.compute(ParseExceptionCommand.java:36)
	at net.sourceforge.czt.session.SectionManager.get(SectionManager.java:1710)
	at net.sourceforge.czt.parser.z.Parser.<init>(Parser.java:2545)
	at net.sourceforge.czt.parser.z.LatexParser.<init>(LatexParser.java:55)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:60)
	at net.sourceforge.czt.parser.z.ParseUtils.parse(ParseUtils.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTCheck.main(CZTCheck.java:100)
	at net.sourceforge.zwordtools.cztinterface.CZTTestUtils.runTest(CZTTestUtils.java:82)
	at net.sourceforge.zwordtools.cztinterface.CZTCheckTest.testUBDFlag(CZTCheckTest.java:49)

Re: [CZT-Devel] Building from CZT snapshot

[Andrius V. <and...@ne...>]

Dear Anthony,

Thanks for the info. Which CZT sources are you using? I am looking at the
latest CZT source code and have problems matching your stack trace to my
code.. The calls that are made in your stack trace are non-existent in my
code :( Are you working on the `master` branch of the CZT Git repository?
Or are you using the nighly build czt.jar?

Best regards,
Andrius




On Mon, Apr 8, 2013 at 5:31 PM, Anthony Hall <an...@an...>wrote:

> Dear Andrius****
>
> ** **
>
> Thank you again for a very swift response****
>
> ** **
>
> The SectionManager did change - mostly internally (we added a support for
> "transactions" as a step towards better incremental-checking of Z sections
> - so that you could re-check only downstream dependencies without throwing
> away all upstream ones). Note, however, that this change enforces a bit
> stricter way of how it should be called - so let us assist if you encounter
> problems regarding to it.****
>
> ** **
>
> The change in SectionManager interface you encountered is that it now
> explicitly requires to provide a dialect to use (see
> net.sourceforge.czt.session.Dialect enum for appropriate values). So in
> your case it would be `new SectionManager(Dialect.Z)` for Z checking.****
>
> Thank you. I did that and it all compiled OK. However, now I seem to be
> running foul of the new transaction features, because I’m getting a lot of
> test failures of the form “SectionInfoException: There is an ongoing
> transaction for the given key”****
>
> Of course I’m not doing anything manually with transactions so I’ve really
> not got much clue as to how to fix this.****
>
> ** **
>
> The tests work be repeatedly calling the main procedure of my class, and
> that does a new SectionManager(Dialect.Z) each time. So I’m not sure what
> else I need to do. ****
>
> ** **
>
> I attach the main class (CZTCheck, the class that runs the test
> (CZTTestUtils), a failing test set and the surefire reports. If you could
> point me at what I need to do I’d be most grateful!****
>
> ** **
>
> You can generate the JavaDocs yourself by running `mvn javadoc:javadoc`
> for some module. They will be put into `target/site/apidocs` of the project
> (I think).****
>
> That seems to work, yes – though I got a lot of warnings like****
>
> [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
> missing, no dependency information available****
>
> [WARNING] Failed to retrieve plugin descriptor for
> org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
> org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
> not be resolved: Failed to read artifact descriptor for
> org.eclipse.m2e:lifecycle-mapping:jar:1.0.0****
>
> but I don’t know whether that matters****
>
> ** **
>
> And of course I have had a look at the SectionManager apidocs but it looks
> as if I shouldn’t have to do anything explicit unless I’m trying to do
> something clever with incremental compilation – or have I missed something
> there?****
>
> ** **
>
> I know it is a bit annoying to manually have to generate all this. Since
> we now have nightly builds, I think I will just put a "nightly" version of
> the website as well - the current one has not been updated for 5 years! :(
>  Then all the changes that we add would be reflected immediately. This way
> all the up-to-date JavaDocs will also be online soon.****
>
> I think that would be *really* helpful – great!****
>
> ** **
>
> Many thanks****
>
> ** **
>
> Anthony****
>
> ** **
>
> Let me know if there are any problems with the JavaDocs.****
>
> ** **
>
> Best regards,****
>
> Andrius****
>
> ** **
>
> On Mon, Apr 8, 2013 at 3:31 PM, Anthony Hall <an...@an...>
> wrote:****
>
> Part of Z Word tools is the cztinterface program which is built from the
> CZT snapshot. I last built it from CZT SVN Version 8214****
>
>  ****
>
> Now I’ve downloaded and built the latest CZT version from Git and I can no
> longer build cztinterface. I get an error “No suitable constructor found
> for SectionManager()” at a line that says ****
>
> SectionManager manager = new SectionManager();****
>
>  ****
>
> I seem to remember that the SectionManager was changed some time ago. Is
> there an up to date javadocs site that I can look at to see the
> documentation of the classes in the current version?****
>
>  ****
>
> Thanks****
>
>  ****
>
> Anthony****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire
> the most talented Cisco Certified professionals. Visit the
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
> _______________________________________________
> CZT-Devel mailing list
> CZT...@li...
> https://lists.sourceforge.net/lists/listinfo/czt-devel
>
>

Re: [CZT-Devel] Building from CZT snapshot

[Anthony H. <an...@an...>]

Dear Andrius

 

I apologise. This was not a CZT problem at all. 

 

It was, as I should have guessed, the diabolical Maven. (I don’t….no, I’d better not express my opinion of Maven – it isn’t fit for a polite mailing list).

 

So, I have now rebuilt czt and this time it did not give the errors in the VCG I encountered before, and I could successfully build my cztinterface. (Though I did have to change one thing – I see that there is no longer a “typechecker”, but rather a “typechecker-z” – my pom had referred to “typechecker” and so failed the first time.)

 

However your question about which version I was using did prompt a couple of questions in return. The answer is that I was using the master cloned from the Git repository. I was slightly surprised that when I did a fetch after a couple of days there seemed to be no changes. When I looked at the log, it seems the last change to master was on Jan 10 at 17-10-07. Is that correct, or am I doing something wrong with git? What are the nightly builds made from? 

 

May I ask a related question, purely about git? When we were using subversion, I referred to the version of czt that I had used in building cztinterface by its svn revision number. What is the git equivalent that allows someone to go and get the exact revision? Is it the checksum, or timestamp, or what?

 

Thanks for all your help, and apologies for bothering you with the maven-induced nonsense

 

Anthony

 

 

 

From: Andrius Velykis [mailto:and...@ne...] 
Sent: 09 April 2013 09:27
To: Anthony Hall
Cc: CZT-Devel
Subject: Re: [CZT-Devel] Building from CZT snapshot

 

Dear Anthony,

 

Thanks for the info. Which CZT sources are you using? I am looking at the latest CZT source code and have problems matching your stack trace to my code.. The calls that are made in your stack trace are non-existent in my code :( Are you working on the `master` branch of the CZT Git repository? Or are you using the nighly build czt.jar?

 

Best regards,

Andrius

 

 

 

On Mon, Apr 8, 2013 at 5:31 PM, Anthony Hall <an...@an...> wrote:

Dear Andrius

 

Thank you again for a very swift response

 

The SectionManager did change - mostly internally (we added a support for "transactions" as a step towards better incremental-checking of Z sections - so that you could re-check only downstream dependencies without throwing away all upstream ones). Note, however, that this change enforces a bit stricter way of how it should be called - so let us assist if you encounter problems regarding to it.

 

The change in SectionManager interface you encountered is that it now explicitly requires to provide a dialect to use (see net.sourceforge.czt.session.Dialect enum for appropriate values). So in your case it would be `new SectionManager(Dialect.Z)` for Z checking.

Thank you. I did that and it all compiled OK. However, now I seem to be running foul of the new transaction features, because I’m getting a lot of test failures of the form “SectionInfoException: There is an ongoing transaction for the given key”

Of course I’m not doing anything manually with transactions so I’ve really not got much clue as to how to fix this.

 

The tests work be repeatedly calling the main procedure of my class, and that does a new SectionManager(Dialect.Z) each time. So I’m not sure what else I need to do. 

 

I attach the main class (CZTCheck, the class that runs the test (CZTTestUtils), a failing test set and the surefire reports. If you could point me at what I need to do I’d be most grateful!

 

You can generate the JavaDocs yourself by running `mvn javadoc:javadoc` for some module. They will be put into `target/site/apidocs` of the project (I think).

That seems to work, yes – though I got a lot of warnings like

[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available

[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0

but I don’t know whether that matters

 

And of course I have had a look at the SectionManager apidocs but it looks as if I shouldn’t have to do anything explicit unless I’m trying to do something clever with incremental compilation – or have I missed something there?

 

I know it is a bit annoying to manually have to generate all this. Since we now have nightly builds, I think I will just put a "nightly" version of the website as well - the current one has not been updated for 5 years! :(  Then all the changes that we add would be reflected immediately. This way all the up-to-date JavaDocs will also be online soon.

I think that would be really helpful – great!

 

Many thanks

 

Anthony

 

Let me know if there are any problems with the JavaDocs.

 

Best regards,

Andrius

 

On Mon, Apr 8, 2013 at 3:31 PM, Anthony Hall <an...@an...> wrote:

Part of Z Word tools is the cztinterface program which is built from the CZT snapshot. I last built it from CZT SVN Version 8214

 

Now I’ve downloaded and built the latest CZT version from Git and I can no longer build cztinterface. I get an error “No suitable constructor found for SectionManager()” at a line that says 

SectionManager manager = new SectionManager();

 

I seem to remember that the SectionManager was changed some time ago. Is there an up to date javadocs site that I can look at to see the documentation of the classes in the current version?

 

Thanks

 

Anthony

 


------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
CZT-Devel mailing list
CZT...@li...
https://lists.sourceforge.net/lists/listinfo/czt-devel

 

Re: [CZT-Devel] Building from CZT snapshot

[Andrius V. <and...@ne...>]

Dear Anthony,

Good to hear!

On Tue, Apr 9, 2013 at 12:02 PM, Anthony Hall <an...@an...>wrote:

>
> So, I have now rebuilt czt and this time it did not give the errors in the
> VCG I encountered before, and I could successfully build my cztinterface.
> (Though I did have to change one thing – I see that there is no longer a
> “typechecker”, but rather a “typechecker-z” – my pom had referred to
> “typechecker” and so failed the first time.)
>

We have normalised all project names to indicate the dialect. `typechecker`
is now a parent "umbrella" project for all typecheckers.


> ****
>
> However your question about which version I was using did prompt a couple
> of questions in return. The answer is that I was using the master cloned
> from the Git repository. I was slightly surprised that when I did a fetch
> after a couple of days there seemed to be no changes. When I looked at the
> log, it seems the last change to master was on Jan 10 at 17-10-07. Is that
> correct, or am I doing something wrong with git? What are the nightly
> builds made from?
>

Interesting issues - I am not really sure. Which address did you use to
clone the Git repository?

I have a hunch that our migration to the new SourceForge platform may have
influenced this.. if you see http://sourceforge.net/p/czt/code/ , the code
listing on their website has some "unknown" bits. After new commits, they
get refreshed to the correct version.. So I am a bit puzzled, but hope it
gets resolved over time by SourceForge.

Nightly builds are being made from the default read-only CZT git repository
at `git://git.code.sf.net/p/czt/code`.

So have you managed to pull the latest updates now or are you still on 2007
version? If there are problems, I can investigate.


> May I ask a related question, purely about git? When we were using
> subversion, I referred to the version of czt that I had used in building
> cztinterface by its svn revision number. What is the git equivalent that
> allows someone to go and get the exact revision? Is it the checksum, or
> timestamp, or what?
>
In Git, the commits are referenced by their hash, e.g.
967829cb33b9fba62c11bb577ca496fee0aa0525 is the current head of the
`master` branch (though we will push a lot of changes soon).
The hash and info of the last commit can be obtained by running `git log
-1`.

You can search for the commit info by this reference, e.g. use `git show
967829cb33b9fba62c11bb577ca496fee0aa0525`

Thanks for all your help, and apologies for bothering you with the
> maven-induced nonsense
>
No problem - builds are rarely trivial!

Best regards,
~Andrius

Re: [CZT-Devel] Building from CZT snapshot

[Andrius V. <and...@ne...>]

Dear Anthony,

I just realised that you may have used the old CZT repository path `git://
czt.git.sourceforge.net/gitroot/czt/czt` if you were following our setup
instructions... After the recent move to the new SourceForge platform, the
Git repository addresses changed. The read-only access is now `git://
git.code.sf.net/p/czt/code`. For write access, check your personal link at
http://sourceforge.net/p/czt/code/ when you are logged in to SourceForge.

Let me know if this gets the latest version for you. Here's some info on
changing the Git remote URL:
http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git

We will update the instructions accordingly.

Andrius


On Tue, Apr 9, 2013 at 12:20 PM, Andrius Velykis <
and...@ne...> wrote:

> Dear Anthony,
>
> Good to hear!
>
> On Tue, Apr 9, 2013 at 12:02 PM, Anthony Hall <an...@an...>wrote:
>
>>
>> So, I have now rebuilt czt and this time it did not give the errors in
>> the VCG I encountered before, and I could successfully build my
>> cztinterface. (Though I did have to change one thing – I see that there is
>> no longer a “typechecker”, but rather a “typechecker-z” – my pom had
>> referred to “typechecker” and so failed the first time.)
>>
>
> We have normalised all project names to indicate the dialect.
> `typechecker` is now a parent "umbrella" project for all typecheckers.
>
>
>> ****
>>
>> However your question about which version I was using did prompt a couple
>> of questions in return. The answer is that I was using the master cloned
>> from the Git repository. I was slightly surprised that when I did a fetch
>> after a couple of days there seemed to be no changes. When I looked at the
>> log, it seems the last change to master was on Jan 10 at 17-10-07. Is that
>> correct, or am I doing something wrong with git? What are the nightly
>> builds made from?
>>
>
> Interesting issues - I am not really sure. Which address did you use to
> clone the Git repository?
>
> I have a hunch that our migration to the new SourceForge platform may have
> influenced this.. if you see http://sourceforge.net/p/czt/code/ , the
> code listing on their website has some "unknown" bits. After new commits,
> they get refreshed to the correct version.. So I am a bit puzzled, but hope
> it gets resolved over time by SourceForge.
>
> Nightly builds are being made from the default read-only CZT git
> repository at `git://git.code.sf.net/p/czt/code`<http://git.code.sf.net/p/czt/code>
> .
>
> So have you managed to pull the latest updates now or are you still on
> 2007 version? If there are problems, I can investigate.
>
>
>> May I ask a related question, purely about git? When we were using
>> subversion, I referred to the version of czt that I had used in building
>> cztinterface by its svn revision number. What is the git equivalent that
>> allows someone to go and get the exact revision? Is it the checksum, or
>> timestamp, or what?
>>
> In Git, the commits are referenced by their hash, e.g.
> 967829cb33b9fba62c11bb577ca496fee0aa0525 is the current head of the
> `master` branch (though we will push a lot of changes soon).
> The hash and info of the last commit can be obtained by running `git log
> -1`.
>
> You can search for the commit info by this reference, e.g. use `git show
> 967829cb33b9fba62c11bb577ca496fee0aa0525`
>
> Thanks for all your help, and apologies for bothering you with the
>> maven-induced nonsense
>>
> No problem - builds are rarely trivial!
>
> Best regards,
> ~Andrius
>
>

Re: [CZT-Devel] Building from CZT snapshot

[Anthony H. <an...@an...>]

Dear Andrius

 

However your question about which version I was using did prompt a couple of questions in return. The answer is that I was using the master cloned from the Git repository. I was slightly surprised that when I did a fetch after a couple of days there seemed to be no changes. When I looked at the log, it seems the last change to master was on Jan 10 at 17-10-07. Is that correct, or am I doing something wrong with git? What are the nightly builds made from?

 

Interesting issues - I am not really sure. Which address did you use to clone the Git repository?

According to git config:

remote.origin.url=git://czt.git.sourceforge.net/gitroot/czt/czt

remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*

The url is what is given in setup.md 

 

I have a hunch that our migration to the new SourceForge platform may have influenced this.. if you see http://sourceforge.net/p/czt/code/ , the code listing on their website has some "unknown" bits. After new commits, they get refreshed to the correct version.. So I am a bit puzzled, but hope it gets resolved over time by SourceForge.

 

Nightly builds are being made from the default read-only CZT git repository at `git://git.code.sf.net/p/czt/code` <http://git.code.sf.net/p/czt/code%60> .

That doesn’t seem to be the same. Which should I be using?

 

So have you managed to pull the latest updates now or are you still on 2007 version? If there are problems, I can investigate.

As I say the version I have is Jan 30th (2013 that is)

 

May I ask a related question, purely about git? When we were using subversion, I referred to the version of czt that I had used in building cztinterface by its svn revision number. What is the git equivalent that allows someone to go and get the exact revision? Is it the checksum, or timestamp, or what?

In Git, the commits are referenced by their hash, e.g. 967829cb33b9fba62c11bb577ca496fee0aa0525 is the current head of the `master` branch (though we will push a lot of changes soon).

The hash and info of the last commit can be obtained by running `git log -1`.

 

You can search for the commit info by this reference, e.g. use `git show 967829cb33b9fba62c11bb577ca496fee0aa0525`

Thanks for that

 

All the best

 

Anthony

Re: [CZT-Devel] Building from CZT snapshot

[Andrius V. <and...@ne...>]

Dear Anthony,

On Tue, Apr 9, 2013 at 12:45 PM, Anthony Hall <an...@an...>wrote:

> According to git config:
>
> remote.origin.url=git://czt.git.sourceforge.net/gitroot/czt/czt****
>
> remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*****
>
> The url is what is given in setup.md ****
>
>
>
Yes, sorry, this is the old CZT Git repository path. After the recent move
to the new SourceForge platform, the Git repository addresses changed. The
read-only access is now `git://git.code.sf.net/p/czt/code`. For write
access, check your personal link at http://sourceforge.net/p/czt/code/ when
you are logged in to SourceForge.

Let me know if this gets the latest version for you. Here's some info on
changing the Git remote URL:
http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git

We will update the instructions accordingly. Sorry the about misleading
instructions in setup.md - I forgot to update the documentation after the
repository change.

Best regards,
Andrius

Re: [CZT-Devel] Building from CZT snapshot

[Anthony H. <an...@an...>]

Thanks Andrius

 

I’ve changed the url 

 

When I rebuilt I again got VCG test errors. This time, however, when I tried again the build was successful, although a lot of errors flashed past during the VCG testing they seemed to be handled in some way that didn’t prevent the build working.

 

I’ve just discovered something horrible that may possibly throw light on that. I’m getting a similar problem with my own cztinterface build – tests are failing apparently randomly. The root cause in my case appears to be a feature of JUnit: within a suite it runs tests in whatever order it feels like (and its mood seems to change from run to run). I had assumed and relied on the fact that it ran them in the order I wrote them. I’m surprised that this hasn’t hit me before. Anyway, I wonder if that might be happening in the VCG case as well?

 

All the best

 

Anthony

 

 

From: Andrius Velykis [mailto:and...@ne...] 
Sent: 09 April 2013 13:57
To: Anthony Hall
Cc: CZT-Devel
Subject: Re: [CZT-Devel] Building from CZT snapshot

 

Dear Anthony,

 

On Tue, Apr 9, 2013 at 12:45 PM, Anthony Hall <an...@an...> wrote:

According to git config:

remote.origin.url=git://czt.git.sourceforge.net/gitroot/czt/czt

remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*

The url is what is given in setup.md 

 

 

Yes, sorry, this is the old CZT Git repository path. After the recent move to the new SourceForge platform, the Git repository addresses changed. The read-only access is now `git://git.code.sf.net/p/czt/code` <http://git.code.sf.net/p/czt/code%60> . For write access, check your personal link at http://sourceforge.net/p/czt/code/ when you are logged in to SourceForge.

 

Let me know if this gets the latest version for you. Here's some info on changing the Git remote URL: http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git

 

We will update the instructions accordingly. Sorry the about misleading instructions in setup.md - I forgot to update the documentation after the repository change.

 

Best regards,

Andrius

 

Re: [CZT-Devel] Building from CZT snapshot

[Andrius V. <and...@ne...>]

Dear Anthony,

That is an interesting observation! I am reading myself online now that
JUnit does run tests in an arbitrary order.. I did have the same assumption
as you.

I am not sure if that is the case in VCG, but Leo's doing an overhaul of it
at the moment so hopefully all such issues will be identified and resolved
in the nearest future. Some of the flashing errors are corner cases for VCG
which require some tuning (if I understand correctly), so they are ignored
in the tests but are still producing verbose output at the moment. So that
output can be ignored as long as the build does not fail.

How is the SectionManager running with the latest CZT version? Are you
still getting transaction errors?

Best regards,
Andrius



On Tue, Apr 9, 2013 at 2:36 PM, Anthony Hall <an...@an...>wrote:

> Thanks Andrius****
>
> ** **
>
> I’ve changed the url ****
>
> ** **
>
> When I rebuilt I again got VCG test errors. This time, however, when I
> tried again the build was successful, although a lot of errors flashed past
> during the VCG testing they seemed to be handled in some way that didn’t
> prevent the build working.****
>
> ** **
>
> I’ve just discovered something horrible that may possibly throw light on
> that. I’m getting a similar problem with my own cztinterface build – tests
> are failing apparently randomly. The root cause in my case appears to be a
> feature of JUnit: within a suite it runs tests in whatever order it feels
> like (and its mood seems to change from run to run). I had assumed and
> relied on the fact that it ran them in the order I wrote them. I’m
> surprised that this hasn’t hit me before. Anyway, I wonder if that might be
> happening in the VCG case as well?****
>
> ** **
>
> All the best****
>
> ** **
>
> Anthony****
>
> ** **
>
> ** **
>
> *From:* Andrius Velykis [mailto:and...@ne...]
> *Sent:* 09 April 2013 13:57
>
> *To:* Anthony Hall
> *Cc:* CZT-Devel
> *Subject:* Re: [CZT-Devel] Building from CZT snapshot****
>
> ** **
>
> Dear Anthony,****
>
> ** **
>
> On Tue, Apr 9, 2013 at 12:45 PM, Anthony Hall <an...@an...>
> wrote:****
>
> According to git config:****
>
> remote.origin.url=git://czt.git.sourceforge.net/gitroot/czt/czt****
>
> remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*****
>
> The url is what is given in setup.md ****
>
> ** **
>
> ** **
>
> Yes, sorry, this is the old CZT Git repository path. After the recent move
> to the new SourceForge platform, the Git repository addresses changed. The
> read-only access is now `git://git.code.sf.net/p/czt/code`<http://git.code.sf.net/p/czt/code%60>.
> For write access, check your personal link at
> http://sourceforge.net/p/czt/code/ when you are logged in to SourceForge.*
> ***
>
> ** **
>
> Let me know if this gets the latest version for you. Here's some info on
> changing the Git remote URL:
> http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git
> ****
>
> ** **
>
> We will update the instructions accordingly. Sorry the about misleading
> instructions in setup.md - I forgot to update the documentation after the
> repository change.****
>
> ** **
>
> Best regards,****
>
> Andrius****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> CZT-Devel mailing list
> CZT...@li...
> https://lists.sourceforge.net/lists/listinfo/czt-devel
>
>

Re: [CZT-Devel] Building from CZT snapshot

[Leo F. <leo...@ne...>]

Hi Anthony,

Thanks for sticking with git and its teething problems… we are getting there and hopefully with the new site it will be easy to document for us/myself as well,
then these problems will be rooted out earlier…

--- SectMngmt.

In a nutshell, review the documentation within the top of SectionManager class and in the get / put methods to see how that affects transactions.
We tried to keep the API as seemingness as possible, yet if you use commands you might need to worry about transactions . Details on the features eamil.

The key motivation for transactions came through the handling of large specs (and those memory issues we discussed a while ago).
The point was how / what to reparse-typecheck or not on the transitive dependency chain such that minimal work was done and consistency
was guarantee.

We took a pretty conservative approach (i.e. if inference of consistency isn't possible, assume section is dirty and redo work), yet even that (together
with memory management improvements) improved performance by an order of magnitude (!!!).

The price for that the API got a bit more complicated for certain kinds of commands. In particular those commands where the "scope" of transaction
need to be widened. For instance, LaTeX parsing leads to a plethora of intermediate stages (i.e. latex markup, operator table, newline table, keyword table, etc),
but in particular low-level Unicode scanning, which leads to transactions overlap that would potentially create inconsistency when a section depend
on similar parents (e.g. quite common with those depending on standard_toolkit).

The widening of transaction scope (to ensure consistency)  and at the same time guarantee a minimum amount of re-work possible (i.e. tokenising
and I/O during parsing is the lion's share of the time for type checking), at the price of some adjustment to section management code.

There are various examples throughout CZT on the use of transactions for the section manager you could draw inspiration from, but we ought / will
add this as a key part of its documentation.

--- VCGing

Some tests on VCG do fail and I know about the issue. They come mostly from weird / unusual schema calculus features for tests that there is
no actual implementation for them yet. I then explicitly say "EXCEPTION HANDLED DURING TESTING" so that I don't loose the test case by removing it.
Given they are from weird uses of Z rather than actual ones, I will only implement later on.

--- jUnit

jUnit is indeed unsorted so one cannot rely on declared order. Instead you could use the setup() and tearDown() methods for setting up things like
the section manager.

Best,
Leo


On 9 Apr 2013, at 14:36, Anthony Hall <an...@an...<mailto:an...@an...>>
 wrote:

Thanks Andrius

I’ve changed the url

When I rebuilt I again got VCG test errors. This time, however, when I tried again the build was successful, although a lot of errors flashed past during the VCG testing they seemed to be handled in some way that didn’t prevent the build working.

I’ve just discovered something horrible that may possibly throw light on that. I’m getting a similar problem with my own cztinterface build – tests are failing apparently randomly. The root cause in my case appears to be a feature of JUnit: within a suite it runs tests in whatever order it feels like (and its mood seems to change from run to run). I had assumed and relied on the fact that it ran them in the order I wrote them. I’m surprised that this hasn’t hit me before. Anyway, I wonder if that might be happening in the VCG case as well?

All the best

Anthony


From: Andrius Velykis [mailto:and...@ne...<http://newcastle.ac.uk>]
Sent: 09 April 2013 13:57
To: Anthony Hall
Cc: CZT-Devel
Subject: Re: [CZT-Devel] Building from CZT snapshot

Dear Anthony,

On Tue, Apr 9, 2013 at 12:45 PM, Anthony Hall <an...@an...<mailto:an...@an...>> wrote:
According to git config:
remote.origin.url=git://czt.git.sourceforge.net/gitroot/czt/czt<http://czt.git.sourceforge.net/gitroot/czt/czt>
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
The url is what is given in setup.md<http://setup.md>


Yes, sorry, this is the old CZT Git repository path. After the recent move to the new SourceForge platform, the Git repository addresses changed. The read-only access is now `git://git.code.sf.net/p/czt/code`<http://git.code.sf.net/p/czt/code%60>. For write access, check your personal link at http://sourceforge.net/p/czt/code/ when you are logged in to SourceForge.

Let me know if this gets the latest version for you. Here's some info on changing the Git remote URL: http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git

We will update the instructions accordingly. Sorry the about misleading instructions in setup.md<http://setup.md> - I forgot to update the documentation after the repository change.

Best regards,
Andrius

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter_______________________________________________
CZT-Devel mailing list
CZT...@li...<mailto:CZT...@li...>
https://lists.sourceforge.net/lists/listinfo/czt-devel