We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After run glibc.py in Rhel8.2 with Avocado(version: 81.0), it shows " ERROR: Command 'make' failed.\nstdout: b'make -r PARALLELMFLAGS="" ".
《SOL log》
《joblog》 【INIT 1】 L0416 DEBUG| [stdout] make[2]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/1-glibc.py_Glibc.test_run-build_directory-run_type-upstream-be0f/glibc-master/signal' L0416 DEBUG| [stderr] make[2]: *** [../o-iterator.mk:9: /tmp/signal/sigorset.o] Error 1 L0686 INFO | Command 'make' finished with 2 after 7.55452561378479s L0416 DEBUG| [stderr] make[1]: *** [Makefile:470: signal/subdir_lib] Error 2 L0416 DEBUG| [stdout] make[1]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/1-glibc.py_Glibc.test_run-build_directory-run_type-upstream-be0f/glibc-master' L0416 DEBUG| [stderr] make: *** [Makefile:9: all] Error 2
【INIT 2】 L0416 DEBUG| [stdout] make[2]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/2-glibc.py_Glibc.test_run-build_directory-run_type-distro-68fc/glibc-distro/glibc-2.28/csu' L0416 DEBUG| [stderr] make[1]: *** [Makefile:258: csu/subdir_lib] Error 2 L0416 DEBUG| [stdout] make[1]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/2-glibc.py_Glibc.test_run-build_directory-run_type-distro-68fc/glibc-distro/glibc-2.28' L0416 DEBUG| [stderr] make: *** [Makefile:9: all] Error 2 L0686 INFO | Command 'make' finished with 2 after 2.6921072006225586s
《Test log》: job-log & Manual-Test-log Test log.zip
《Configuration》
[Rhel8.2 Kernel] 4.18.0-193.19.1.el8_2.ppc64le
[FW config] BMC: op940.00.mih-5-0-g86f9791c2 PNOR: OP9-v2.4-4.37-prod
[HW config] CPU DD2.3 20core *2 Micron (M393A8K40B22-CWD6Y) 64G *16 Samsung PM985 960GB *1 PSU ACBEL 2000w *2 Broadcom (LSI) MegaRAID 9361-8i SAS3 Controller w/ 8 internal ports *1 @ slot10
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After run glibc.py in Rhel8.2 with Avocado(version: 81.0), it shows " ERROR: Command 'make' failed.\nstdout: b'make -r PARALLELMFLAGS="" ".
《SOL log》
《joblog》
【INIT 1】
L0416 DEBUG| [stdout] make[2]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/1-glibc.py_Glibc.test_run-build_directory-run_type-upstream-be0f/glibc-master/signal'
L0416 DEBUG| [stderr] make[2]: *** [../o-iterator.mk:9: /tmp/signal/sigorset.o] Error 1
L0686 INFO | Command 'make' finished with 2 after 7.55452561378479s
L0416 DEBUG| [stderr] make[1]: *** [Makefile:470: signal/subdir_lib] Error 2
L0416 DEBUG| [stdout] make[1]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/1-glibc.py_Glibc.test_run-build_directory-run_type-upstream-be0f/glibc-master'
L0416 DEBUG| [stderr] make: *** [Makefile:9: all] Error 2
【INIT 2】
L0416 DEBUG| [stdout] make[2]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/2-glibc.py_Glibc.test_run-build_directory-run_type-distro-68fc/glibc-distro/glibc-2.28/csu'
L0416 DEBUG| [stderr] make[1]: *** [Makefile:258: csu/subdir_lib] Error 2
L0416 DEBUG| [stdout] make[1]: Leaving directory '/var/tmp/avocado_tsro15c8/avocado_job_ro6o5zqi/2-glibc.py_Glibc.test_run-build_directory-run_type-distro-68fc/glibc-distro/glibc-2.28'
L0416 DEBUG| [stderr] make: *** [Makefile:9: all] Error 2
L0686 INFO | Command 'make' finished with 2 after 2.6921072006225586s
《Test log》: job-log & Manual-Test-log
Test log.zip
《Configuration》
[Rhel8.2 Kernel]
4.18.0-193.19.1.el8_2.ppc64le
[FW config]
BMC: op940.00.mih-5-0-g86f9791c2
PNOR: OP9-v2.4-4.37-prod
[HW config]
CPU DD2.3 20core *2
Micron (M393A8K40B22-CWD6Y) 64G *16
Samsung PM985 960GB *1
PSU ACBEL 2000w *2
Broadcom (LSI) MegaRAID 9361-8i SAS3 Controller w/ 8 internal ports *1 @ slot10
The text was updated successfully, but these errors were encountered: