Quantopian's community platform is shutting down. Please read this post for more information and download your code.
Back to Community
I get quite often error by starting the backtest

Backtest Error
Something went wrong starting a full backtest.

I am not sure if the other have the same problem.

8 responses

This may be different because you said "full backtest". Varies but often "Execution timeout" on start here in under 15 seconds. Average retires ~4 maybe. Even if the backtest is for only a few days. There's a very tight timeout of some sort.
If you change your start date to a few trading days before end for less work by pipeline, any difference?

As a result of the "great improvement" since Sept 2018 for each bascktest run , I get about 10 'Error Execution timeout'.
In the previous 4 years, I didn't even know that such an error existed.
Very often I cannot save the changed settings (the “Save” button is not active).
Right now “Save” only responds to code changes but not other settings.

@Blue:

...If you change your start date to a few trading days before end for less work by pipeline...

What do you mean here? A concrect example maybe ?

The error you're addressing is -- "Something went wrong". That might have to do with pipeline, we don't know, but there's a chance.
I'm assuming your algorithm is set to run for the last 2 years or so, some number of years, and just suggesting you run a test by changing the start date, like, for example, to 01/02/2019, since the most recent date available right now is 01/04/2019. Thus covering only a few days.
Pipeline loads in chunks, some number of months at a time. A backtest of just the last few days has less pipeline work to do.
If it makes a difference, then I would try adding more and more time.

Ok, now I understand what you mean. But the errors I got have definitely little to do with what you said since the errors I got is just right after I clicked the backtest button. If I tried many times or after a while, it works again. I guess the Q has reduced the power of the server or has set some limitations. If "too many peoples" are doing the backtest, someone will get this error. But this is just my guess

Thomas,
My guess is the same as yours.

Hi all,

We recently diagnosed an issue that was causing timeouts during the code validation step. We are now working on a fix.

Thanks for flagging, everyone.

Disclaimer

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by Quantopian. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. No information contained herein should be regarded as a suggestion to engage in or refrain from any investment-related course of action as none of Quantopian nor any of its affiliates is undertaking to provide investment advice, act as an adviser to any plan or entity subject to the Employee Retirement Income Security Act of 1974, as amended, individual retirement account or individual retirement annuity, or give advice in a fiduciary capacity with respect to the materials presented herein. If you are an individual retirement or other investor, contact your financial advisor or other fiduciary unrelated to Quantopian about whether any given investment idea, strategy, product or service described herein may be appropriate for your circumstances. All investments involve risk, including loss of principal. Quantopian makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances.

@Cal,

Do you mean pipeline timeout? I experience no pipeline timeout when i run full backtest but in the contest, I get such an error and the algo gets disqualified.

Thank you
L