See <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/2535/changes>
Changes:
[weblate] Translated using Weblate (Chinese (Taiwan))
[weblate] Translated using Weblate (Turkish)
------------------------------------------
Started by GitHub push by
Building in workspace <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/>
Checkout:workspace / <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/> - hudson.remoting.LocalChannel@3ff9f663
Using strategy: Default
Last Built Revision: Revision 935376cd496ed3fd692691cf52946c3dbfe9c9b3 (origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from git://github.com/phpmyadmin/phpmyadmin.git
Commencing build of Revision 8bbacc735ec8cd76a78cfb5e5f03471f1d56ae40 (origin/master)
Checking out Revision 8bbacc735ec8cd76a78cfb5e5f03471f1d56ae40 (origin/master)
[workspace] $ /bin/sh -xe /tmp/hudson1015853050382603793.sh
+ ./scripts/generate-mo --quiet
po/zh_TW.po:1191: format specifications in 'msgid' and 'msgstr' for argument 1 are not the same
msgfmt: found 1 fatal error
Build step 'Execute shell' marked build as failure
[CHECKSTYLE] Skipping publisher since build result is FAILURE
[DRY] Collecting duplicate code analysis files...
[DRY] Finding all files that match the pattern build/logs/pmd-cpd.xml
[DRY] Parsing 1 files in <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/>
[DRY] Successfully parsed file <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/build/logs/pmd-cpd.xml> of module with 20 warnings.
[DRY] Computing warning deltas based on reference build #2534
[TASKS] Skipping publisher since build result is FAILURE
[ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #2534
Recording plot data
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.4 (default)
[xUnit] [INFO] - [PHPUnit-3.4 (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '<http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/'> for the testing framework 'PHPUnit-3.4 (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
* <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/build/logs/junit.xml> is 1 min 59 sec old
[xUnit] [INFO] - Setting the build status to FAILURE
[xUnit] [INFO] - Stopping recording.
Hi,
to answer Rouslan's question, the last time I heard from Thijs, he wrote
that Debian was in freeze for its next release, so they could not put
phpMyAdmin 3.5 in it.
--
Marc Delisle
http://infomarc.info
Hi All,
I'm a computer engineering student at university of Peradeniya, Sri Lanka.
I would like to contribute to
phpmyadmin in the next summer.
So I went through the idea list of this summer
https://wiki.phpmyadmin.net/pma/GSoC_2013_Ideas_List
I'm interesting about automated testing Idea since I have experienced in
php and mysql.
Can someone explain me more about this idea ?
--
Thank You and Best Regards,
Senura Yasaswin
University of Peradeniya
Hello Team,
I have create store procedure in this ( "http://aekoncabs.com/") domain.
it was created successfully but when i trying to call that procedure in
phpmyadmin it giving following error.
procedure can't return a resultset in the given context
And i do same process in my localhost in same version of mysql its working
fine there.
Please help me. Its urgent.
Regards
Niraj Singh
Hi Rouslan,
Are you pointing the same file..? Ehh... I want to know about that CSS
printing file, in the head tag, for all Links of stylesheets, we have
phpmyadmin/pma.printcss.php?css_file_name something like this for all,
and it has something to do with Theme Manager as at last of the code
of this file it is
ThemeManager->printCss();
so, can you explain me that part and rest what i might havnt marked.
- Regards
Dron Rathore
@rouslan:
>> Hmmm.. there are no framesets in master
Well sorry for replying late, i tried every release of PMA and there
was none without framesets. The 2 framesets, one for navigation.php
and another one for tbl_structure or other, that we call main frame
havn't dwarfed(As far as i have found, might you be using different
release, if it is the case then please update me about it).
So, it took a while for me to figure out in what context i was talking
and i found it right. Just, instead of calling a click event of outer
anchor(refer to my previous mail) we can do it directly i.e. Adding a
#curr_db_name to window.location for each click in Navigation panel,
in that way we will not be using something extra for $Global and will
not cause any consequences with MaxNavigation and can solve the Marc's
Bug(refer to his mail).
Root conversation thread of Marc:
Le 2012-11-29 15:05, Rouslan Placella a ?crit :
> On 28/11/12 13:53, Marc Delisle wrote:
>> Rouslan Placella a ?crit :
>>> On 27/11/12 17:55, Marc Delisle wrote:
>>>> Hi Rouslan and list,
>>>>
>>>> I wonder whether this is a bug or a missing feature :) but
I noticed
>>>> that in some situations, for example following a foreign
link or picking
>>>> a table from the output of db_structure.php, the navi
panel does not
>>>> position itself to the new table.
>>>
>>> Sorry, but I don't understand what you mean.
>>
>> Example 1:
>> - in navi, click on sakila
>> - in main, click on the Browse Action on the actor line
>> - navi should show that actor is the current table
>>
>> Example 2:
>> - in navi, click on sakila
>> - in navi, under sakila, click on Tables then click on
inventory
>> - in main, for inventory_id 1, click on the film_id 1
>> - now, in main you are seeing a row from film, but the navi
panel no
>> longer shows that the current db is sakila
>
> I see.
>
> Well, it's not a bug. There is no such concept as a current db
(or table
> or other item) in the new navigation. The only "current"
thing that
> there is implemented is the current page in the db pagination.
So if you
> open something in a new tab, at least the db that the item
displayed on
> the page is associated with will be on the correct page in the
navigation.
>
> As far as implementing anything new goes, I think that the
issue with
> MaxNavigationItems that is discussed in a different thread
should be
> addressed first, as it will change some of the underlying logic
of the
> navigation system.
>
> Actually, Marc, would you please file this issue as a feature
request
> and the other one as a bug on the tracker. Thanks.
I filed the two issues.
--
Marc Delisle
http://infomarc.info