I'll try to track it down.
On 2018-06-06 09:13 PM, bill lam wrote:
Did it run om last time? Do you know how to bisect and locate the commit
that caused the problem? always remember to update and sync test suite
after each git reset.
On Thu, Jun 7, 2018, 8:45 AM Bill Heagy <[email protected]> wrote:
For a few days now, running the test routines has produced a long list
of errors. That's with the latest source from git. I'm sorry, I didn't
notice which update started the problem. This is on Linux testing or
stable 32bit and testing 64bit.
load 'test/tsu.ijs'
RUN ddall
g000s
g010s
g011s
g012s
g020s
g021s
g022s
g100s
g101s
g102s
g110s
g111s
g112s
g120s
g222s
g230s
g402
g410
g410s
g431
g510
gb
gintovfl
gos
gparse
gsp431
RUN1'g000s'
1:@:(9!:19)2^_44[(echo^:ECHOFILENAME) './g000s.ijs'
1
NB. =/\. B
-------------------------------------------------------------
(1 0 0 1,:0 1 0 1) -: =/\. 0 0 1 1 ,: 0 1 0 1
1
eq=: 4 : 'x=y'
f=: 3 : '(=/\. -: eq/\.) ?y$2'
,f"1 x=:7 8 9,."0 1 [ _1 0 1+ 255
0 0 0 0 0 0 0 0 0
|assertion failure: RUN1
|[-8] /home/wheagy/tmp/jsource.git/trunk/test/g000s.ijs
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
Bill Heagy
615 Country Club Drive mailto:[email protected]
London, Ontario N6C 5P8 Canada telephone: 519-680-0311
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
