Quel est le principe?

La radio propose sur un site des liens vers des fichiers audio permettant de réécouter une émission radio de manière diférrée.

Avantages

Pouvoir écouter quand on veut et où l’on veut une émission.

Bon mais c’est la même chose que le podcast jusque là. Alors quel est la différence ?

La différence est déjà dans le mot BALADO-DIFFUSION, la diffusion en balade.
Balade: Selon le wiktionnaire:

Etymologie: Du verbe balader, lui-même venant de ballade (« poème chanté ») en raison des saltimbanques qui se déplaçaient sans destination particulière et qui chantaient des ballades pour demander l’aumône.

C’est ici toute l’idée: Balade, poème chanté, déplacement, mobilité. A notre époque il s’agit de pouvoir se promener avec de la musique. Totalement différent de Podcast, qui n’est qu’un mot commercial contraction de iPod(R) et de broadcast ==> diffusion sur iPod…

WTF?

Oui, je sais…

Faites comme moi, adieu podcast, bienvenue baladodiffusion et m…. à l’envahisseur (Pomme (R) )

TAG: #baladodiffusion #jeBosseSurMusiq3 #vivelamusiqueclassique

I had several:

Generating code coverage report, this may take a moment.PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 21503527 bytes) in /usr/share/php/PHPUnit/Util/Report/Node/File.php on line 406

And here is how it started:

At work we are using phpunit to test our framework, we flew from SimpleTest as there was no real integration with our tools and no real followup of the the product.

So to automate the test, as there is no “build” in php (interpreted vs compiled remember?) we ran it after each commit …

Until it tooks 30 minutes to run throught the whole set of tests…

Then we decided to run it locally before comitting… until it tooks up to 2 hours to run tests (yes we have slow laptops I know, at least 4 times slower than the servers).

Actually we use phpunit for recipe test, including database change, third parties, providers… everything from A to Z… and that needs a lot of time and CPU power…

So we solved the problem by running test in a cronjob, hourly on the integration server.

This was done running phpunit in command line


> phpunit --include-path ../code/ MyTestSuite.php


Of course as we had several tests suites and we had to put them all in one bigger testsuite… but that was not easy so we moved to the Phpunit config file, added code coverage reporting and send a mail everytime sometimes goes wrong

PhpunitConfig.xml

<?xml version="1.0" encoding="UTF-8"?>
<phpunit
         colors="true"
         >
         <testsuites>
         	<testsuite name="RTBF_Service">
         		<file>RTBF/Service/Rating/Adapter/AbstractPhpunittest.php</file>
         		<file>RTBF/Service/Rating/Adapter/MediaPhpunittest.php</file>
         	<--! ... -->
         	</testsuite>
         	<testsuite name="RTBF">
         		<file>RTBF/AclPhpunittest.php</file>
         	</testsuite>
         	<testsuite name="RTBF_Utility">
         		<file>RTBF/Utility/AjaxConnectorPhpunittest.php</file>
	         	<--! ... -->
         	</testsuite>
         	<--! ... -->
	</testsuites>
	<listeners>
  		<listener class="SimpleTestListener" file="PhpunitTestListener.php">
  		</listener>
  	</listeners>
  	<!--
	<logging>
		<log type="coverage-html" target="/reporting/phpunit/library/" charset="UTF-8" />
	</logging>
	-->
	<php>
		<ini name="memory_limit" value="2047M" />
	</php>
	<filter>
	  <blacklist>
	    <directory suffix=".php">library/code/Zend</directory>
	  </blacklist>
	</filter>
</phpunit>

PhpunitTestListener.php

class SimpleTestListener implements PHPUnit_Framework_TestListener
{
	private $emailContent=array(self::Error=>"",self::Failure=>"",self::Incomplete=>"",self::Skipped=>"");
	private $assertions=0;
	private $itemCount=array(self::Error=>0,self::Failure=>0,self::Incomplete=>0,self::Skipped=>0);
	private $totalItems=0;

	const Error="Error";
	const Failure="Failure";
	const Incomplete="Incomplete";
	const Skipped="Skipped";

	private function addEmailContent($severity,$test,$e){
		$result = $test->getResult();
		$traces = $e->getTrace();
		$continue=true;
		$tracingMessage="";
		for($i=1;$i<count($traces)&&$continue;$i++){
			if(isset($traces[$i]['file'])){
				$tracingMessage.=$traces[$i]['file'].":(".$traces[$i]['line'].")\n\t";
			}else{
				$continue=false;
			}
		}
		$this->itemCount[$severity]++;
		$this->emailContent[$severity].=$this->itemCount[$severity].")\t".get_class($test).'::'.$test->getName(TRUE)."\n\t".str_replace("\n","\n\t",PHPUnit_Framework_TestFailure::exceptionToString($e))."".$tracingMessage."\n\n";
		$this->totalItems++;
	}

	public function addError(PHPUnit_Framework_Test $test,Exception $e,$time){
		$this->addEmailContent(self::Error,$test,$e);
	}

