Trace number 209824

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, and are wall clock time (not CPU 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
BPrologCSPSolver70a 2006-12-13UNSAT 13.5289 13.658

General information on the benchmark

Namefapp/fapp26-30/fapp26/
fapp26-2300-2.xml
MD5SUM5ab9fef4baf6ea85cbbe46e92584c6bf
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark6.70498
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables2300
Number of constraints24253
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension24253
Global constraints used (with number of constraints)

Solver Data (download as text)

13.63	
13.65	Time: 13311
13.65	
c 
c 
c 
c solution file
c 
c 

UNSAT
c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/209824-1168194423/unknown)

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node5/watcher-209824-1168194423 -o ROOT/results/node5/solver-209824-1168194423 -C 1800 -M 900 /tmp/evaluation/209824-1168194423/Complete/Ordinary/solver /tmp/evaluation/209824-1168194423/unknown 1800 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 2.07 2.14 2.08 5/88 16015
/proc/meminfo: memFree=1419352/2055920 swapFree=4192812/4192956
[pid=16014] ppid=16012 vsize=5352 CPUtime=0
/proc/16014/stat : 16014 (sh) R 16012 16014 15115 0 -1 4194304 267 0 0 0 0 0 0 0 20 0 1 0 148058334 5480448 234 18446744073709551615 4194304 4889804 548682069344 18446744073709551615 226913352774 0 0 4100 65536 0 0 0 17 1 0 0
/proc/16014/statm: 1338 234 196 169 0 49 0

[startup+0.103118 s]
/proc/loadavg: 2.07 2.14 2.08 5/88 16015
/proc/meminfo: memFree=1419352/2055920 swapFree=4192812/4192956
[pid=16014] ppid=16012 vsize=53824 CPUtime=0.08
/proc/16014/stat : 16014 (bprolog) R 16012 16014 15115 0 -1 4194304 2174 0 0 0 8 0 0 0 20 0 1 0 148058334 55115776 1890 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134560546 0 0 4096 2 0 0 0 17 1 0 0
/proc/16014/statm: 13456 1890 157 90 0 12994 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 53824

[startup+0.511162 s]
/proc/loadavg: 2.07 2.14 2.08 5/88 16015
/proc/meminfo: memFree=1419352/2055920 swapFree=4192812/4192956
[pid=16014] ppid=16012 vsize=67856 CPUtime=0.49
/proc/16014/stat : 16014 (bprolog) R 16012 16014 15115 0 -1 4194304 8838 0 0 0 45 4 0 0 23 0 1 0 148058334 69484544 8552 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134857829 0 0 4096 2 0 0 0 17 1 0 0
/proc/16014/statm: 16964 8552 157 90 0 16502 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 67856

[startup+1.33225 s]
/proc/loadavg: 2.06 2.14 2.08 3/88 16015
/proc/meminfo: memFree=1375768/2055920 swapFree=4192812/4192956
[pid=16014] ppid=16012 vsize=67856 CPUtime=1.31
/proc/16014/stat : 16014 (bprolog) R 16012 16014 15115 0 -1 4194304 11961 0 0 0 126 5 0 0 25 0 1 0 148058334 69484544 11675 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134550468 0 0 4096 2 0 0 0 17 1 0 0
/proc/16014/statm: 16964 11675 157 90 0 16502 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 67856

[startup+2.97745 s]
/proc/loadavg: 2.06 2.14 2.08 3/88 16015
/proc/meminfo: memFree=1372312/2055920 swapFree=4192812/4192956
[pid=16014] ppid=16012 vsize=67852 CPUtime=2.94
/proc/16014/stat : 16014 (bprolog) R 16012 16014 15115 0 -1 4194304 12212 0 0 0 289 5 0 0 25 0 1 0 148058334 69480448 11925 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134756017 0 0 4096 2 0 0 0 17 1 0 0
/proc/16014/statm: 16963 11925 176 90 0 16501 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 67852

[startup+6.25782 s]
/proc/loadavg: 2.06 2.14 2.08 3/88 16015
/proc/meminfo: memFree=1368600/2055920 swapFree=4192812/4192956
[pid=16014] ppid=16012 vsize=141456 CPUtime=6.19
/proc/16014/stat : 16014 (bprolog) R 16012 16014 15115 0 -1 4194304 27831 0 0 0 608 11 0 0 25 0 1 0 148058334 144850944 21399 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134866797 0 0 4096 2 0 0 0 17 1 0 0
/proc/16014/statm: 35364 21399 176 90 0 34902 0
Current children cumulated CPU time (s) 6.19
Current children cumulated vsize (KiB) 141456

[startup+12.7235 s]
/proc/loadavg: 2.05 2.14 2.07 3/89 16016
/proc/meminfo: memFree=1311504/2055920 swapFree=4192812/4192956
[pid=16014] ppid=16012 vsize=140452 CPUtime=12.59
/proc/16014/stat : 16014 (bprolog) R 16012 16014 15115 0 -1 4194304 46180 0 0 0 1241 18 0 0 25 0 2 0 148058334 143822848 27092 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134664015 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/16014/statm: 35113 27092 180 90 0 34651 0
[pid=16014/tid=16016] ppid=16012 vsize=140452 CPUtime=0
/proc/16014/task/16016/stat : 16016 (bprolog) S 16012 16014 15115 0 -1 4194368 2 0 0 0 0 0 0 0 25 0 2 0 148059460 143822848 27092 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 4294960144 0 0 4096 2 0 0 0 -1 1 0 0
Current children cumulated CPU time (s) 12.59
Current children cumulated vsize (KiB) 140452

Child status: 0
Real time (s): 13.658
CPU time (s): 13.5289
CPU user time (s): 13.323
CPU system time (s): 0.205968
CPU usage (%): 99.0552
Max. virtual memory (cumulated for all children) (KiB): 141456

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

runsolver used 0.024996 s user time and 0.042993 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Sun Jan  7 18:27:04 UTC 2007


IDJOB= 209824
IDBENCH= 4563
FILE ID= node5/209824-1168194423

PBS_JOBID= 3479003

Free space on /tmp= 66342 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp26-30/fapp26/fapp26-2300-2.xml
COMMAND LINE= /tmp/evaluation/209824-1168194423/Complete/Ordinary/solver /tmp/evaluation/209824-1168194423/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node5/convwatcher-209824-1168194423 -o ROOT/results/node5/conversion-209824-1168194423 -C 600 -M 900 /tmp/evaluation/209824-1168194423/Complete/Ordinary/conversion /tmp/evaluation/209824-1168194423/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-209824-1168194423 -o ROOT/results/node5/solver-209824-1168194423 -C 1800 -M 900  /tmp/evaluation/209824-1168194423/Complete/Ordinary/solver /tmp/evaluation/209824-1168194423/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  5ab9fef4baf6ea85cbbe46e92584c6bf

RANDOM SEED= 395041182

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.240
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.240
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:       1419832 kB
Buffers:         52076 kB
Cached:         379316 kB
SwapCached:          0 kB
Active:         233176 kB
Inactive:       340268 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1419832 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6832 kB
Writeback:           0 kB
Mapped:         162336 kB
Slab:            47220 kB
Committed_AS:  3895376 kB
PageTables:       2404 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= 66340 MiB



End job on node5 on Sun Jan  7 18:27:33 UTC 2007