I was in the process of building some packages, and thought I'd run the testsuite. One test did fail, and I figured I'd send it on for completeness:
/Users/hww3/Pike-v7.6.86/src/testsuite.in:10260: Test 10425 (shift 2) failed to return proper results. 1: 2: array a() 3: { 4: Stdio.File p = Stdio.File(); 5: object pid = Process.create_process(RUNPIKE_ARRAY + 6: ({ "/Users/hww3/Pike-v7.6.86/ src/test_resolve.pike" }), 7: ([ "stdout":p->pipe (Stdio.PROP_IPC) ])); 8: __signal_watchdog(); 9: string results = lower_case(p->read()); 10: __signal_watchdog(); 11: int err = pid->wait(); 12: int ok; 13: int failed; 14: if (((sscanf(results, "%*sok:%d", ok) != 2) + 15: (sscanf(results, "%*sfailed:%d", failed) != 2)) == 2) { 16: // No "ok", and no "failed". 17: return ({ err, results }); 18: } 19: return ({ ok, failed }); 20: } 21:
o->a(): ({ /* 2 elements */ -1, "invalid memory access of location 00000ab0 eip=92c39c8d\n" })
Could that be when it's trying to resolve or initialize the GL module? Should be possible to pin down by inserting a couple of debug messages in test_resolve.pike and then run it manually.
Could that be when it's trying to resolve or initialize the GL module? Should be possible to pin down by inserting a couple of debug messages in test_resolve.pike and then run it manually.
Could that be when it's trying to resolve or initialize the GL module? Should be possible to pin down by inserting a couple of debug messages in test_resolve.pike and then run it manually.
Could that be when it's trying to resolve or initialize the GL module? Should be possible to pin down by inserting a couple of debug messages in test_resolve.pike and then run it manually.
Could that be when it's trying to resolve or initialize the GL module? Should be possible to pin down by inserting a couple of debug messages in test_resolve.pike and then run it manually.
Could that be when it's trying to resolve or initialize the GL module? Should be possible to pin down by inserting a couple of debug messages in test_resolve.pike and then run it manually.
pike-devel@lists.lysator.liu.se