	public function addFailure(PHPUnit_Framework_Test $test,PHPUnit_Framework_AssertionFailedError $e,$time){
		$this->addEmailContent(self::Failure,$test,$e);
	}

	public function addIncompleteTest(PHPUnit_Framework_Test $test,Exception $e,$time){
		$this->addEmailContent(self::Incomplete,$test,$e);
	}

	public function addSkippedTest(PHPUnit_Framework_Test $test,Exception $e,$time){
		$this->addEmailContent(self::Skipped,$test,$e);
	}

	public function startTest(PHPUnit_Framework_Test $test){
	}

	public function endTest(PHPUnit_Framework_Test $test, $time){
	}

	public function startTestSuite(PHPUnit_Framework_TestSuite $suite){
	}

	public function endTestSuite(PHPUnit_Framework_TestSuite $suite){
	}

	public function __destruct(){
		if($this->totalItems>0){
			// HIDDEN but concat everything from $this->emailContent nicely and send the mail
			//print("\n\nMail sent: ".$text."\n");
		}
	}
}

That’s it for the big picture…

And as you can see there are several point in the XML that are quite important:

memory limit 2047MBthat’s huge… but this is the price to pay to have a fully working code-coverage HTML report. As we are using suhosin we had to change the memory limit in suhosin too… and yes when the limit is 2048 MB don’t try to set the memory to 2048 MB it really means this is a limit you have to be under that limit (here 2047 MB).

2 Gigs!!! I know this is huge but believe me I went through several tries and 128 MB was not enought, nor 256 MB, nor 512 MB, not even 1 GB … I didn’t try to see where is my limit … I put 2 gigs and then it worked… we have about 30% of lines covered so I think that if we shift to 100% we will have to give more memory… I’m pretty sure, there is something leaking somewhere… but according to phpunit.de site… I have the answer remains: Give more memory

/etc/php5/conf.d/suhosin.ini

logging is commented out because logging needs xdebug and while we stay with ZendServer CE we do not have xdebug… (see my previous post for more info).

But the server which is not running Zend Server CE does!

So I commented out the line in the config to let developers run the unit test and pasted it as command line argument on the server’s cronjob.

phpunit --include-path ../code/ --coverage-html /reporting/phpunit/library/ --configuration PhpunitConfig.xml

the listener This is a simple easy listener. It’s always useful to have one sample so I pasted here above, feel free to copy, enhance… The only ‘hack’ we use it to call the send email on listener destruction, so the email will be sent at the end. But there is a drawback… if there is a php error somewhere, nothing is sent. And as nothing is sent when everythign goes well… we dont know if everythings goes well or if there is a real bug…
This problem will be addressed later. Stay tuned!

TODAY

• added update load and delete methods
• secured checks
• updated database for thumbnails

TOMORROW

• Thumbnails handling

TOYOTA

• ah bah dis donc, elle bonne celle-là !

Dans le petit lexique du B2B francophone (on devrait pas dire B2B), pour les communications “latin grec” vs “math sciences” voici un nouveau mot:

diacritique: du grec διακριτικός diacritikós, « qui distingue » (Thanks google & wikipedia)

en gros:
lettres_diacritique = [a-zA-Z] // et pas çöéà….

on en apprend tous les jours…

A+
–
I wish you good luck anyway with your new job.
The guy that hires you really is a lucky one ;-)

success,
–
Je suis en congé, mais bon on se reverra bientôt …
–
Bon vent :-)

Pour info http://howto.wired.com/wiki/Run_Mac_OS_X_on_an_Eee_PC

C’est quoi ton email @gmail ?
–
Salut Seb,

Tristesse de te voir partir. Ton mail lors de ta présentation aux élections sociales m’avait déjà serré le cœur.
Mais maintenant c’est pour du vrai.
Encore une personne que j’apprécie qui part et que je comprends très bien.
Je te souhaite le meilleur.

Bizzzz
–
Je te souhaite beaucoup de bonnes choses pour ton futur job (où que ce soit…;-))

–
Ha, bon tu quittes Skynet ??

Je vais essayer de passer … ;)

Et, tu vas ou ?

–
Bon ben… ce sera sans moi

Je te souhaite plein de bonnes choses là où tu vas… (tu peux me le dire maintenant !!!!!!!!!!!)
Je pense qu’on va te maudire pendant qques temps…mais t’inquiète pas ça va vite nous passer J

Merci pour ton agréable collaboration. Ce fût un plaisir de travailler avec toi.

A très bientôt j’espère

–
Quelle tristesse! Va falloir que je boive pour surmonter encore un départ de plus (avant le mien!)…
Je serai là !
A demain
–
Sebastien, since I’m not here tomorrow: good luck and success with your new job !!!!
–
I wish you a lot of success in your new job. It has always been very pleasant to work with you & the whole skynet team.
–
Merci!

A demain et bon voyage.
–

il est là…

il est beau…

et je l’aime: http://www.skynet.be/

Et franchement, après de 10 jours de travail d’affilé (oui je sais c’est nulle pour un syndicaliste mais quand on aime on ne compte pas) je commence seulement à accuser la fatigue post-natale…

merci à tous…