[Bug 1204629] New: [Build 20221023] transactional-update: munmap_chunk(): invalid pointer
http://bugzilla.opensuse.org/show_bug.cgi?id=1204629 Bug ID: 1204629 Summary: [Build 20221023] transactional-update: munmap_chunk(): invalid pointer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2831134/modules/tdup /steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: openQA Blocker: Yes ## Observation While testing an upgrade from the previous snapshot to 1023 (which does not have a lot of changes, so possibly this issue is not even related to the snapshot), tdup fails with: munmap_chunk(): invalid pointer Use '--interactive' for manual problem resolution. openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos-old2microosnext@64bit fails in [tdup](https://openqa.opensuse.org/tests/2831134/modules/tdup/steps/11) ## Test suite description Boot from existing, static MicroOS image and transactional-update dup to snapshot under test ## Reproducible Fails since (at least) Build [20221023](https://openqa.opensuse.org/tests/2829980) ## Expected result Last good: [20221022](https://openqa.opensuse.org/tests/2828758) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos&flavor=MicroOS-Image&machine=64bit&test=microos-old2microosnext&version=Tumbleweed) -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204629 http://bugzilla.opensuse.org/show_bug.cgi?id=1204629#c1 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iforster@suse.com --- Comment #1 from Ignaz Forster <iforster@suse.com> --- https://openqa.opensuse.org/tests/2831134#step/tdup/14 indicates that zypper was terminated by a SIGABRT (return code 134). It seems however that current tests are working fine again? -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com