Bug 1149647 - new tests failing
Summary: new tests failing
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mariadb
Version: 21
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Dorňák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2014-10-06 10:45 UTC by Dan Horák
Modified: 2015-12-02 16:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 04:08:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dan Horák 2014-10-06 10:45:49 UTC
seems 3 tests started to fail on s390x with mariadb-10.0.14-4.fc21
connect.part_file connect.part_table connect.updelx

http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1578654
http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1578464
http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1578245
3 build attempts in different times, seems deterministic

other secondary arches (s390, ppc64, ppc64le) were not yet investigated


Version-Release number of selected component (if applicable):
mariadb-10.0.14-4.fc21

Comment 1 Dan Horák 2014-10-06 12:17:28 UTC
for the record the ppc* builds are http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2137855 (not finished yet)

Comment 2 Michal Toman 2014-10-06 20:07:52 UTC
As I expected the tests are only failing on big endian (ppc64le works). Several other connect.* tests are disabled on BE archs so I guess these should just be added to the list.

Comment 3 Dan Horák 2014-10-11 14:19:12 UTC
one more test failing on s390 (32-bit) = http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1582084

--------------------------------------------------------------------------
The servers were restarted 3183 times
Spent 2614.515 of 6730 seconds executing testcases
Completed: Failed 1/2896 tests, 99.97% were successful.
Failing test(s): main.key_cache
The log files in var/log may give you some hint of what went wrong.
If you want to report this error, please read first the documentation
at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html
631 tests were skipped, 341 by the test itself.
mysql-test-run: *** ERROR: there were failing test cases

Comment 4 Dan Horák 2014-10-12 15:49:42 UTC
- all ppc builds (ppc64, ppc64p7, ppc64le) went fine - http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2143656
- s390x build was also fine
=> only s390 remains with one test failing

Comment 5 Honza Horak 2014-10-13 10:53:17 UTC
(In reply to Dan Horák from comment #4)
> => only s390 remains with one test failing

OK will fix hopefully today and will submit updates right after it, since the previous are already stable.

Comment 6 Dan Horák 2015-01-06 12:00:05 UTC
with mariadb-10.0.15-3.fc21 we see

...
The servers were restarted 3201 times
Spent 2564.480 of 6897 seconds executing testcases
Completed: Failed 2/2911 tests, 99.93% were successful.
Failing test(s): connect.mrr connect.updelx2
The log files in var/log may give you some hint of what went wrong.
If you want to report this error, please read first the documentation
at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html
630 tests were skipped, 344 by the test itself.
...

in http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1681591 (s390, s390x)
or
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2271491 (ppc64/ppc64p7)

Comment 7 Honza Horak 2015-01-06 13:27:01 UTC
(In reply to Dan Horák from comment #6)
> Completed: Failed 2/2911 tests, 99.93% were successful.
> Failing test(s): connect.mrr connect.updelx2

Also disabled for now:
http://pkgs.fedoraproject.org/cgit/mariadb.git/commit/?id=07c8c5049274d04db51d52877681cf73d26e5492

Comment 8 Jakub Dorňák 2015-06-02 17:16:00 UTC
another one on ppc64p7: connect.json_udf
(disabled for now)

Comment 9 Fedora Admin XMLRPC Client 2015-08-11 10:03:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 10 Fedora End Of Life 2015-11-04 10:53:59 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2015-12-02 04:08:59 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.