[Bug 1021654] New: Sometimes clisp build fails on i586/x86_64 on testing sockets
http://bugzilla.suse.com/show_bug.cgi?id=1021654 Bug ID: 1021654 Summary: Sometimes clisp build fails on i586/x86_64 on testing sockets Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening@forge.provo.novell.com Reporter: werner@suse.com QA Contact: adrian@suse.com Found By: --- Blocker: --- This is how it should look like and how it does look most times: [ 594s] 33 path: 0 errors out of 176 tests [ 594s] 34 setf: 0 errors out of 197 tests [ 594s] 35 socket: 0 errors out of 92 tests [ 594s] 36 steele7: 0 errors out of 86 tests [ 594s] 37 streams: 0 errors out of 374 tests [ 594s] 38 streamslong: 0 errors out of 25 tests [ 594s] 39 strings: 0 errors out of 409 tests but sometimes the KVM build fails with [ 669s] 33 path: 0 errors out of 176 tests [ 669s] 34 setf: 0 errors out of 197 tests [ 669s] 35 socket: 1 error out of 92 tests [ 669s] 36 steele7: 0 errors out of 86 tests [ 669s] 37 streams: 0 errors out of 374 tests [ 669s] 38 streamslong: 0 errors out of 25 tests [ 669s] 39 strings: 0 errors out of 409 tests and this on both i586 and x86_64 ... compare with devel:languages:misc/clisp -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1021654 http://bugzilla.suse.com/show_bug.cgi?id=1021654#c2 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tchvatal@suse.com Resolution|--- |UPSTREAM --- Comment #2 from Dr. Werner Fink <werner@suse.com> --- Currently I do not see this behaviour [ 504s] 37 socket: 0 errors out of 92 tests seems to be that the KVM had been fixed at this point. Beside this: why have a package maintainer fix a bug in the KVM engine if a standard test does fail within a KVM? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com