OK, thanks.
My impression of Git master is that there is often work-in-progress that should not be expected to work. Is it useful to report bugs while development is still in progress? For example, trying it now I saw this: Fail "Exception- InternalError: codeToPRegRev raised while compiling"
On 11 November 2017 at 19:37, David Matthews <David.Matthews at prolingua.co.uk
wrote:
Hi Ramana, The fixes branches are useful in the early phase of the development cycle if bugs are found soon after a release. At some point it is no longer viable to keep back-porting especially if there is a risk that the fix itself may introduce bugs. This particular change was one of a number to make the thread system more resilient. At this point I'd suggest switching to Git master.
Regards, David
On 11/11/2017 07:15, Ramana Kumar wrote:
Hi David,
Are you still updating the fixes-5.7 branch? It seems to me that this commit might be a bug fix worth including, though I'm not sure if it depends on new developments. https://github.com/polyml/polyml/commit/5ba42e588373bd3cd63b 8cadb8c4cb8a349c7fff#diff-27af5828c397c28b2fdeacab709ccf57
Cheers, Ramana
On 17 May 2017 at 00:49, David Matthews <David.Matthews at prolingua.co.uk> wrote:
On 16/05/2017 04:47, Jerry James wrote:
I attempted to build this version for Fedora. It succeeded on all
architectures except aarch64:
https://koji.fedoraproject.org/koji/taskinfo?taskID=19526061
I don't understand the failure, though. We run "make check" after the build to gain some confidence that the build is good. Here is an extract from the build log (https://kojipkgs.fedoraproject.org//work/tasks/6133/19526133/build.log ): Test044.ML => Passed make[2]: Leaving directory '/builddir/build/BUILD/polyml-5.7' make[2]: *** [Makefile:1175: check-local] Error 1 make[1]: Leaving directory '/builddir/build/BUILD/polyml-5.7' make[1]: *** [Makefile:997: check-am] Error 2 make: *** [Makefile:706: check-recursive] Error 1
It looks like every individual test passed, but the test suite as a whole failed. Do you have any idea what might cause this? Thank you,
The only thing that occurs to me is that one or other of the tests messed up the internal state so that when the poly process came to exit it crashed. I don't have access to any machine running aarch64 (that's 64-bit ARM isn't it?) so there's no way I can test any of this.
Regards, David
polyml mailing list polyml at inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml