[GRASS-dev] I've tripled GRASS's I/O speed

[Vaclav Petras]

On Mon, Oct 5, 2015 at 3:21 PM, Seth Price <seth at planet.com> wrote:

> Hi, I've spent the last two or three hours trying to get GRASS' unit tests
> running. With a fresh source tree, the best I can get is ~9% of the tests
> passing:
>

Oh, sorry about that, you need to use basic instead of full NC location.
The datasets are unfortunately incompatible and the whole thing is
undocumented because we never made the switch official.

https://grass.osgeo.org/download/sample-data/

But since NC basic will be replaced by standardized sample dataset (which
is partially reason for the confusing situation), use this new dataset
instead.

https://trac.osgeo.org/grass/wiki/SampleDataset (goes here:
http://www4.ncsu.edu/~hmitaso/grasswork/grassbookdat4ed/)

Have you noticed that you can view the errors in an HTML report?

"grass.gunittest.main writes a text summary to standard output and it
creates an HTML report from all tests in all testsuite directories inside
the directory tree. The report is placed in testreport by default. Open
file testreport/index.html in you web browser to inspect it."

https://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html#running-tests-and-creating-report

seths-mbp:grass-7.1.svn_src_snapshot_2015_09_19 sprice$ grass71 --text
> ../nc_spm_08_grass7/PERMANENT/
>
> [...]
>
> GRASS 7.1.svn
> (nc_spm_08_grass7):/usr/local/grass/grass-7.1.svn_src_snapshot_2015_09_19 >
> python -m grass.gunittest.main --location
> /usr/local/grass/nc_spm_08_grass7/ --location-type nc
>
> test_g_list from ./general/g.list failed (1 test failed)
>
> test_g_remove from ./general/g.remove failed (2 tests failed)
>
> test_overwrite from ./general/g.rename failed (3 tests failed)
> [...]
>
> test_vto3d from ./vector/v.to.3d failed (1 test failed)
>
> test_vwhat_layers from ./vector/v.what failed (1 test failed)
>
> test_vwhat_ncspm from ./vector/v.what failed (4 tests failed)
>
>
> Executed 127 test files in 0:00:55.959398.
>
> From them 12 files (9%) were successful and 115 files (91%) failed.
>
> GRASS 7.1.svn
> (nc_spm_08_grass7):/usr/local/grass/grass-7.1.svn_src_snapshot_2015_09_19 >
>
> I'd really like to work on these unit tests. Any ideas as to where I'm
> going wrong? I feel like I've exhausted the various knowledge bases
> available online.
> Thanks,
> Seth
>
>
> On Fri, Oct 2, 2015 at 11:25 AM, Vaclav Petras <wenzeslaus at gmail.com>
> wrote:
>
>>
>>
>> On Fri, Oct 2, 2015 at 12:49 PM, Seth Price <seth at planet.com> wrote:
>>
>>> ..by adding the option of a few different compression schemes, including
>>> LZ4. I've had the ticket open for a week now with no responses. I'd love to
>>> get it incorporated into trunk. For more info, see here:
>>> https://trac.osgeo.org/grass/ticket/2750
>>>
>>
>> Hi,
>>
>> thanks for the reminder. This looks really good. Can you provide a test
>> which would do a trivial operation (like the benchmark in the ticket)
>> ideally using Python and gunittest [1]? Please, let me know if you don't
>> know where to start.
>>
>> Vaclav
>>
>> [1]
>> https://grass.osgeo.org/grass71/manuals/libpython/gunittest_testing.html
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20151005/8c663d5d/attachment.html>