[Scons-users] [Bug report] Tests fail on non-Intel platforms

[Mats Wichmann]

On 10/08/2018 08:27 AM, Bill Deegan wrote:
> Matěj,
> 
> Thanks for the report.
> That shouldn't be too hard to fix.
> Can you file a bug in our github tracker?
> 
> Thanks,
> Bill
> 
> On Mon, Oct 8, 2018 at 6:56 AM Matej Cepl <mcepl at suse.cz> wrote:
> 
>> Hi,
>>
>> when working on cleaning up packaging for openSUSE, I discovered
>> couple of texts which fail on Linux running on non-Intel
>> architectures (aarch64, armv7l, ppc64, ppc64le, s390x), while they pass
>> on the same version of Linux distribution (openSUSE Tumbleweed) on Intel
>> architecture:
>>
>> [ 1123s] Failed the following 14 tests:
>> [ 1123s]        test/MSVS/vs-11.0-scc-files.py
>> [ 1123s]        test/MSVS/vs-10.0-scc-legacy-files.py
>> [ 1123s]        test/MSVS/vs-8.0-scc-legacy-files.py
>> [ 1123s]        test/MSVS/vs-11.0-scc-legacy-files.py
>> [ 1123s]        test/MSVS/vs-9.0-scc-legacy-files.py
>> [ 1123s]        test/MSVS/vs-7.1-scc-files.py
>> [ 1123s]        test/MSVS/vs-9.0-scc-files.py
>> [ 1123s]        test/MSVS/vs-8.0-scc-files.py
>> [ 1123s]        test/MSVS/vs-7.1-scc-legacy-files.py
>> [ 1123s]        test/MSVS/vs-7.0-scc-files.py
>> [ 1123s]        test/MSVS/vs-7.0-scc-legacy-files.py
>> [ 1123s]        test/MSVS/vs-14.0-scc-files.py
>> [ 1123s]        test/MSVS/vs-14.0-scc-legacy-files.py
>> [ 1123s]        test/MSVS/vs-10.0-scc-files.py

all tests which _can_ run on non-Windows platforms because they don't
use the MS tools, just manipulate the project files which are xml, but
which don't really make any sense. MSCommon/vc.py has an architecture
translation table which maps things Windows is supported on - I know
because I dug there after my project complained ARM triggered a problem,
and that *is* supported on recent Windows.  Seems odd to add
architectures to a windows-specific table that don't apply to windows so
probably a fix will involve properly catching the exception instead?

after taking a quick look: this is intentionally raising an exception
inside the try block, guess the code needs to do something better with
the answer.