Mercurial > hg > orthanc
comparison TODO @ 5349:0223315871e8
note
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Tue, 04 Jul 2023 12:00:14 +0200 |
parents | b376abae664a |
children | b551e4fdc708 b074943fca35 |
comparison
equal
deleted
inserted
replaced
5348:303e930fff0f | 5349:0223315871e8 |
---|---|
329 * Add more complex testing scenarios like data-migration, change of | 329 * Add more complex testing scenarios like data-migration, change of |
330 configuration files, multiple orthanc interacting togethers with various | 330 configuration files, multiple orthanc interacting togethers with various |
331 config. This should probably look like the python toolbox tests ... | 331 config. This should probably look like the python toolbox tests ... |
332 - add a test to validate Modalities and Peers stored in DB are not lost | 332 - add a test to validate Modalities and Peers stored in DB are not lost |
333 while upgrading from one version to the other (Sylvain) | 333 while upgrading from one version to the other (Sylvain) |
334 * On Ubuntu 20.04, accesses to unitialized memory are sometimes | |
335 reported in libgjpeg by valgrind, if running the following command | |
336 (this is probably unrelated to Orthanc): | |
337 $ ./Start.sh --force Orthanc.test_bitbucket_issue_141 Orthanc.test_create_pdf Orthanc.test_decode_brainix_as_jpeg | |
334 | 338 |
335 | 339 |
336 --------------------- | 340 --------------------- |
337 External applications | 341 External applications |
338 --------------------- | 342 --------------------- |