aboutsummaryrefslogtreecommitdiffstats
path: root/testing/lazperf
Commit message (Collapse)AuthorAgeFilesLines
* testing/lazperf: upgrade to 1.2.0Bradley J Chambers2018-06-011-2/+2
|
* testing/[various]: fixes on s390xTuan M. Hoang2018-02-131-1/+1
| | | | | | | | | | | | need py-numpy : py-cpuinfo, websockify, py-gnuplot, py-scipy, py-fonttools, py-matplotlib, py-opengl need openblas : harminv no jit support : texlive no arch support : tcc, nim, perl-sys-syscall radare2 : need disabling debugger thermald : seems to be intel-only thing lazperf : io tests hang
* [various]: unify names of licenses according to SPDXJakub Jirutka2017-12-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit updates $license variable in all APKBUILDs to comply with short names specified by SPDX version 3.0 [1] where possible. It was done using find-and-replace method on substrings inside $license variables. Only license names were updated, not "expressions" specifying relation between the licenses (e.g. "X and Y", "X or Y", "X and (Y or Z)") or exceptions (e.g. "X with exceptions"). Many licenses have a version or multiple variants, e.g. MPL-2.0, BSD-2-Clause, BSD-3-Clause. However, $license in many aports do not contain license version or variant. Since there's no way how to infer this information just from abuild, it were left without the variant suffix or version, i.e. non SPDX compliant. GNU licenses (AGPL, GFDL, GPL, LGPL) are especially complicated. They exist in two variants: -only (formerly e.g. GPL-2.0) and -or-later (formerly e.g. GPL-2.0+). We did not systematically noted distinguish between these variants, so GPL-2.0, GPL2, GPLv2 etc. may mean GPL-2.0-only or GPL-2.0-or-later. Thus GNU licenses without "+" (e.g. GPL2+) were left without the variant suffix, i.e. non SPDX compliant. Note: This commit just fixes format of the license names, no verification has been done if the specified license information is actually correct! [1]: https://spdx.org/licenses/
* testing/lazperf: disable on armhf due to segfault in testsJakub Jirutka2017-10-081-1/+1
| | | | | | | | | | | | | | | | | | | Running tests... Test project /home/buildozer/aports/testing/lazperf/src/laz-perf-1.1.0/build Start 1: io_tests 1/3 Test #1: io_tests .........................***Exception: SegFault 0.24 sec Start 2: lazperf_tests 2/3 Test #2: lazperf_tests .................... Passed 1.18 sec Start 3: stream_tests 3/3 Test #3: stream_tests ..................... Passed 0.00 sec 67% tests passed, 1 tests failed out of 3 Total Test time (real) = 1.44 sec The following tests FAILED: 1 - io_tests (SEGFAULT) Errors while running CTest
* testing/lazperf: new aportBradley J Chambers2017-08-291-0/+37
https://github.com/hobu/laz-perf Alternative LAZ implementation for C++ and JavaScript