User tests: Successful: Unsuccessful:
If you export a live site's database and compare it to the core joomla.sql you'll see lots of minor differences. This hardens the database examination and shows that joomla.sql contains many code style mistakes.
Labels |
Added:
?
|
Category | ⇒ | Code style |
@nicksavov Those failures are pre-existing and have been for several weeks now.
Ah, OK, cool. Thanks!
Status | Pending | ⇒ | Ready to Commit |
Easy | No | ⇒ | Yes |
RTC
This comment was created with the J!Tracker Application at http://issues.joomla.org/.
I don't know why my PR causes the Travis CI build mistake.
Is there any actions from my side expected to have this PR accepted?
There are some codestyle issues. You can see them at the bottom of https://travis-ci.org/joomla/joomla-cms/jobs/34492664. It would be great if you can fix those.
The failed unit tests itself are because we use a deprecated method in the tests. It hasn't anything to do with your PR. To fix that, you could rebase your PR with staging, if you know how to do that. Otherwise don't bother.
True, interesting :)
Labels |
Added:
?
|
Labels |
Removed:
?
|
Labels |
Added:
?
|
Status | Ready to Commit | ⇒ | Needs Review |
@phproberto
Frankly speaking I'm not sure how to rebase correctly.
But I made another PR #4311 that has all the changes from the current PR and much more changes. And that PR is associated to staging.
Probably the current PR can be closed, if PR #4311 is accepted.
Status | Needs Review | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-10-08 10:18:23 |
Thanks for submitting this, Shur! :)
The code looks good.
It's all code styling improvements, with the additions of the following two options for the postinstall_messages table:
IF NOT EXISTS
ENGINE=InnoDB
Looks like Travis is failing on the above two changes, so the unit tests would have to be updated appropriately.