Re: buildds: rv-osuosl-01 vs rv-mullvad-03
On Sat, Aug 6, 2022 at 9:25 AM Bo YU <tsu.yubo@gmail.com> wrote:
>
> Hi,
> On Fri, Aug 05, 2022 at 05:47:21PM +0200, Mathieu Malaterre wrote:
> >Dear riscv porters,
> >
> >Could someone please tell me what is the actual difference between
> >rv-osuosl-01 and rv-mullvad-03 buildds ?
>
> rv-osuosl-01/02 are unmatched board and rv-mullvad-03 is qemu IIRC.
> >
> >I did not see them listed at:
> >
> >* https://db.debian.org/machines.cgi
> >
> >It appears that at least one of my package does not build successfully
> >on rv-osuosl-01 (*). I could not reproduce the issue of 'Illegal
> >instruction' neither on my local schroot/qemu setup nor on real
> >hardware (lab.rvperf.org).
>
> I try to build on my local unmatched boards, it reported the same issue
> also:
>
> ```
> FILE=/<<PKGBUILDDIR>>/obj-riscv64-linux-gnu/find_test[1]_tests.cmake -D TEST_DISCOVERY_TIMEOUT=60 -D TEST_XML_OUTPUT_DIR= -P /usr/share/cmake-3.24/Modules/GoogleTestAddTests.cmake
> FAILED: tests/find_test find_test[1]_tests.cmake /<<PKGBUILDDIR>>/obj-riscv64-linux-gnu/find_test[1]_tests.cmake
> : && /usr/bin/c++ -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -DHWY_BROKEN_EMU128=1 -DHWY_COMPILE_ONLY_EMU128 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -fPIE -pie CMakeFiles/find_test.dir/hwy/contrib/algo/find_test.cc.o -o tests/find_test -Wl,-rpath,/<<PKGBUILDDIR>>/obj-riscv64-linux-gnu libhwy_test.so.1.0.0 libhwy_contrib.so.1.0.0 libhwy.so.1.0.0 -latomic /usr/lib/riscv64-linux-gnu/libgtest_main.a /usr/lib/riscv64-linux-gnu/libgtest.a -lpthread && cd /<<PKGBUILDDIR>>/obj-riscv64-linux-gnu && /usr/bin/cmake -D TEST_TARGET=find_test -D TEST_EXECUTABLE=/<<PKGBUILDDIR>>/obj-riscv64-linux-gnu/tests/find_test -D TEST_EXECUTOR= -D TEST_WORKING_DIR=/<<PKGBUILDDIR>>/obj-riscv64-linux-gnu -D TEST_EXTRA_ARGS= -D TEST_PROPERTIES= -D TEST_PREFIX= -D TEST_SUFFIX= -D TEST_FILTER= -D NO_PRETTY_TYPES=FALSE -D NO_PRETTY_VALUES=FALSE -D TEST_LIST=find_test_TESTS -D CTEST_FILE=/<<PKGBUILDDIR>>/obj-riscv64-linux-gnu/find_test[1]_tests.cmake -D TEST_DISCOVERY_TIMEOUT=60 -D TEST_XML_OUTPUT_DIR= -P /usr/share/cmake-3.24/Modules/GoogleTestAddTests.cmake
> CMake Error at /usr/share/cmake-3.24/Modules/GoogleTestAddTests.cmake:112 (message):
> Error running test executable.
>
> Path: '/<<PKGBUILDDIR>>/obj-riscv64-linux-gnu/tests/find_test'
> Result: Illegal instruction
> Output:
>
>
> Call Stack (most recent call first):
> /usr/share/cmake-3.24/Modules/GoogleTestAddTests.cmake:225 (gtest_discover_tests_impl)
>
>
> ninja: build stopped: subcommand failed.
> dh_auto_build: error: cd obj-riscv64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v returned exit code 1
> make: *** [debian/rules:10: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
> --------------------------------------------------------------------------------
> ...
> Build Architecture: riscv64
> Build Type: binary
> Build-Space: 33400
> Build-Time: 210
> Distribution: unstable
> Fail-Stage: build
> Host Architecture: riscv64
> Install-Time: 63
> Job: /home/vimer/build/08/12_highway/highway_1.0.0-5.dsc
> Machine Architecture: riscv64
> Package: highway
> Package-Time: 366
> Source-Version: 1.0.0-5
> Space: 33400
> Status: attempted
> Version: 1.0.0-5
> ```
>
> What OS run on your real hardware from lab.rvperf.org?
I am unable to reproduce the issue on the following:
$ uname -a
Linux unmatched 5.16.0-5-riscv64 #1 SMP Debian 5.16.14-1 (2022-03-15)
riscv64 GNU/Linux
$ cat /proc/cpuinfo
processor : 0
hart : 2
isa : rv64imafdc
mmu : sv39
uarch : sifive,bullet0
processor : 1
hart : 1
isa : rv64imafdc
mmu : sv39
uarch : sifive,bullet0
processor : 2
hart : 3
isa : rv64imafdc
mmu : sv39
uarch : sifive,bullet0
processor : 3
hart : 4
isa : rv64imafdc
mmu : sv39
uarch : sifive,bullet0
> But sorry I haven't had time to help you out with this in the
> last few days.
>
> --
> Regards,
> --
> Bo YU
>
Reply to: