> Can you share the result?
> > So many failures usually indicate something stupid that can be easily fixed. Sorry for the late reply. Here it goes: ## ----------------------------- ## ## GNU Smalltalk 3.2 test suite. ## ## ----------------------------- ## Regression tests. 1: arrays.st FAILED (testsuite.at:27) 2: classes.st FAILED (testsuite.at:28) 3: blocks.st FAILED (testsuite.at:29) 4: sets.st FAILED (testsuite.at:30) 5: processes.st FAILED (testsuite.at:31) 6: exceptions.st FAILED (testsuite.at:32) 7: intmath.st FAILED (testsuite.at:33) 8: floatmath.st FAILED (testsuite.at:34) 9: dates.st FAILED (testsuite.at:39) 10: objects.st FAILED (testsuite.at:40) 11: strings.st FAILED (testsuite.at:41) 12: chars.st FAILED (testsuite.at:42) 13: objdump.st FAILED (testsuite.at:43) 14: delays.st FAILED (testsuite.at:44) 15: geometry.st FAILED (testsuite.at:45) 16: cobjects.st FAILED (testsuite.at:46) 17: compiler.st FAILED (testsuite.at:47) 18: fileext.st FAILED (testsuite.at:48) 19: mutate.st FAILED (testsuite.at:49) 20: untrusted.st ok 21: getopt.st FAILED (testsuite.at:51) 22: quit.st ok 23: pools.st ok Other simple tests. 24: ackermann.st FAILED (testsuite.at:56) 25: ary3.st FAILED (testsuite.at:57) 26: except.st FAILED (testsuite.at:58) 27: fibo.st FAILED (testsuite.at:59) 28: hash.st FAILED (testsuite.at:60) 29: hash2.st FAILED (testsuite.at:61) 30: heapsort.st FAILED (testsuite.at:62) 31: lists.st FAILED (testsuite.at:63) 32: lists1.st FAILED (testsuite.at:64) 33: lists2.st FAILED (testsuite.at:65) 34: matrix.st FAILED (testsuite.at:66) 35: methcall.st FAILED (testsuite.at:67) 36: nestedloop.st FAILED (testsuite.at:68) 37: objinst.st FAILED (testsuite.at:69) 38: prodcons.st FAILED (testsuite.at:70) 39: random-bench.st FAILED (testsuite.at:71) 40: sieve.st FAILED (testsuite.at:72) 41: strcat.st FAILED (testsuite.at:73) Basic packages. 42: SUnit ok 43: Parser ok ANSI compliancy tests. 44: ArrayANSITest ok 45: ArrayFactoryANSITest ok 46: BagANSITest ok 47: BagFactoryANSITest ok 48: BooleanANSITest ok 49: ByteArrayANSITest ok 50: ByteArrayFactoryANSITest ok 51: CharacterANSITest ok 52: CharacterFactoryANSITest ok 53: DateAndTimeANSITest ok 54: DateAndTimeFactoryANSITest ok 55: DictionaryANSITest ok 56: DictionaryFactoryANSITest ok 57: DurationANSITest ok 58: DurationFactoryANSITest ok 59: DyadicValuableANSITest ok 60: ErrorANSITest ok 61: ErrorClassANSITest ok 62: ExceptionANSITest ok 63: ExceptionClassANSITest ok 64: ExceptionSetANSITest ok 65: FailedMessageANSITest ok 66: FileStreamFactoryANSITest ok 67: FloatANSITest ok 68: FloatCharacterizationANSITest ok 69: FractionANSITest ok 70: FractionFactoryANSITest ok 71: IdentityDictionaryANSITest ok 72: IdentityDictionaryFactoryANSITest ok 73: IntegerANSITest ok 74: IntervalANSITest ok 75: IntervalFactoryANSITest ok 76: MessageNotUnderstoodANSITest ok 77: MessageNotUnderstoodSelectorANSITest ok 78: MonadicBlockANSITest ok 79: NilANSITest ok 80: NiladicBlockANSITest ok 81: NotificationANSITest ok 82: NotificationClassANSITest ok 83: ObjectANSITest ok 84: ObjectClassANSITest ok 85: OrderedCollectionANSITest ok 86: OrderedCollectionFactoryANSITest ok 87: ReadFileStreamANSITest ok 88: ReadStreamANSITest ok 89: ReadStreamFactoryANSITest ok 90: ReadWriteStreamANSITest ok 91: ReadWriteStreamFactoryANSITest ok 92: ScaledDecimalANSITest ok 93: SelectorANSITest ok 94: SetANSITest ok 95: SetFactoryANSITest ok 96: SortedCollectionANSITest ok 97: SortedCollectionFactoryANSITest ok 98: StringANSITest ok 99: StringFactoryANSITest ok 100: SymbolANSITest ok 101: TranscriptANSITest ok 102: WarningANSITest ok 103: WarningClassANSITest ok 104: WriteFileStreamANSITest ok 105: WriteStreamANSITest ok 106: WriteStreamFactoryANSITest ok 107: ZeroDivideANSITest ok 108: ZeroDivideFactoryANSITest ok Other packages. 109: Complex ok 110: Continuations ok 111: DBD-MySQL skipped (testsuite.at:149) 112: DBD-SQLite skipped (testsuite.at:150) 113: DebugTools ok 114: DhbNumericalMethods ok 115: Digest FAILED (testsuite.at:153) 116: GDBM skipped (testsuite.at:154) 117: Iconv skipped (testsuite.at:155) 118: Magritte ok 119: ROE skipped (testsuite.at:157) 120: SandstoneDb ok 121: Seaside-Core FAILED (testsuite.at:159) 122: Sport ok 123: Swazoo ... |
On Tue, May 11, 2010 at 08:12, leledumbo <[hidden email]> wrote:
> >> Can you share the result? >> >> So many failures usually indicate something stupid that can be easily >> fixed. > > Sorry for the late reply. Here it goes: Please share the testsuite.log and testsuite.dir files, tar/gzipped. Most could be a CR/LF problem. I wonder why 20/22/23 pass... > 115: Digest FAILED > (testsuite.at:153) This is unexpected. > 121: Seaside-Core FAILED > (testsuite.at:159) This is kind-of-unexpected. > 122: Sport ok This is good news for sockets support. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Enjoy it: testsuite.zip
Note: I don't know why re-"make check" stops (or maybe I didn't wait too long) at Swazoo test, so I Ctrl+C it. I'll retry with a fresh build. |
> Enjoy it: http://n4.nabble.com/file/n2195777/testsuite.zip testsuite.zip
Indeed, something is wrong with the way transcript and stdout/stderr output is mixed. I'll look at it later. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
In reply to this post by leledumbo
On 05/12/2010 11:03 AM, leledumbo wrote:
> Enjoy it: http://n4.nabble.com/file/n2195777/testsuite.zip testsuite.zip Please try the attached patch. > Note: I don't know why re-"make check" stops (or maybe I didn't wait too > long) at Swazoo test, so I Ctrl+C it. I'll retry with a fresh build. This may be a race condition/heisenbug. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk win32-try.patch (1K) Download Attachment |
Before I did something wrong, what patch command should I invoke? i.e.: patch -p0 bla bla bla < thispatch.patch
|
On Mon, May 17, 2010 at 08:25, leledumbo <[hidden email]> wrote:
> > Before I did something wrong, what patch command should I invoke? i.e.: patch > -p0 bla bla bla < thispatch.patch patch -p1 I think. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Free forum by Nabble | Edit this page |