Trace number 203950

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
VALCSP 3.0? (MO) 8.20775 8.78421

General information on the benchmark

Namedomino/
domino-2000-2000.xml
MD5SUM3fad24b255c7d71c68ec020283e120af
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.108982
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables2000
Number of constraints2000
Maximum constraint arity2
Maximum domain size2000
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2000
Global constraints used (with number of constraints)

Solver Data (download as text)



Verifier Data (download as text)




ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer: 



Watcher Data (download as text)




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

command line: runsolver --timestamp -w ROOT/results/node38/watcher-203950-1168165067 -o ROOT/results/node38/solver-203950-1168165067 -C 1800 -M 900 /tmp/evaluation/203950-1168165067/VALCSP /tmp/evaluation/203950-1168165067/unknown.xml 

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: 0.84 1.59 1.70 5/70 12354
/proc/meminfo: memFree=1675632/2055920 swapFree=4192812/4192956
[pid=12353] ppid=12350 vsize=4268 CPUtime=0
/proc/12353/stat : 12353 (VALCSP) R 12350 12353 12241 0 -1 4194304 784 0 0 0 0 0 0 0 18 0 1 0 164906656 4370432 762 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 9041531 0 0 4096 0 0 0 0 17 1 0 0
/proc/12353/statm: 1067 769 62 8 0 739 0

[startup+0.102926 s]
/proc/loadavg: 0.84 1.59 1.70 5/70 12354
/proc/meminfo: memFree=1675632/2055920 swapFree=4192812/4192956
[pid=12353] ppid=12350 vsize=67948 CPUtime=0.09
/proc/12353/stat : 12353 (VALCSP) R 12350 12353 12241 0 -1 4194304 16726 0 0 0 2 7 0 0 18 0 1 0 164906656 69578752 16705 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 9041531 0 0 4096 0 0 0 0 17 1 0 0
/proc/12353/statm: 17020 16714 62 8 0 16692 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 67948

[startup+0.511002 s]
/proc/loadavg: 0.84 1.59 1.70 5/70 12354
/proc/meminfo: memFree=1675632/2055920 swapFree=4192812/4192956
[pid=12353] ppid=12350 vsize=158384 CPUtime=0.5
/proc/12353/stat : 12353 (VALCSP) R 12350 12353 12241 0 -1 4194304 39350 0 0 0 33 17 0 0 21 0 1 0 164906656 162185216 39328 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530223 0 0 4096 0 0 0 0 17 1 0 0
/proc/12353/statm: 39596 39328 64 8 0 39268 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 158384

[startup+1.33216 s]
/proc/loadavg: 0.84 1.59 1.70 4/84 12368
/proc/meminfo: memFree=1441088/2055920 swapFree=4192812/4192956
[pid=12353] ppid=12350 vsize=252380 CPUtime=1.32
/proc/12353/stat : 12353 (VALCSP) R 12350 12353 12241 0 -1 4194304 62823 0 0 0 107 25 0 0 25 0 1 0 164906656 258437120 62801 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530258 0 0 4096 0 0 0 0 17 1 0 0
/proc/12353/statm: 63095 62801 64 8 0 62767 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 252380

[startup+2.97849 s]
/proc/loadavg: 0.84 1.59 1.70 5/84 12368
/proc/meminfo: memFree=1095168/2055920 swapFree=4192812/4192956
[pid=12353] ppid=12350 vsize=393176 CPUtime=2.82
/proc/12353/stat : 12353 (VALCSP) R 12350 12353 12241 0 -1 4194304 98034 0 0 0 237 45 0 0 25 0 1 0 164906656 402612224 98012 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530300 0 0 4096 0 0 0 0 17 1 0 0
/proc/12353/statm: 98294 98012 64 8 0 97966 0
Current children cumulated CPU time (s) 2.82
Current children cumulated vsize (KiB) 393176

[startup+6.27312 s]
/proc/loadavg: 1.10 1.63 1.71 4/84 12368
/proc/meminfo: memFree=611136/2055920 swapFree=4192812/4192956
[pid=12353] ppid=12350 vsize=674900 CPUtime=5.72
/proc/12353/stat : 12353 (VALCSP) R 12350 12353 12241 0 -1 4194304 168455 0 0 0 488 84 0 0 25 0 1 0 164906656 691097600 168433 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530955 0 0 4096 0 0 0 0 17 0 0 0
/proc/12353/statm: 168725 168433 64 8 0 168397 0
Current children cumulated CPU time (s) 5.72
Current children cumulated vsize (KiB) 674900



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+8.63259 s]
/proc/loadavg: 1.09 1.62 1.70 2/68 12382
/proc/meminfo: memFree=752632/2055920 swapFree=4192812/4192956
[pid=12353] ppid=12350 vsize=925244 CPUtime=8.05
/proc/12353/stat : 12353 (VALCSP) R 12350 12353 12241 0 -1 4194304 231052 0 0 0 693 112 0 0 25 0 1 0 164906656 947449856 231030 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530227 0 0 4096 0 0 0 0 17 1 0 0
/proc/12353/statm: 231311 231030 64 8 0 230983 0
Current children cumulated CPU time (s) 8.05
Current children cumulated vsize (KiB) 925244

Sending SIGTERM to process tree (bottom up)
Sleeping 2 seconds

Child ended because it received signal 15 (SIGTERM)
Real time (s): 8.78421
CPU time (s): 8.20775
CPU user time (s): 6.93994
CPU system time (s): 1.26781
CPU usage (%): 93.4376
Max. virtual memory (cumulated for all children) (KiB): 925244

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

runsolver used 0.002999 s user time and 0.037994 s system time

The end



Launcher Data (download as text)




Begin job on node38 on Sun Jan  7 10:17:48 UTC 2007


IDJOB= 203950
IDBENCH= 3991
FILE ID= node38/203950-1168165067

PBS_JOBID= 3478582

Free space on /tmp= 66515 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-2000-2000.xml
COMMAND LINE= /tmp/evaluation/203950-1168165067/VALCSP /tmp/evaluation/203950-1168165067/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-203950-1168165067 -o ROOT/results/node38/solver-203950-1168165067 -C 1800 -M 900  /tmp/evaluation/203950-1168165067/VALCSP /tmp/evaluation/203950-1168165067/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  3fad24b255c7d71c68ec020283e120af

RANDOM SEED= 344174569

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.267
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.267
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:       1675976 kB
Buffers:         54884 kB
Cached:         233572 kB
SwapCached:          0 kB
Active:         143400 kB
Inactive:       165324 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1675976 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3368 kB
Writeback:           0 kB
Mapped:          30688 kB
Slab:            56688 kB
Committed_AS:  3469200 kB
PageTables:       1792 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= 66517 MiB



End job on node38 on Sun Jan  7 10:18:00 UTC 2007