[tlbuild] makejvf.test test failures
Mojca Miklavec
mojca.miklavec.lists at gmail.com
Sun Jul 23 09:17:25 CEST 2017
On 12 July 2017 at 00:34, Hironobu Yamashita wrote:
> Hi Mojca,
>
> Sorry for inconvenience, but the test is successful in my two environment,
>
> * Mac OS X El Capitan 11.6
> * Win32 (MSVC12)
>
> Which test fails? min10, or tmin10?
$ cat Work/texk/makejvf/test-suite.log
===============================================
makejvf (TeX Live) 1.1a: ./test-suite.log
===============================================
# TOTAL: 1
# PASS: 0
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: makejvf
=============
../../../texk/makejvf/tests/tmin10.vf tmin10.vf differ: char 856, line 1
FAIL makejvf.test (exit status: 1)
>From hex dump:
Original:
00000350: 9101 8a1f 9ff7 33c0 8121 6df2 0000 0087 ......3..!m.....
00000360: 0000 2149 0007 b29e 9106 287e 9f08 cc40 ..!I......(~...@
The file built on that machine:
00000350: 9101 8a1f 9ff7 33c1 8121 6df2 0000 0087 ......3..!m.....
00000360: 0000 2149 0007 b29e 9106 287e 9f08 cc3f ..!I......(~...?
So:
0x357: c1 instead of c0
0x36f: 3f instead of 40
Is there any volunteer to modify the build system in such a way that
it will always print this information to stdout/stderr? (Of course not
the vf file differences, but at least the more verbose log.) At the
moment it just says that a test failed, but I now need to log in to
some weird location to be able to get the necessary logs.
Mojca
More information about the tlbuild
mailing list