10-06-2012
I expected the name of the library that I can use -
from the people who worked with hpl. If you do not know it, do not write.
8 More Discussions You Might Find Interesting
1. Linux Benchmarks
Should we conver to Linpack for Linux Benchmarks?
http://www.netlib.org/benchmark/hpl/
What do you think? (0 Replies)
Discussion started by: Neo
0 Replies
2. High Performance Computing
Our directory of HPC related links is growing:
Virtualization, Grid and Cloud Computing - Links
Please contribute! (0 Replies)
Discussion started by: Neo
0 Replies
3. High Performance Computing
Hi guys,
I am having some issues tuning the HPL.dat file for the Linpack benchmark test across 2 nodes. I am very new to this with minimal Linux experience, however i am trying my luck.
The specs for the two nodes are:
3GHZ QX6850 CORE 2 EXTREME (QUAD CORE)
4GB RAM
I have been typing these... (1 Reply)
Discussion started by: mercthunder
1 Replies
4. Shell Programming and Scripting
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Discussion started by: Max89
1 Replies
5. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
6. High Performance Computing
In my company, it's fallen on me to serve as the admin of our new HPC cluster, a task that's very new to me. It's very important to me to lay a solid foundation and avoid any unnecessary pitfalls. So, can anyone recommend a succinct guide or list of do's-and-don'ts for adiminstering an HPC cluster?... (0 Replies)
Discussion started by: DBryan
0 Replies
7. High Performance Computing
I'm trying to compile Linpack on a Ubuntu cluster. I'm running MPI. I've modified the following values to fit my system TOPdir MPdir LAlib CC LINKER.
When compiling I get the following error: (the error is at the end, the other errors in between are because I've ran the script several times so... (0 Replies)
Discussion started by: JPJPJPJP
0 Replies
8. Homework & Coursework Questions
My high school started a tech lab where students like myself can take apart computers, build circuit boards, learn to program and lots more.
I got the job of building a cluster with 4 old work stations we have. This is just a trial if it works well we can get more work stations.
We have one... (3 Replies)
Discussion started by: PC-2011
3 Replies
LEARN ABOUT DEBIAN
go-test
GO-TEST(1) General Commands Manual GO-TEST(1)
NAME
go - tool for managing Go source code
SYNOPSIS
go test [-c] [-i] [ build flags ] [ packages ] [ flags for test binary ]
DESCRIPTION
"Go test" automates testing the packages named by the import paths. It prints a summary of the test results in the format:
ok archive/tar 0.011s
FAIL archive/zip 0.022s
ok compress/gzip 0.033s
...
followed by detailed output for each failed package.
"Go test" recompiles each package along with any files with names matching the file pattern "*_test.go". These additional files can con-
tain test functions, benchmark functions, and example functions. See go-testfunc(7) for more.
By default, go test needs no arguments. It compiles and tests the package with source in the current directory, including tests, and runs
the tests.
The package is built in a temporary directory so it does not interfere with the non-test installation.
OPTIONS
In addition to the build flags, the flags handled by 'go test' itself are:
-c Compile the test binary to pkg.test but do not run it.
-i Install packages that are dependencies of the test. Do not run the test.
The test binary also accepts flags that control execution of the test; these flags are also accessible by 'go test'. See go-testflag(7)
for details.
For more about build flags, see go-build(1).
For more about specifying packages, see go-packages(7).
SEE ALSO
go-build(1), go-vet(1).
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-TEST(1)