Re: [boost] [system] [teeks99] Mass test failures on MSVC-14.0
On 02/26/18 17:20, Tom Kent wrote:
On Mon, Feb 26, 2018 at 6:56 AM, Andrey Semashev via Boost <boost@lists.boost.org <mailto:boost@lists.boost.org>> wrote:
On 02/26/18 15:43, Tom Kent via Boost wrote:
On Sat, Feb 24, 2018 at 3:45 PM, Andrey Semashev via Boost < boost@lists.boost.org <mailto:boost@lists.boost.org>> wrote:
Hi,
Most of Boost.System tests are failing on the teeks99-09-f-win2016-64on64 tester, MSVC-14.0[1]. The test logs don't show any errors and I can't reproduce it locally. I'm seeing similar test failures in other libraries, like Boost.Atomic for example, and the links point to Boost.System.
Is it possible to get the error log from the tester?
>> > Here's all 82MB of it: > http://boost.teeks99.com/temp/teeks99-09-f-results-bjam-2018-02-26.log <http://boost.teeks99.com/temp/teeks99-09-f-results-bjam-2018-02-26.log> > > But be warned, I just moved the -09 runner onto a new (Win 2016) VM about a > week ago, and there have been some teething issues. If all goes well, the > -f run should hit again in the next 24-48hrs.
The link returns 403: Forbidden.
Try again now. Sorry about that.
I got the log now, thanks. The relevant part seems to be this: msvc.link.dll D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll call "D:\teeks99-09\run\results\boost\bin.v2\standalone\msvc\msvc-14.0\adrs-mdl-64\archt-x86\msvc-setup.bat" amd64 >nul link /NOLOGO /INCREMENTAL:NO /DLL /DEBUG /MACHINE:X64 /MANIFEST /subsystem:console /out:"D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll" /IMPLIB:"D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.lib" @"D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll.rsp" if %ERRORLEVEL% NEQ 0 EXIT %ERRORLEVEL% Creating library D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.lib and object D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.exp msvc.manifest.dll D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll if exist "D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll.manifest" ( call "D:\teeks99-09\run\results\boost\bin.v2\standalone\msvc\msvc-14.0\adrs-mdl-64\archt-x86\msvc-setup.bat" amd64 >nul mt -nologo -manifest "D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll.manifest" "-outputresource:D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll;2" ) 'mt' is not recognized as an internal or external command, operable program or batch file. ...failed msvc.manifest.dll D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.lib D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.pdb D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.pdb D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.pdb D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.pdb D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.pdb... ...removing D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.dll ...removing D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.lib ...removing D:\teeks99-09\run\results\boost\bin.v2\libs\system\build\msvc-14.0\dbg\adrs-mdl-64\thrd-mlt\boost_system-vc140-mt-gd-x64-1_67.pdb I think, this problem has been discussed on the list not long ago - `mt` being not found on the system after some MSVC update: http://boost.2283326.n4.nabble.com/build-msvc-14-linker-step-failing-tc47017... Looks like MSVC needs to be reinstalled or installed on a separate machine. Will you be able to fix this?
Am 26.02.2018 um 15:52 schrieb Andrey Semashev via Boost:
On 02/26/18 17:20, Tom Kent wrote:
'mt' is not recognized as an internal or external command, operable program or batch file. ...failed msvc.manifest.dll
I think, this problem has been discussed on the list not long ago - `mt` being not found on the system after some MSVC update:
Looks like MSVC needs to be reinstalled or installed on a separate machine. Will you be able to fix this?
Most likely the path to the SDK tools is missing in the setup: "C:\Program Files (x86)\Windows Kits\10\bin\x64" or "C:\Program Files (x86)\Windows Kits\10\bin\x86" Ciao Dani
On Mon, Feb 26, 2018 at 11:12 AM, Daniela Engert via Boost < boost@lists.boost.org> wrote:
Am 26.02.2018 um 15:52 schrieb Andrey Semashev via Boost:
On 02/26/18 17:20, Tom Kent wrote:
'mt' is not recognized as an internal or external command, operable program or batch file. ...failed msvc.manifest.dll
I think, this problem has been discussed on the list not long ago - `mt` being not found on the system after some MSVC update:
Looks like MSVC needs to be reinstalled or installed on a separate machine. Will you be able to fix this?
Most likely the path to the SDK tools is missing in the setup: "C:\Program Files (x86)\Windows Kits\10\bin\x64" or "C:\Program Files (x86)\Windows Kits\10\bin\x86"
Ciao Dani
Hmm, those two paths exist but have very little in them. It looks like most of the SDK (including mt.exe) is in 10/bin/10.0.16299.0/[x86|x64]. Any idea if that is normal? Tom
Am 26.02.2018 um 21:55 schrieb Tom Kent via Boost:
On Mon, Feb 26, 2018 at 11:12 AM, Daniela Engert via Boost <
Most likely the path to the SDK tools is missing in the setup: "C:\Program Files (x86)\Windows Kits\10\bin\x64" or "C:\Program Files (x86)\Windows Kits\10\bin\x86"
Hmm, those two paths exist but have very little in them. It looks like most of the SDK (including mt.exe) is in 10/bin/10.0.16299.0/[x86|x64]. Any idea if that is normal?
I've been suffering from the same problem some time ago. My strictly straight-forward solution was to copy over the missing parts from the bin\x* directories and call it a day. Simple and effective ... Ciao Dani
On 02/26/18 23:55, Tom Kent via Boost wrote:
On Mon, Feb 26, 2018 at 11:12 AM, Daniela Engert via Boost < boost@lists.boost.org> wrote:
Am 26.02.2018 um 15:52 schrieb Andrey Semashev via Boost:
On 02/26/18 17:20, Tom Kent wrote:
'mt' is not recognized as an internal or external command, operable program or batch file. ...failed msvc.manifest.dll
I think, this problem has been discussed on the list not long ago - `mt` being not found on the system after some MSVC update:
Looks like MSVC needs to be reinstalled or installed on a separate machine. Will you be able to fix this?
Most likely the path to the SDK tools is missing in the setup: "C:\Program Files (x86)\Windows Kits\10\bin\x64" or "C:\Program Files (x86)\Windows Kits\10\bin\x86"
Ciao Dani
Hmm, those two paths exist but have very little in them. It looks like most of the SDK (including mt.exe) is in 10/bin/10.0.16299.0/[x86|x64]. Any idea if that is normal?
FWIW, on my system I have mt.exe and other tools in both 10\bin\x64 and 10\bin\10.0.16299.0\x64. But I probably haven't installed the problematic MSVC update.
On 02/28/18 19:42, Andrey Semashev wrote:
On 02/26/18 23:55, Tom Kent via Boost wrote:
On Mon, Feb 26, 2018 at 11:12 AM, Daniela Engert via Boost < boost@lists.boost.org> wrote:
Am 26.02.2018 um 15:52 schrieb Andrey Semashev via Boost:
On 02/26/18 17:20, Tom Kent wrote:
'mt' is not recognized as an internal or external command, operable program or batch file. ...failed msvc.manifest.dll
I think, this problem has been discussed on the list not long ago - `mt` being not found on the system after some MSVC update:
Looks like MSVC needs to be reinstalled or installed on a separate machine. Will you be able to fix this?
Most likely the path to the SDK tools is missing in the setup: "C:\Program Files (x86)\Windows Kits\10\bin\x64" or "C:\Program Files (x86)\Windows Kits\10\bin\x86"
Ciao Dani
Hmm, those two paths exist but have very little in them. It looks like most of the SDK (including mt.exe) is in 10/bin/10.0.16299.0/[x86|x64]. Any idea if that is normal?
FWIW, on my system I have mt.exe and other tools in both 10\bin\x64 and 10\bin\10.0.16299.0\x64. But I probably haven't installed the problematic MSVC update.
Any news about this issue?
On Wed, Mar 7, 2018 at 4:30 AM, Andrey Semashev via Boost < boost@lists.boost.org> wrote:
On 02/28/18 19:42, Andrey Semashev wrote:
On 02/26/18 23:55, Tom Kent via Boost wrote:
On Mon, Feb 26, 2018 at 11:12 AM, Daniela Engert via Boost < boost@lists.boost.org> wrote:
Am 26.02.2018 um 15:52 schrieb Andrey Semashev via Boost:
On 02/26/18 17:20, Tom Kent wrote:
'mt' is not recognized as an internal or external command, operable program or batch file. ...failed msvc.manifest.dll
I think, this problem has been discussed on the list not long ago - `mt`
being not found on the system after some MSVC update:
Looks like MSVC needs to be reinstalled or installed on a separate machine. Will you be able to fix this?
Most likely the path to the SDK tools is missing in the setup: "C:\Program Files (x86)\Windows Kits\10\bin\x64" or "C:\Program Files (x86)\Windows Kits\10\bin\x86"
Ciao Dani
Hmm, those two paths exist but have very little in them. It looks like most of the SDK (including mt.exe) is in 10/bin/10.0.16299.0/[x86|x64]. Any idea if that is normal?
FWIW, on my system I have mt.exe and other tools in both 10\bin\x64 and 10\bin\10.0.16299.0\x64. But I probably haven't installed the problematic MSVC update.
Any news about this issue?
Two days ago I gave up trying to solve the problem correctly, and just copied everything from the specific versioned SDK folders to those two (kids, don't try this at home!). It seems to have worked, the develop branch just cycled (previously, both develop and master had ssl connection problems with github when they tried to run in their normal slots over the last 24hrs) and looks a lot more green. Master is running now, and should be up in a few hours. Tom
On 03/08/18 01:20, Tom Kent via Boost wrote:
Two days ago I gave up trying to solve the problem correctly, and just copied everything from the specific versioned SDK folders to those two (kids, don't try this at home!). It seems to have worked, the develop branch just cycled (previously, both develop and master had ssl connection problems with github when they tried to run in their normal slots over the last 24hrs) and looks a lot more green. Master is running now, and should be up in a few hours.
Ah, I see the develop is green now. Thank you Tom.
participants (3)
-
Andrey Semashev -
Daniela Engert -
Tom Kent