./configure --with-libdir=lib64 --with-mysql
This is probably obvious to most but I needed to do this to make PHP compile using mysql against the 64 bit header files:
So there was this bloke in the 3rd Century who was a christian scholar (probably big business at the time), named Hippolytus. He spent his time arguing how the Greek Philosophers were full of shit, and also ungodly (which let's face it is probably the main thing that pissed off Hippolytus).
So in the end Hippolytus was matyred (probably by Greeks), by being pulled apart by wild horses, which lead some bright spark to make him the patron saint of horses (they made him a saint, even though at the time he was also the first Antipope).
But then there was this bloke from greek mythology, also named Hippolytus, and he was the "unleasher of horses". (This Hippolytus supposedly also spurned Aphrodite, which suggests he wasn't into chicks because wasn't she like the hottest tart going around?)
So how did this co-incidence with the horses happen? Someone just made up a story of course. Probably the blokes who killed Hippolytus the Saint – they simply stabbed him, but then spread the story that they employed wild horses to do the job because who's going to fuck with blokes who go around pulling people apart with wild horses? Especially ones so learned in Greek mythology.
Man the shit you learn on Wikipedia.
So in the end Hippolytus was matyred (probably by Greeks), by being pulled apart by wild horses, which lead some bright spark to make him the patron saint of horses (they made him a saint, even though at the time he was also the first Antipope).
But then there was this bloke from greek mythology, also named Hippolytus, and he was the "unleasher of horses". (This Hippolytus supposedly also spurned Aphrodite, which suggests he wasn't into chicks because wasn't she like the hottest tart going around?)
So how did this co-incidence with the horses happen? Someone just made up a story of course. Probably the blokes who killed Hippolytus the Saint – they simply stabbed him, but then spread the story that they employed wild horses to do the job because who's going to fuck with blokes who go around pulling people apart with wild horses? Especially ones so learned in Greek mythology.
Man the shit you learn on Wikipedia.
Not sure exactly what the problem is (sorry about that, could be related to mongo but I suspect not), but PHP 5.3.6 is breaking (many, but not all pages are "unavailable") our li3 application. PHP 5.3.5 works fine, as does PHP 5.3.7-dev.
We recently moved from using Hudson to Jenkins (not by choice, our sysadmin just decided to do it one day). I know there's a big nerd-rage about Hudson vs. Jenkins but I honestly couldn't care less. I just want something that works. Well, from what we've seen, Hudson is more stable than Jenkins.Here are some of the problems we are getting (and fixes):
| Error | Fix |
|---|---|
| FATAL: Could not checkout null with start point 1234... Caused by: hudson.plugins.git.GitException: Error performing command: git checkout -f 1234... Command "git checkout -f 1234..." returned status code 1: error: unable to unlink old ' |
Jenkins keeps thinking one file has been modified locally, so (from the jenkins machine) git checkout that file and the tests will run fine. |
| Sometimes the Xvfb process crashes. You will only know because the tests will not stop trying to run, so any running time above 15 minutes means this has probably happened. | Restart Xvfb (which is supposed to be always running in the background): Xvfb -ac :99 & |
| Sometimes Jenkins doesn't want to checkout from git (sometimes for the same reason above, a file that has been "modified" locally, but sometimes for no apparent reason): ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway ERROR: Could not fetch from any repository FATAL: Could not fetch from any repository |
You have to login to the jenkins machine and manually git pull origin dev from the repo, and then run the tests again (via jenkins interface). |
| Caused by: hudson.plugins.git.GitException: Error performing command: git tag -a -f -m Jenkins Build #309 jenkins-oars-dev-309 Command "git tag -a -f -m Jenkins Build #309 jenkins-oars-dev-309" returned status code 128: error: insufficient permission for adding an object to repository database .git/objects error: unable to write tag file |
Not sure about this one. The selenium log was very big so I deleted it and the tests ran. The log is supposed to get rotated but maybe this didn't occur. |
| error: Your local changes to the following files would be overwritten by merge: Please, commit your changes or stash them before you can merge. |
These are local changes to the files on the test machine (not the jenkins machine). So from jenkins, there's a script to remotely update the files on the test machine, but in this case there were local modifications (not sure how that happened either). There's a plan to move the .test repos/installs to the jenkins machine so we won't need to do the remote update. However this plan has been devised by our "sysadmin", so might take a while to eventuate. Solution is to checkout the locally modified files on the test machine then do a git pull. |
This is really a note-to-self.
Sometimes when I run my unit tests in Lithium (li3) I get something like:
Exception thrown in lithium\data\Model::connection() on line 929: The data connection `test` is not configured.
Which doesn't make any sense because our unit test classes inherit from our own Unit class, which determines which data connection to use, however in our Unit test class setUp method we have to tell every class we need to use to use the correct data connection. Also, we never use the data connection "test". (The "test" data connection is the one li3 chooses by default when tests are run, which is why we had to overwrite it in our Unit class.)
So why is this happening? Because a class that I'm using as part of the testing includes another class in itself, and so we also have to manually tell this file which data connection to use.
Probably a better way to do this :D