Hide Forgot
Description of problem: Case: /live-g-file/test_copy_move Random Seed: R02S1191492334812ef385a5af89a59f29c9 Output: ERROR:live-g-file.c:708:do_copy_move: assertion failed (error == (g-io-error-quark, 25)): Target file exists (g-io-error-quark, 2) Version-Release number of selected component (if applicable): glib2-2.22.5-5.el6 How reproducible: 100% Steps to Reproduce: 1. rpmbuild -bc ~/rpmbuild/SPECS/glib2.spec 2. cd ~/rpmbuil/BUILD/glib* 3. make full-report Actual results: one failure Expected results: no failures Additional info:
Found another one: TEST: desktop-app-info... (pid=27576) /desktop-app-info/delete: ** ERROR:desktop-app-info.c:92:test_delete: assertion failed: (!res) FAIL GTester: last random seed: R02S8d61ed03004d0a05490f0e3dedda9c50 Really don't know if it is false alarm (wrong test) or real bug.
What user are these tests running under? I wrote the first one, wonder why it fails.
Hm can't reproduce the first one anymore. Second failure still in, but it seems that only when running as root.
Can see again the firs error (running as non-root user). ERROR:live-g-file.c:708:do_copy_move: assertion failed (error == (g-io-error-quark, 25)): Target file exists (g-io-error-quark, 2) On fresh installed RHEL6.1 (RHEL6.1-20110301.n.1). Can anybody also reproduce it? Also spotted that only on i686 machines /g-icon/serialize will always stuck, will not cause any crash but take so long that beaker watchdog always kill it. Should this operation/test really take so long? glib2-2.22.5-6.el6
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Can still reproduce on glib2-2.22.5-7.el6. x86_64: ======- #F# /live-g-file/test_copy_move .... [failed] ERROR:live-g-file.c:708:do_copy_move: assertion failed (error == (g-io-error-quark, 25)): Target file exists (g-io-error-quark, 2) (ret. code: -256 ) Plus a new one: #F# /array/large-size .... [failed] ERROR:array-test.c:121:array_large_size: stderr of child process (28202) failed to match: *failed to allocate 2147483648 bytes* (ret. code: -256 ) Full log on x86_64 at http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/02/1979/197918/419745/4691922/TESTOUT.log i686: ===== ####### Overall results -- 2 FAILED, 230 PASSED ####### #F# /misc/timer .... [failed] ERROR:testing.c:60:test_timer: assertion failed (g_test_timer_last() == ttime): (0.025065 == 0.025065) (ret. code: -256 ) #F# /live-g-file/test_copy_move .... [failed] ERROR:live-g-file.c:708:do_copy_move: assertion failed (error == (g-io-error-quark, 25)): Target file exists (g-io-error-quark, 2) (ret. code: -256 ) Log at http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/02/1979/197918/419746/4691927/TESTOUT.log
s390x: ====== ####### Overall results -- 1 FAILED, 231 PASSED ####### #F# /live-g-file/test_copy_move .... [failed] ERROR:live-g-file.c:708:do_copy_move: assertion failed (error == (g-io-error-quark, 25)): Target file exists (g-io-error-quark, 2) (ret. code: -256 ) Full log at http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/03/1992/199242/422657/4728327/TESTOUT.log
(In reply to comment #7) > s390x: > ====== > > ####### Overall results -- 1 FAILED, 231 PASSED ####### > #F# /live-g-file/test_copy_move .... [failed] > > ERROR:live-g-file.c:708:do_copy_move: assertion failed (error == > (g-io-error-quark, 25)): Target file exists (g-io-error-quark, 2) (ret. code: > -256 ) > > Full log at > http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/03/1992/199242/422657/4728327/TESTOUT.log Same for ppc64, log at http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/03/1992/199242/422656/4728322/TESTOUT.log
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Another test failed for me: ERROR:buffered-input-stream.c:109:test_set_buffer_size: assertion failed (size == bufsize): (47244640267 == 11) (ret. code: -256 ) this fail is visible only on ppc64 and s390x, on i386 and x86_64 this test passed.
I'm able to reproduce the failure from comment 14 on ppc64 and s390x only with version glib2-2.28.8-4.el6. A new fail appear on i386 only: ERROR:testing.c:74:test_timer: assertion failed (g_test_timer_last() == ttime): (0.025023 == 0.025023) (ret. code: -256 ) but according the values I expect that this is some rounding error, so not critical.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/