[Bug 1136788] New: Sqlite oserror test fails on ppc64le
http://bugzilla.suse.com/show_bug.cgi?id=1136788 Bug ID: 1136788 Summary: Sqlite oserror test fails on ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: max@suse.com Reporter: jbrielmaier@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The oserror.test (https://repo.or.cz/sqlite.git/blob_plain/HEAD:/test/oserror.test) fails sometimes on ppc64le with the following error log: ! oserror-2.1.1 expected: [1 {disk I/O error}] ! oserror-2.1.1 got: [0 {}] ! oserror-2.1.2 expected: [^os_unix.c:\d+: \(\d+\) unlink\(.*test.db-wal\) - ] ! oserror-2.1.2 got: [] Time: oserror.test 194 ms The strange point here is, that it doesn't seem to fail always. So the build in server:database for openSUSE_Factory_PowerPC succeeds without this error. But when I built sqlite from server:database on a local ppc64le machine, it fails with exactly this test. I checked it on another Power machine and there the test also fails (one is POWER8, the other POWER9). In openSUSE:Factory:PowerPC/sqlite3 it fails in a different test (swarmvtab2.test). So I assume these failures are not connected. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1136788 http://bugzilla.suse.com/show_bug.cgi?id=1136788#c1 Reinhard Max <max@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbrielmaier@suse.com Flags| |needinfo?(jbrielmaier@suse. | |com) --- Comment #1 from Reinhard Max <max@suse.com> --- Does this still happen with recent SQLite versions? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1136788 http://bugzilla.suse.com/show_bug.cgi?id=1136788#c2 Reinhard Max <max@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #2 from Reinhard Max <max@suse.com> --- I assume this is not an issue anymore. If it still happens, feel free to reopen. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com