Trace number 1777747

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock time.

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
gNovelty+-T 2009-03-22 (4 threads)SAT 0.17 0.1298

General information on the benchmark

NameRANDOM/MEDIUM/5SAT/SATISFIABLE/90/
unif-k5-r21.3-v90-c1917-S1159550149-077.cnf
MD5SUM7e03cd843234dc424776ba0f93603598
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.17
Satisfiable
(Un)Satisfiability was proved
Number of variables90
Number of clauses1917
Sum of the clauses size9585
Maximum clause length5
Minimum clause length5
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 51917
Number of clauses of size over 50

Solver Data 

0.00/0.08	c +------------------------------+
0.00/0.08	c | gNovelty+, version 1.0       |
0.00/0.08	c +------------------------------+
0.00/0.08	c gnovelty+ -h for help
0.00/0.08	c 
0.12/0.12	s SATISFIABLE
0.12/0.12	v -1 -2 -3 -4 -5 -6 -7 -8 9 10 -11 12 13 -14 -15 16 17 18 19 -20 21 22 23 24 25 -26 -27 28 29 -30 31 32 33 34 -35 -36 -37 -38 39 40 -41 42 -43 44 -45 -46 -47 48 -49 -50 51 -52 -53 -54 -55 56 -57 -58 -59 60 61 -62 -63 64 -65 -66 -67 -68 69 -70 71 -72 -73 74 -75 -76 77 78 -79 80 -81 -82 -83 84 85 -86 87 88 -89 90 0
0.12/0.12	c Done in 0.070000 seconds

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:503) (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w /tmp/evaluation-result-1777747-1243456553/watcher-1777747-1243456553 -o /tmp/evaluation-result-1777747-1243456553/solver-1777747-1243456553 -C 5000 -W 1000 -M 2047 HOME/gnovelty+ HOME/instance-1777747-1243456553.cnf 555049521 4 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 5000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 5030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 1000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 2096128 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 2147328 KiB
Current StackSize limit: 8192 KiB


[startup+0 s]
/proc/loadavg: 2.61 3.70 3.93 2/115 9927
/proc/meminfo: memFree=3161708/3368532 swapFree=1941392/1959888
[pid=9927] ppid=9925 vsize=509232 CPUtime=0.01
/proc/9927/stat : 9927 (gnovelty+) R 9925 9927 24991 0 -1 4202496 1596 0 0 0 1 0 0 0 18 0 1 0 1110335147 521453568 1552 4294967295 134512640 135680988 3219657168 3219656432 134537167 0 0 0 0 0 0 0 17 1 0 0 0
/proc/9927/statm: 127308 1560 99 286 0 127020 0

[startup+0.100623 s]
/proc/loadavg: 2.61 3.70 3.93 2/115 9927
/proc/meminfo: memFree=3161708/3368532 swapFree=1941392/1959888
[pid=9927] ppid=9925 vsize=545804 CPUtime=0.12
/proc/9927/stat : 9927 (gnovelty+) R 9925 9927 24991 0 -1 4202496 19797 0 0 0 7 5 0 0 20 0 4 0 1110335147 558903296 19752 4294967295 134512640 135680988 3219657168 3219656412 134957681 0 0 0 0 4294967295 0 0 17 2 0 0 0
/proc/9927/statm: 136451 19752 103 286 0 136163 0
Current children cumulated CPU time (s) 0.12
Current children cumulated vsize (KiB) 545804

Solver just ended. Dumping a history of the last processes samples

[startup+0.100623 s]
/proc/loadavg: 2.61 3.70 3.93 2/115 9927
/proc/meminfo: memFree=3161708/3368532 swapFree=1941392/1959888
[pid=9927] ppid=9925 vsize=545804 CPUtime=0.12
/proc/9927/stat : 9927 (gnovelty+) R 9925 9927 24991 0 -1 4202496 19797 0 0 0 7 5 0 0 20 0 4 0 1110335147 558903296 19752 4294967295 134512640 135680988 3219657168 3219656412 134957681 0 0 0 0 4294967295 0 0 17 2 0 0 0
/proc/9927/statm: 136451 19752 103 286 0 136163 0
Current children cumulated CPU time (s) 0.12
Current children cumulated vsize (KiB) 545804

Child status: 10
Real time (s): 0.1298
CPU time (s): 0.17
CPU user time (s): 0.12
CPU system time (s): 0.05
CPU usage (%): 130.971
Max. virtual memory (cumulated for all children) (KiB): 545804

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.12
system time used= 0.05
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 19812
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 256
involuntary context switches= 52

runsolver used 0.01 second user time and 0 second system time

The end

Launcher Data 

Begin job on  at 2009-05-27 22:35:53
IDJOB=1777747
IDBENCH=70431
IDSOLVER=617
FILE ID=/1777747-1243456553
PBS_JOBID=
Free space on /tmp= 15730 MiB

SOLVER NAME= gNovelty+-T 2009-03-22 (4 threads)
BENCH NAME= SAT09/RANDOM/MEDIUM/5SAT/SATISFIABLE/90/unif-k5-r21.3-v90-c1917-S1159550149-077.cnf
COMMAND LINE= HOME/gnovelty+ BENCHNAME RANDOMSEED MAXNBTHREAD
RUNSOLVER COMMAND LINE= runsolver --timestamp  -w /tmp/evaluation-result-1777747-1243456553/watcher-1777747-1243456553 -o /tmp/evaluation-result-1777747-1243456553/solver-1777747-1243456553 -C 5000 -W 1000 -M 2047  HOME/gnovelty+ HOME/instance-1777747-1243456553.cnf 555049521 4

TIME LIMIT= 5000 seconds
MEMORY LIMIT= 2047 MiB
MAX NB THREAD= 4

MD5SUM BENCH= 7e03cd843234dc424776ba0f93603598
RANDOM SEED= 555049521

Linux (none) 2.6.21.5 #6 SMP Wed Jul 4 17:16:38 CEST 2007 i686 GNU/Linux

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.143
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3992.42
clflush size	: 64

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.143
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.11
clflush size	: 64

processor	: 2
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.143
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.17
clflush size	: 64

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.143
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.15
clflush size	: 64


/proc/meminfo:
MemTotal:      3368532 kB
MemFree:       3161708 kB
Buffers:         13088 kB
Cached:         120904 kB
SwapCached:       4320 kB
Active:         105280 kB
Inactive:        39688 kB
HighTotal:     2489216 kB
HighFree:      2355440 kB
LowTotal:       879316 kB
LowFree:        806268 kB
SwapTotal:     1959888 kB
SwapFree:      1941392 kB
Dirty:            1556 kB
Writeback:           0 kB
AnonPages:        9560 kB
Mapped:           4296 kB
Slab:            51696 kB
SReclaimable:    43068 kB
SUnreclaim:       8628 kB
PageTables:        896 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   3644152 kB
Committed_AS:   127260 kB
VmallocTotal:   114680 kB
VmallocUsed:      1444 kB
VmallocChunk:   113072 kB

Free space on /tmp at the end= 15730 MiB
End job on  at 2009-05-27 22:35:54