|
Boost Testing : |
Subject: Re: [Boost-testing] Failure of process_jam_log.exe on windows
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-10-24 18:11:17
AMDG
On 10/22/2018 07:49 PM, Tom Kent via Boost-Testing wrote:
> <snip>
>> -> "st/bin.v2/libs/graph/example/msvc-14.1/dbg/adrs-mdl-64/thrd-mlt"
>> *****Warning - can't open output file:
>> line 228411:
>> line_start:
>> line 228412: call
>> "D:\teeks99-09\run\results\boost\bin.v2\standalone\msvc\msvc-14.1\adrs-mdl-64\archt-x86\msvc-setup.bat"
>>> nul
>> line_start:
>> line 228413: cl /Zm800 -nologo
>> @"D:\teeks99-09\run\results\boost\bin.v2\libs\graph\example\msvc-14.1\dbg\adrs-mdl-64\thrd-mlt\accum-compile-times.obj.rsp"
>> line_start:
>> line 228414:
>> line_start:
>> line 228415: accum-compile-times.cpp
>> line_start: accum-compile-times.cpp
>>
The problem is this test case, which was
added to the test suite here:
process_jam_log incorrectly interprets the name
of the source file as the name of a compile action.
(like msvc.compile-c-c++)
In Christ,
Steven Watanabe