build.log
[MDEV-20579] Mass Testsuite Failures on armv7hl Created: 2019-09-13 Updated: 2019-10-14 Resolved: 2019-10-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server, Tests |
| Affects Version/s: | 10.3.18 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Michal Schorm | Assignee: | Sergei Golubchik |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
Fedora |
||
| Attachments: |
build.log
|
| Description |
|
The testsuite of the freshly released version 10.3.18 fails heavily exclusively on the armv7hl architecture. The failing testsuites are Spider and Versioning. An interesting simmilarity is nearly 1000 occurences of:
For example:
You can you the attached build log, or this link to that log. (they are the same) I haven't made much of a research yet. I just found out and tried to inform you ASAP. |
| Comments |
| Comment by Sergei Golubchik [ 2019-09-14 ] |
|
These warnings should be expected. In tests mysqld is started with one big config file that has a bunch of plugin options (like this loose-feedback-debug-startup-interval=20 and many loose-innodb- optons. If a feedback plugin or innodb aren't enabled for any particular tests, all these options will be unknown to mysqld, but loose- prefix makes them warnings, not hard errors. So, warnings about unknown loose- options are normal. In fact, you can ignore all warnings in the log files, unless mysql-test-run tells you not to. mtr has a built-in list of "expected" warnings, it will complain when it'll see a warning not in the list. As long as mtr does not complain, warnings are fine. |
| Comment by Sergei Golubchik [ 2019-10-14 ] |
|
mschorm, I'm closing this one as we typically do with any MDEV that had "need_feedback" label and no activity for a month. If you'd like to keep it open, just say so in a comment and I'll reopen it. |