This content has been marked as final.
Show 6 replies
-
1. Re: LargeMessageTest hanging
timfox Nov 2, 2009 4:21 AM (in response to ataylor)Could you just set the default address full message policy back to PAGE for now?
-
2. Re: LargeMessageTest hanging
ataylor Nov 2, 2009 4:26 AM (in response to ataylor)Ive applied the same fix to PagingStoreImplTest
-
3. Re: LargeMessageTest hanging
ataylor Nov 2, 2009 4:28 AM (in response to ataylor)"timfox" wrote:
Could you just set the default address full message policy back to PAGE for now?
If you like but i have fixed the tests for now. I still think its a better out of the box configuration. Maybe we could have the default mode set on the configuration? -
4. Re: LargeMessageTest hanging
timfox Nov 2, 2009 4:33 AM (in response to ataylor)Problem is, I have a suspicion that some of the paging tests don't explicitly set the mode to PAGE, they just assume the default is PAGE. This could mean the tests silently pass when we change default to BLOCK, but actually they're not doing any paging.
Clebert needs to check this. -
5. Re: LargeMessageTest hanging
ataylor Nov 2, 2009 4:39 AM (in response to ataylor)"timfox" wrote:
Problem is, I have a suspicion that some of the paging tests don't explicitly set the mode to PAGE, they just assume the default is PAGE. This could mean the tests silently pass when we change default to BLOCK, but actually they're not doing any paging.
Clebert needs to check this.
I can go thru and check them if you want, shouldnt take too long. -
6. Re: LargeMessageTest hanging
timfox Nov 2, 2009 4:43 AM (in response to ataylor)Ok fair enough.
I guess if you just go through every paging test and make sure it explicitly sets mode to PAGE that should be enough.
There are paging tests scattered in various different places though.