Test to isolate the unit test causing the segfault in WMS GetPrint #36198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@pblottiere random thought -- maybe this issue only shows up on release builds (i.e. Travis), and not our local builds because we all run debug builds? |
pblottiere
force-pushed
the
debug_getprint
branch
2 times, most recently
from
3af6182
to
ee1c5b3
Compare
I tried to run the I'm still trying to isolate the culprit more precisely with Travis. |
pblottiere
force-pushed
the
debug_getprint
branch
7 times, most recently
from
29818ca
to
73a7ae3
Compare
pblottiere
force-pushed
the
debug_getprint
branch
from
73a7ae3
to
b8d62a6
Compare
pblottiere
force-pushed
the
debug_getprint
branch
from
b8d62a6
to
a534605
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Since I cannot replicate the segfault locally, I'd like to find which specific test is causing the segmentation fault before investigating more.
It seems to be related to
test_wms_getprint_two_mapsbut I'd like to be sure.basicandstyle: 5xbasic,style,groupandlegend: 5xbasic,style,group,legend,srs,scale,gridandrotation: 5xbasic,style,group,legend,srs,scale,grid,rotation,opacity,selection,opacity_postandhilight: 5xbasic,style,group,legend,srs,scale,grid,rotation,opacity,selection,opacity_post,hilight,label: 5xbasic,style,group,legend,srs,scale,grid,rotation,opacity,selection,opacity_post,hilight,labelandatlas: 5x success and 5x failbasic,style,group,legend,srs,scale,grid,rotation,opacity,selection,opacity_post,hilight,label,atlasandtwo_maps:Suspicious tests:
atlas: 5x (no fail when no other tests)