PrusaSlicer-NonPlainar/t
Lukas Matena 07282eb24d Fixed unit tests when run with range checks on std::vector
There was a bug in unit tests that led to generating the wipe tower with non-normalized preset.
This caused out-of-bounds access into max_layer_height vector in fill_wipe_tower_partitions.
The problem surfaced in https://github.com/prusa3d/PrusaSlicer/issues/2288.
I quickly patched additional normalization of the preset to prevent this from happening.

Also, an assert in the same function turned out to trip on one of the tests.
This one was commented out for now and will (hopefully) be looked into later.

Function Print::apply_config was renamed to apply_config_perl_tests_only so everyone
sees its current purpose and does not mistake it for the more important Print::apply.
2019-05-22 16:48:20 +02:00
..
angles.t
avoid_crossing_perimeters.t
bridges.t
clean_polylines.t
clipper.t
collinear.t
combineinfill.t Fixed unit tests when run with range checks on std::vector 2019-05-22 16:48:20 +02:00
config.t
cooling.t
custom_gcode.t
dynamic.t
fill.t Fixed unit test after splitting the external fill pattern to top/bottom. 2019-02-25 09:11:20 +01:00
flow.t Fix of the previous commit 2019-05-14 15:48:00 +02:00
gaps.t
gcode.t
geometry.t
layers.t
loops.t
multi.t
perimeters.t Perimeters test modified to skip lines M73 2018-07-13 10:46:30 +02:00
polyclip.t
print.t Fixed unit tests when run with range checks on std::vector 2019-05-22 16:48:20 +02:00
retraction.t
shells.t Fix of the previous commit 2019-05-14 15:48:00 +02:00
skirt_brim.t Fixed unit tests when run with range checks on std::vector 2019-05-22 16:48:20 +02:00
slice.t
support.t
thin.t