squashfs-tools-ng.git/tests, branch v1.0.3

Backport changes to the test setup

2020-11-02T10:49:44+00:00

Signed-off-by: David Oberhollenzer

Add a test case for tar2sqfs root becomes file & link filtering

2020-10-31T17:34:37+00:00

Signed-off-by: David Oberhollenzer

Remove tar test cases for file flags (not applicable)

2020-09-03T16:28:09+00:00

Signed-off-by: David Oberhollenzer

Cleanup: reduce tar test cases to a few generic C files

2020-09-03T15:01:32+00:00

This commit removes the existing tar test cases that simply call the generic test case function with several different paths with generic test case source files that are parameneterized via the pro-processor. For each tar archive, a separate test case is generated. On the one hand, this reduces the test source code to practically nothing. On the other hand, a test binary is generated for every distinct test case, instead of one per group and we get more detailed insights if something goes wrong. Signed-off-by: David Oberhollenzer

Cleanup copy & paste mess in the tar parser test cases

2020-09-03T12:37:28+00:00

Many of the patterns tested are very repetetive. This commit moves the two common test cases out into helper functions and uses them for the test cases. Signed-off-by: David Oberhollenzer

Fix nonexistant gnu tar sparse format 1.0 support

2020-09-02T09:19:11+00:00

Contrary to previous claims, support for the GNU tar sparse format 1.0 was missing entirely (the newest of their 3 different sparse mapping formats). This oversight wasn't caught, because the unit test was compiling the wrong source file and tar2sqfs had no problem processing the test file because it is still a valid POSIX-ish tar archive (but the sparse part was missing and the mapping embedded in the file). Signed-off-by: David Oberhollenzer

Add a libtar test case for a completely filled link target field

2020-08-16T12:01:19+00:00

Signed-off-by: David Oberhollenzer

Fix compressor config union size test

2020-06-04T09:21:10+00:00

Signed-off-by: David Oberhollenzer

Strictly enfore min/max dictionary size in XZ & LZMA compressors

2020-06-04T03:38:40+00:00

Signed-off-by: David Oberhollenzer

Fix: zstd: actually set the compression level from the options

2020-05-21T19:24:28+00:00

In the zstd compressor, the compression level from the configuration structure wasn't used at all. Instead, the zstd compressor was told to use level 0 and compressor options with that parameter were written to disk. This commit makes sure the level parameter is propperly initialized. Reported-by: Sébastien Gross Signed-off-by: David Oberhollenzer