Discussion:
[Scons-users] [Bug report] Tests fail on non-Intel platforms
Matej Cepl
2018-10-08 10:56:24 UTC
Permalink
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

Full build log has been attached as well.

Best,

Matěj Cepl
--
https://matej.ceplovi.cz/blog/, Jabber: ***@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8

A man once asked Mozart how to write a symphony. Mozart told him
to study at the conservatory for six or eight years, then
apprentice with a composer for four or five more years, then
begin writing a few sonatas, pieces for string quartets, piano
concertos, etc. and in another four or five years he would be
ready to try a full symphony. The man said, "But Mozart, didn't
you write a symphony at age eight?" Mozart replied, "Yes, but
I didn't have to ask how."
-- ripped from another sig
Bill Deegan
2018-10-08 14:27:44 UTC
Permalink
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
Post by Matej Cepl
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
[ 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
Full build log has been attached as well.
Best,
Matěj Cepl
--
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
A man once asked Mozart how to write a symphony. Mozart told him
to study at the conservatory for six or eight years, then
apprentice with a composer for four or five more years, then
begin writing a few sonatas, pieces for string quartets, piano
concertos, etc. and in another four or five years he would be
ready to try a full symphony. The man said, "But Mozart, didn't
you write a symphony at age eight?" Mozart replied, "Yes, but
I didn't have to ask how."
-- ripped from another sig
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users
Mats Wichmann
2018-10-08 14:55:46 UTC
Permalink
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
Post by Matej Cepl
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
[ 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.
Bill Deegan
2018-10-08 15:22:45 UTC
Permalink
Mats,

Indeed.
Perhaps just skip the test if on arch not supported?

-Bill
Post by Mats Wichmann
Post by Bill Deegan
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
Post by Matej Cepl
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
[ 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.
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users
Loading...