similar to: [PATCH] Make test_compression a little more forgiving

* Use `mktemp` instead of playing with date(1). * Use -f instead of removing the file every time. * "echo ERROR; exit 1" is what die() is for. * Some cosmetic renamings ('k' to 'comp' for compression etc). * Remove the MacOSX comment. It's not MacOSX specific, and it's not a problem anyway. The number behaves just right. * Remove the $((${size}+10)). It's

On Nov 26 01:25:25, hans at stare.cz wrote: > On Nov 25 23:56:05, mvanb1 at gmail.com wrote: > > Op 25-11-14 om 23:39 schreef Jan Stary: > > > Is there a reason the test scripts are calling bash? > > > > The change from sh to bash was made a little more than a year > > ago. The mailing list thread accompanying this change can be > > found here: >

On Nov 25 00:43:22, mle+la at mega-nerd.com wrote: > http://downloads.xiph.org/releases/flac/beta/ > Please test. Running 'make fullcheck' fails for me like this: $ pwd /home/hans/src/flac-1.3.1pre1/test $ make fullcheck FLAC__TEST_LEVEL=1 FLAC__TEST_WITH_VALGRIND=no ./test_libFLAC.sh /bin/sh: ./test_libFLAC.sh: No such file or directory *** Error 1 in

Op 25-11-14 om 23:39 schreef Jan Stary: > Is there a reason the test scripts are calling bash? The change from sh to bash was made a little more than a year ago. The mailing list thread accompanying this change can be found here: http://lists.xiph.org/pipermail/flac-dev/2013-September/004374.html

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-11-24 9:49 PM, mark4o wrote: > $ make check ... Original file size 441044 bytes. Compression > level 0, file size 421389 bytes. ./test_compression.sh: line 42: > let: last_size=: syntax error: operand expected (error token is > "=") I can reproduce on MacOS X 10.8.5. It doesn't seem to like the assignment

Op 20-10-14 om 16:36 schreef Martijn van Beurden: > Op 20-10-14 om 16:31 schreef lvqcl: >> But your patch changes only two last presets (-7 and -8) so >> -6 stays unchanged. ( IIRC it should have >> "tukey(5e-1);partial_tukey(2)" as its apodization string >> instead of current "tukey(5e-1)" ). > > .... okay, I really don't know how it is

Hi all, As people may have seen there's a pre-release here: http://downloads.xiph.org/releases/flac/beta/ Specifically: flac-1.3.1pre1.tar.xz : The source code flac-1.3.1pre1-win.zip : Windows 32 and 64 bit binaries Please test. I'm particularly interested in hearing about the windows binaries which were cross compiled from Linux to Windows. Unfortunately there is a bug

Martijn van Beurden wrote: > This patch changes the settings associated with compression > levels 6, 7 and 8. With this patch, -e is no longer used, but > instead apodization functions are added. This should improve > compression with at least 95% of all material. Independent tests > show that this is probably the case. But your patch changes only two last presets (-7 and -8) so

Attached is a patch for 'test_compression.sh'. Interestingly, I noticed compression level '0' is omitted, so I've added it in. Also, I tested this on a 24bit/96kHz FLAC file and the test failed between compression level 0 and compression level 1 -- the file size was greater with a compression level of 1, rather than 0. The test works on 'noisy-sine.wav'. It may be

ldisk.c32 is a Lua module that provides information about disks to Lua scripts The example script com32/lua/test/detect_disks.lua uses it to implement some- thing akin to 'disk.c32'. The name 'ldisk.c32' was chosen to avoid a name-clash with 'disk.c32'. --- com32/lua/src/Makefile | 1 + com32/lua/src/ldisk.c | 103

hello my server is centos 6 64 bit while installing dovecot i get this error Failed to run: ./test-compression what could be the reason. could someone guide me please Version dovecot-ce-2.3.0-1 0 / 7 tests failed ==21130== Conditional jump or move depends on uninitialised value(s) ==21130== at 0x349B00ACB2: ??? (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x349B00AEA9: ??? (in

As I haven't heard any complaints concerning the proposal for retuning compression levels which I posted a few months ago, here's the patch that enables them, with the change proposed by lvqcl. This patch changes the settings associated with compression levels 6, 7 and 8. With this patch, -e is no longer used, but instead apodization functions are added. This should improve

Hi all, The compression levels in FLAC have been kept the same for a long time, only preset 6, 7 and 8 got a slight change years ago. However, as some parts of FLAC got much faster, I felt it was time to retune the presets, to better use the now much faster parts. There is a proposal at github here: https://github.com/xiph/flac/pull/576 I think there might be strong opinions on this matter.

Hello list, I've configured dovecot-2.3.0 on CentOS 6 with the following options. CFLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fno-strict-aliasing"? ? \ LDFLAGS="-Wl,-z,now -Wl,-z,relro"??? \ ./configure???????????????????????????????????? \ ??? --docdir=/usr/share/doc/dovecot-2.3.0?? \

I setup new server with dovecot 2.1.12 and mboxes from backup (moboxes was used with dovecot 1.1.6). OS: FreeBSD 8.3-STABLE, amd64. All index files from dovecot 1.1.6 has been deleted. Some times dovecot processes aborted. E. g. Jan 25 03:01:52 ost dovecot: lda(user at example.ru): Panic: file mail-transaction-log-file.c: line 1694 (mail_transaction_log_file_map): assertion failed:

Hi Sadaf, Out of curiosity, what sorts of things have you tried to fix this? For example, after playing around with this a bit, if I remove your "eps" parameter from your `ranges` list, it works. Perhaps you should try tweaking the values you pick for your parameters. You don't even have to put it in the `tune` function to get an idea of the ranges you should use: R>

I've run into a problem with `doveadm backup` (2.2 rc2 and 20130226) I did not notice in 2.1.15 doveadm backup [-Dv] -R -u cyrtest1 at iai.uni-bonn.de -m INBOX imapc: => crashes (signal 6 with acl plugin configured, sig 11 without acl) If this is considered a bug (not just because of the crash but in the meaning of "my configuration should work") it would be great if it could be

Op 03-12-14 om 18:14 schreef Brian Willoughby: > I would like to point out that 'quiet' material is common when making original recordings. This is probably a misunderstanding: I said that the material that suffers is usually quiet, not that all quiet material suffers. > I do a great deal of live recording, and the levels are always quiet in order to guard against clipping. These

Maybe I should've started a new thread with this question (it was in the /proc/sys/vm/bdflush thread), so I am now :) According to tests performed for this article: http://www-106.ibm.com/developerworks/linux/library/l-fs8/ "ext3's data=journal mode is incredibly well-suited to situations where data needs to be read from and written to disk at the same time." This is the

Eh - I'd say "Big" new features (hey, LLVM supports DWARFv5, or Split DWARF, or DWARF type units, or DWARF compression (though I don't think I wrote any release notes for several of those features that I implemented)). I wouldn't bother release noting changes in output format for tools we don't consider to have stable output, or changes in robustness/better error