Failure of process_jam_log.exe on windows

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Failure of process_jam_log.exe on windows

Boost - Testing mailing list
I tried to send these once before, but had issues...trying again...


On Sun, Oct 21, 2018 at 7:20 AM Tom Kent <[hidden email]> wrote:
On Fri, Oct 19, 2018 at 4:59 AM Tom Kent <[hidden email]> wrote:
Recently none of my windows runners have been executing. Initially, it was because of the addition of the unicode path [1], but I upgraded my scripts to python3 and fixed that (and they zipped up the test case [2]). The run.py script is still executed in python2 however (it isn't python 3 compatible!).

Now, each time I get to the end of a run, I'm seeing a popup saying "process_jam_log.exe has stopped working". Which prevents the upload of results and also prevents my scripts from continuing on. I'm going to try to run with python 2 again, but I doubt that is the issue since the execution of run.py is what calls process_jam_log.exe. 


Some more details. I re-ran process_jam_log.exe with --echo and got this at the end of the output, immediately before the crash.  

        line_start: "D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.1\dbg\adrs-mdl-64\lnk-sttc\thrd-mlt\libboost_system-vc141-mt-gd-x64-1_69.lib"
line 228408: "D:\teeks99-09\run\results\boost\bin.v2\libs\chrono\build\msvc-14.1\dbg\adrs-mdl-64\lnk-sttc\thrd-mlt\libboost_chrono-vc141-mt-gd-x64-1_69.lib"
        line_start: "D:\teeks99-09\run\results\boost\bin.v2\libs\chrono\build\msvc-14.1\dbg\adrs-mdl-64\lnk-sttc\thrd-mlt\libboost_chrono-vc141-mt-gd-x64-1_69.lib"
line 228409: "D:\teeks99-09\run\results\boost\bin.v2\libs\timer\build\msvc-14.1\dbg\adrs-mdl-64\lnk-sttc\thrd-mlt\libboost_timer-vc141-mt-gd-x64-1_69.lib"
        line_start: "D:\teeks99-09\run\results\boost\bin.v2\libs\timer\build\msvc-14.1\dbg\adrs-mdl-64\lnk-sttc\thrd-mlt\libboost_timer-vc141-mt-gd-x64-1_69.lib"
line 228410: compile-c-c++ D:\teeks99-09\run\results\boost\bin.v2\libs\graph\example\msvc-14.1\dbg\adrs-mdl-64\thrd-mlt\accum-compile-times.obj
        line_start: compile-c-c++
        target_directory( "compile-c-c++ D:\teeks99-09\run\results\boost\bin.v2\libs\graph\example\msvc-14.1\dbg\adrs-mdl-64\thrd-mlt\accum-compile-times.obj") -> "st/bin.v2/libs/graph/example/msvc-14.1/dbg/adrs-mdl-64/thrd-mlt"
*****Warning - can't open output file: D:\\teeks99-09\\run\\results\st/bin.v2/libs/graph/test/find_flow_cost_bundled_properties_and_named_params_test.test/msvc-14.1/dbg/adrs-mdl-64/thrd-mlt\test_log.xml
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


_______________________________________________
Boost-Testing mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Failure of process_jam_log.exe on windows

Boost - Testing mailing list
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:

https://github.com/boostorg/graph/commit/d51ba76e2020a30375640de742f5d394e98c7014#diff-e97299ad55a4013dc19889043aa464a5

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
_______________________________________________
Boost-Testing mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Failure of process_jam_log.exe on windows

Boost - Testing mailing list
In reply to this post by Boost - Testing mailing list
AMDG

On 10/22/2018 07:49 PM, Tom Kent via Boost-Testing wrote:

> I tried to send these once before, but had issues...trying again...
>
> On Sun, Oct 21, 2018 at 7:20 AM Tom Kent <[hidden email]> wrote:
>
>> On Fri, Oct 19, 2018 at 4:59 AM Tom Kent <[hidden email]> wrote:
>>
>>> <snip>
>>> Now, each time I get to the end of a run, I'm seeing a popup saying
>>> "process_jam_log.exe has stopped working". Which prevents the upload of
>>> results and also prevents my scripts from continuing on. I'm going to try
>>> to run with python 2 again, but I doubt that is the issue since the
>>> execution of run.py is what calls process_jam_log.exe.
>>>
>>> Thoughts? Any changes there?
>>>

Sorry about the delay in getting to this.  Can you check
whether this PR fixes the problem?
https://github.com/boostorg/regression/pull/45

In Christ,
Steven Watanabe
_______________________________________________
Boost-Testing mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Failure of process_jam_log.exe on windows

Boost - Testing mailing list


On Wed, Oct 24, 2018 at 2:15 PM Steven Watanabe via Boost-Testing <[hidden email]> wrote:
AMDG

On 10/22/2018 07:49 PM, Tom Kent via Boost-Testing wrote:
> I tried to send these once before, but had issues...trying again...
>
> On Sun, Oct 21, 2018 at 7:20 AM Tom Kent <[hidden email]> wrote:
>
>> On Fri, Oct 19, 2018 at 4:59 AM Tom Kent <[hidden email]> wrote:
>>
>>> <snip>
>>> Now, each time I get to the end of a run, I'm seeing a popup saying
>>> "process_jam_log.exe has stopped working". Which prevents the upload of
>>> results and also prevents my scripts from continuing on. I'm going to try
>>> to run with python 2 again, but I doubt that is the issue since the
>>> execution of run.py is what calls process_jam_log.exe.
>>>
>>> Thoughts? Any changes there?
>>>

Sorry about the delay in getting to this.  Can you check
whether this PR fixes the problem?
https://github.com/boostorg/regression/pull/45

That fix worked.

Tom 

_______________________________________________
Boost-Testing mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Failure of process_jam_log.exe on windows

Boost - Testing mailing list
AMDG

On 10/24/2018 04:41 PM, Tom Kent via Boost-Testing wrote:

> On Wed, Oct 24, 2018 at 2:15 PM Steven Watanabe via Boost-Testing <
> [hidden email]> wrote:
>
>> <snip>
>> Can you check
>> whether this PR fixes the problem?
>> https://github.com/boostorg/regression/pull/45
>
>
> That fix worked.
>

Thanks.  I just merged it.  I'd recommend keeping
an eye out in case it broke something else, though.
It shouldn't, but with process_jam_log you never know.

In Christ,
Steven Watanabe
_______________________________________________
Boost-Testing mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-testing