Trace number 1732874

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+ 2009-03-22SAT 0.704892 0.70448

General information on the benchmark

NameCRAFTED/ramseycube/
Q3inK10.cnf
MD5SUM0d32a4893e12fa46a8943c5daeb46b88
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.12498
Satisfiable
(Un)Satisfiability was proved
Number of variables45
Number of clauses75600
Sum of the clauses size907200
Maximum clause length12
Minimum clause length12
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 50
Number of clauses of size over 575600

Solver Data 

0.59/0.67	c +------------------------------+
0.59/0.67	c | gNovelty+, version 1.2       |
0.59/0.67	c +------------------------------+
0.59/0.67	c gnovelty+ -h for help
0.59/0.67	c 
0.59/0.67	finish initINstance()
0.59/0.67	c Problem instance: numAtoms = 45, numClauses = 75600, numLiterals = 907200
0.59/0.67	c General parameters: seed = 1487581448, timeout = 10 secs, targetCost = 0, print solution: no
0.59/0.67	c gNovelty+ parameters: walkprob = 0.01, smoothprob = 1.00, noise = adaptive
0.59/0.67	c tries = 1
0.59/0.67	c 
0.59/0.69	     0        2         0         2         0      0.01
0.59/0.69	s SATISFIABLE
0.59/0.69	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 0
0.59/0.69	c Done in 0.010000 seconds

Verifier Data 

OK

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1732874-1240783902/watcher-1732874-1240783902 -o /tmp/evaluation-result-1732874-1240783902/solver-1732874-1240783902 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/gnovelty+ HOME/instance-1732874-1240783902.cnf 1487581448 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 23777
/proc/meminfo: memFree=1556656/2055920 swapFree=4181396/4192956
[pid=23777] ppid=23775 vsize=959252 CPUtime=0
/proc/23777/stat : 23777 (gnovelty+) R 23775 23777 23410 0 -1 4194304 752 0 0 0 0 0 0 0 18 0 1 0 106423274 982274048 736 1992294400 134512640 135098890 4294956208 18446744073709551615 134517913 0 0 4096 0 0 0 0 17 1 0 0
/proc/23777/statm: 239813 742 46 143 0 239668 0

[startup+0.092376 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 23777
/proc/meminfo: memFree=1556656/2055920 swapFree=4181396/4192956
[pid=23777] ppid=23775 vsize=960036 CPUtime=0.08
/proc/23777/stat : 23777 (gnovelty+) R 23775 23777 23410 0 -1 4194304 9927 0 0 0 4 4 0 0 18 0 1 0 106423274 983076864 9911 1992294400 134512640 135098890 4294956208 18446744073709551615 134603886 0 0 4096 0 0 0 0 17 1 0 0
/proc/23777/statm: 240009 9911 48 143 0 239864 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 960036

[startup+0.101376 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 23777
/proc/meminfo: memFree=1556656/2055920 swapFree=4181396/4192956
[pid=23777] ppid=23775 vsize=960036 CPUtime=0.09
/proc/23777/stat : 23777 (gnovelty+) R 23775 23777 23410 0 -1 4194304 9949 0 0 0 5 4 0 0 18 0 1 0 106423274 983076864 9933 1992294400 134512640 135098890 4294956208 18446744073709551615 134598775 0 0 4096 0 0 0 0 17 1 0 0
/proc/23777/statm: 240009 9933 48 143 0 239864 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 960036

[startup+0.301409 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 23777
/proc/meminfo: memFree=1556656/2055920 swapFree=4181396/4192956
[pid=23777] ppid=23775 vsize=961604 CPUtime=0.29
/proc/23777/stat : 23777 (gnovelty+) R 23775 23777 23410 0 -1 4194304 10443 0 0 0 25 4 0 0 19 0 1 0 106423274 984682496 10427 1992294400 134512640 135098890 4294956208 18446744073709551615 134560772 0 0 4096 0 0 0 0 17 1 0 0
/proc/23777/statm: 240401 10427 48 143 0 240256 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 961604

[startup+0.701479 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 23777
/proc/meminfo: memFree=1556656/2055920 swapFree=4181396/4192956
[pid=23777] ppid=23775 vsize=0 CPUtime=0.69
/proc/23777/stat : 23777 (gnovelty+) R 23775 23777 23410 0 -1 4194308 21788 0 0 0 59 10 0 0 22 0 1 0 106423274 0 0 1992294400 0 0 0 0 0 0 0 4096 0 0 0 0 17 1 0 0
/proc/23777/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 0

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

Child status: 10
Real time (s): 0.70448
CPU time (s): 0.704892
CPU user time (s): 0.597909
CPU system time (s): 0.106983
CPU usage (%): 100.058
Max. virtual memory (cumulated for all children) (KiB): 967088

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.597909
system time used= 0.106983
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 21788
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= 2
involuntary context switches= 2

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node25 at 2009-04-27 00:11:43
IDJOB=1732874
IDBENCH=71129
IDSOLVER=536
FILE ID=node25/1732874-1240783902
PBS_JOBID= 9187232
Free space on /tmp= 66384 MiB

SOLVER NAME= gnovelty+ 2009-03-22
BENCH NAME= SAT09/CRAFTED/ramseycube/Q3inK10.cnf
COMMAND LINE= HOME/gnovelty+ BENCHNAME RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1732874-1240783902/watcher-1732874-1240783902 -o /tmp/evaluation-result-1732874-1240783902/solver-1732874-1240783902 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/gnovelty+ HOME/instance-1732874-1240783902.cnf 1487581448

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 0d32a4893e12fa46a8943c5daeb46b88
RANDOM SEED=1487581448

node25.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.259
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
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 syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.259
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
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 syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1557136 kB
Buffers:         54852 kB
Cached:         386484 kB
SwapCached:       5424 kB
Active:         149812 kB
Inactive:       299400 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1557136 kB
SwapTotal:     4192956 kB
SwapFree:      4181396 kB
Dirty:            3848 kB
Writeback:           0 kB
Mapped:          13480 kB
Slab:            35528 kB
Committed_AS:   411324 kB
PageTables:       1460 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66384 MiB
End job on node25 at 2009-04-27 00:11:43