You need to sign in to do that
Don't have an account?
TehNrd
System.Exception: Too many script statements: 50001...new System Log problem
So I think the new system log is causing some of the test classes to fail. To test the "bulk" of my triggers most test classes process 200 records. Yet on opportunities we have tons of workflow, formulas, validations, etc. This is causing the Debug Log to explode on opportunity Triggers causing to many script statements.
I thought when salesforce.com updated instances it was going to run all the test classes to see if they pass? If so what is going to happen when you update our production instance?
Also what can I do to fix this problem.
Thanks,
Jason
I thought when salesforce.com updated instances it was going to run all the test classes to see if they pass? If so what is going to happen when you update our production instance?
Also what can I do to fix this problem.
Thanks,
Jason
Message Edited by TehNrd on 11-06-2007 04:28 PM
Summer:
Code:
Winter: Only a little bit as I hit the 50,000 limit and it errors out.
EDIT: I was wrong, its not erroring out but it is reaching the maximum debug lenghth and then not showing me Apex metrics.
Code:
I apologize if I come across as a little rough, but how is this useful? I can't even see relevent Apex information and it breaks most of my test classes.
Thanks,
Jason
Message Edited by TehNrd on 11-09-2007 11:16 AM
It does sound like a serious roadblock if your existing tests fail due to the new deep system log.
Are you sure these two orgs have all the same triggers and workflow rules in place?
We have some experts that can look into your issue, but you will have to file a case.
What about this...
Do validation rules, workflow, etc, have script statements?
Perhaps now that these are being logged they are added against my script limit?
All I know is that the tests pass in Summer and fail in Winter. I'm just trying to figure out what changed (my code didn't, its identical). I saw that the log exploded in size so I just assumed the script statements where related.
Message Edited by TehNrd on 11-08-2007 01:52 PM
Apparently it was caused by a System.Debug statement pumping out too much data. I guess this adds up to a lot of script statements. My apologies for all the noise. I still like the old Summer log though as it shows a nice clean look at Apex metrics.
It's been one of those weeks.....
Message Edited by TehNrd on 11-08-2007 05:40 PM