From: Rick K. <rk...@nc...> - 2006-07-29 00:21:11
|
Berkin, This is most likely not a bug, but instead a problem due to either a non-functional installation of PAPI on your system or misconfiguration of PerfSuite. The test results show a pattern in which only PAPI-related tests are failing. You might want to check that PAPI is working on your system by running its test suite (check the PAPI installation notes for instructions). If all PAPI tests run well, then try reviewing the PerfSuite INSTALL file. It's important that PAPI is actually installed (not just built) and that the --with-papi=DIR option to configure points to the top-level of the PAPI installation directory (there should be an "include" and a "lib" directory there). Rick On Fri, 28 Jul 2006, bo...@ec... wrote: > Hi, > > I could not find a testsuite.log. > Here is what i get on the command line. > > Thanks > Berkin > > berkin@CALC3:~/perfsuite-0.6.2a5> make -s check > Making check in src > Making check in libperfsuite > Making check in . > Making check in tests > ## ------------------------------------------- ## > ## PerfSuite 0.6.2a5 test suite: Core Library. ## > ## ------------------------------------------- ## > 1: Hello, world! ok > 2: CPU identification ok > 3: CPU speed information ok > 4: CPU speed information (Fortran) ok > 5: CPU usage ok > 6: tokenizer ok > 7: error reporting ok > 8: error reporting (Fortran) ok > 9: argument processing ok > 10: proc filesystem ok > 11: memory usage reporting ok > 12: memory usage reporting (Fortran) ok > 13: dynamic memory usage reporting ok > 14: hash tables ok > 15: load map address inquiry ok > > ## ------------- ## > ## Test results. ## > ## ------------- ## > > All 15 tests were successful. > Making check in libpshwpc > Making check in . > Making check in arch-defaults > Making check in xml > Making check in css > Making check in dtds > Making check in xsl > Making check in tests > ## ----------------------------------------------------------- ## > ## PerfSuite 0.6.2a5 test suite: Hardware Performance Library. ## > ## ----------------------------------------------------------- ## > 1: base PAPI functionality FAILED (PAPI.at:47) > 2: PAPI compatibility FAILED (papicompat.at:47) > 3: PAPI to PerfSuite conversion (C/Fortran) FAILED (PAPI-PS.at:47) > 4: PAPI with POSIX threads (non-multiplexed) FAILED (PAPI-nompx.at:47) > 5: PAPI with POSIX threads (multiplexed) FAILED (PAPI-mpx.at:47) > 6: XML input document parsing (counting) ok > 7: XML input document parsing (profiling) ok > 8: inquiry (numevents) FAILED (inquiry.at:61) > 9: inquiry (numevents) error handling ok > 10: inquiry (numevents = 0) ok > 11: serial program (counting) FAILED (serial.at:73) > 12: serial program (profiling) FAILED (serial.at:85) > 13: serial program (profil) ok > 14: serial program (itimer) ok > 15: serial program (counting auto) FAILED (serial.at:121) > 16: serial program (profiling auto) FAILED (serial.at:133) > 17: serial program (profil auto) ok > 18: serial program (itimer auto) ok > 19: serial program (counting Fortran) FAILED (serial.at:167) > 20: serial program (profiling Fortran) FAILED (serial.at:179) > 21: serial program (profil Fortran) ok > 22: serial program (counting Fortran auto) FAILED (serial.at:202) > 23: serial program (profiling Fortran auto) FAILED (serial.at:214) > 24: serial program (profil Fortran auto) ok > 25: serial program (itimer Fortran auto) ok > 26: fork (counting) FAILED (fork.at:53) > 27: fork (profiling) FAILED (fork.at:63) > 28: POSIX threads program (counting) FAILED (threads.at:56) > 29: POSIX threads program (profiling) FAILED (threads.at:69) > > ## ------------- ## > ## Test results. ## > ## ------------- ## > > ERROR: All 29 tests were run, > 18 failed unexpectedly. > ## -------------------------- ## > ## testsuite.log was created. ## > ## -------------------------- ## > > Please send `testsuite.log' and all information you think might help: > > To: <per...@li...> > Subject: [PerfSuite 0.6.2a5] testsuite: 1 2 3 4 5 8 11 12 15 16 19 20 22 23 > 26 27 28 29 failed > > > You may investigate any problem if you feel able to do so, in which > case the test suite provides a good starting point. > > make[4]: *** [check-local] Error 1 > make[3]: *** [check-am] Error 2 > make[2]: *** [check-recursive] Error 1 > make[1]: *** [check-recursive] Error 1 > make: *** [check-recursive] Error 1 > > _________________________________________________________ > This message was sent through the NU ECE webmail gateway. > |