Trace number 1577835

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
iPAWS 2009-03-22? 0.000999 0.00532592

General information on the benchmark

NameAPPLICATIONS/bioinfo/
q_query_3_L100_coli.sat.cnf
MD5SUM370a08d01be1cc652e9a09ab1aafdced
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark183.559
Satisfiable
(Un)Satisfiability was proved
Number of variables315617
Number of clauses1522583
Sum of the clauses size4407119
Maximum clause length11
Minimum clause length1
Number of clauses of size 132077
Number of clauses of size 2403677
Number of clauses of size 3835608
Number of clauses of size 4197035
Number of clauses of size 553887
Number of clauses of size over 5299

Solver Data 

0.00/0.00	s UNKNOWN
0.00/0.00	c Too many atoms

Verifier Data 

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer: UNKNOWN

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1577835-1241005066/watcher-1577835-1241005066 -o /tmp/evaluation-result-1577835-1241005066/solver-1577835-1241005066 -C 1200 -W 1800 -M 1800 HOME/iPAWS HOME/instance-1577835-1241005066.cnf 585070529 

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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.99 0.98 0.91 3/64 24814
/proc/meminfo: memFree=1385912/2055920 swapFree=4174088/4192956
[pid=24814] ppid=24812 vsize=0 CPUtime=0
/proc/24814/stat : 24814 (iPAWS) Z 24812 24814 24453 0 -1 4194316 84 0 0 0 0 0 0 0 18 0 1 0 128534850 0 0 1992294400 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 0 0 0
/proc/24814/statm: 0 0 0 0 0 0 0

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

Child status: 255
Real time (s): 0.00532592
CPU time (s): 0.000999
CPU user time (s): 0.000999
CPU system time (s): 0
CPU usage (%): 18.7573
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.000999
system time used= 0
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 84
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= 0

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node50 at 2009-04-29 13:37:48
IDJOB=1577835
IDBENCH=70967
IDSOLVER=516
FILE ID=node50/1577835-1241005066
PBS_JOBID= 9204820
Free space on /tmp= 66492 MiB

SOLVER NAME= iPAWS 2009-03-22
BENCH NAME= SAT09/APPLICATIONS/bioinfo/q_query_3_L100_coli.sat.cnf
COMMAND LINE= HOME/iPAWS BENCHNAME RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1577835-1241005066/watcher-1577835-1241005066 -o /tmp/evaluation-result-1577835-1241005066/solver-1577835-1241005066 -C 1200 -W 1800 -M 1800  HOME/iPAWS HOME/instance-1577835-1241005066.cnf 585070529

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

MD5SUM BENCH= 370a08d01be1cc652e9a09ab1aafdced
RANDOM SEED=585070529

node50.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.216
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.216
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:       1386328 kB
Buffers:         40332 kB
Cached:         544800 kB
SwapCached:      13132 kB
Active:          53764 kB
Inactive:       546200 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1386328 kB
SwapTotal:     4192956 kB
SwapFree:      4174088 kB
Dirty:           30748 kB
Writeback:           0 kB
Mapped:          13516 kB
Slab:            55520 kB
Committed_AS:   447168 kB
PageTables:       1464 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= 66488 MiB
End job on node50 at 2009-04-29 13:37:48