retry mage-test-stand setup if it fails

[tkn98]

Reference: #283

See: http://docs.travis-ci.com/user/build-timeouts/

[ktomk]

We fixed the underlying issue upstream in magerun and it is already part of mage test stand (AOEpeople/MageTestStand@f2038ef). These updates becamse important for working magento downloads. They are technically not that important for the retry-issue this PR was originally about. Just saying.

[sprankhub]

Thanks! Any idea why it fails during the cleanup? It fails during the following command:

rm -rf /tmp/mageteststand.25JSVJ94

But it also seems that he cleans up too early. It does not finish the test FireGento_Pdf_Test_Model_CreditmemoTest::itShouldReturnAZendPdf, but cleans up before. It does not show any error though, which is strange...?

[sprankhub]

Idea: Older versions probably fail because Magento < 1.9 does not natively support PHP 5.4 / 5.5...

[tkn98]

I don't understand why the exit status differs between the builds. perhaps the download doesn't work. because curl is silenced this is not visible. I will try the one or other thing to make things more visible.

[Schrank]

@tkn98 You are great, thanks for your help!

[tkn98]

From my end this now looks like a failing test to me: FireGento_Pdf_Test_Model_CreditmemoTest::itShouldReturnAZendPdf

This test is failing hard, that means with either a non catchable fatal error (hinted by exit status 255) or even some other hard failure that the php binary crashed. I don't have a good reference at hand that explains all PHP exit codes, I know that 255 is an error.

I can't say whether or not -d display_errors=1 does actually work as intended in that case. I'd say it normally should work. That then again would be a hint that it's not an error but just a crash.

Both these statements are speculative. So they are of no concrete help and don't take them for real.

Maybe if you look into the test you can find out what is going on.

[tkn98]

@sprankhub The file build/travis/mageteststand-setup.sh is not used any longer and can be removed. It's just a forgotten leftover from testing the build.

[sprankhub]

@tkn98 00dde26 ;) Thanks!

By the way, this is a good explanation of PHP error code 255. I still try to fix the error. I encountered a bug (ccf839d), but it does not seem to be the issue.