Trace number 268373

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.1? (exit code) 2.35664 2.38482

General information on the benchmark

Namedomino/
domino-5000-5000.xml
MD5SUM18de54b00f9f9844eda77aa609528237
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.243961
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables5000
Number of constraints5000
Maximum constraint arity2
Maximum domain size5000
Number of constraints which are defined in extension0
Number of constraints which are defined in intension5000
Global constraints used (with number of constraints)

Solver Data (download as text)

2.22	Out of memory

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/node1/watcher-268373-1168978740 -o ROOT/results/node1/solver-268373-1168978740 -C 1800 -M 900 /tmp/evaluation/268373-1168978740/VALCSP /tmp/evaluation/268373-1168978740/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: 1.90 1.69 1.02 5/86 31889
/proc/meminfo: memFree=1614616/2055920 swapFree=4165612/4192956
[pid=31888] ppid=31886 vsize=3268 CPUtime=0
/proc/31888/stat : 31888 (VALCSP) R 31886 31888 31678 0 -1 4194304 453 0 0 0 0 0 0 0 20 0 1 0 246269865 3346432 431 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134533489 0 0 4096 0 0 0 0 17 1 0 0
/proc/31888/statm: 817 431 65 8 0 489 0

[startup+0.105838 s]
/proc/loadavg: 1.90 1.69 1.02 5/86 31889
/proc/meminfo: memFree=1614616/2055920 swapFree=4165612/4192956
[pid=31888] ppid=31886 vsize=81260 CPUtime=0.09
/proc/31888/stat : 31888 (VALCSP) R 31886 31888 31678 0 -1 4194304 18025 0 0 0 2 7 0 0 20 0 1 0 246269865 83210240 18003 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134533496 0 0 4096 0 0 0 0 17 1 0 0
/proc/31888/statm: 20315 18003 65 8 0 19987 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 81260

[startup+0.513895 s]
/proc/loadavg: 1.90 1.69 1.02 5/86 31889
/proc/meminfo: memFree=1614616/2055920 swapFree=4165612/4192956
[pid=31888] ppid=31886 vsize=387092 CPUtime=0.49
/proc/31888/stat : 31888 (VALCSP) R 31886 31888 31678 0 -1 4194304 89275 0 0 0 14 35 0 0 24 0 1 0 246269865 396382208 89253 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134532931 0 0 4096 0 0 0 0 17 1 0 0
/proc/31888/statm: 96773 89253 65 8 0 96445 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 387092

[startup+1.33498 s]
/proc/loadavg: 1.91 1.70 1.03 3/86 31889
/proc/meminfo: memFree=860824/2055920 swapFree=4165612/4192956
[pid=31888] ppid=31886 vsize=882256 CPUtime=1.3
/proc/31888/stat : 31888 (VALCSP) R 31886 31888 31678 0 -1 4194304 213059 0 0 0 47 83 0 0 25 0 1 0 246269865 903430144 213037 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528685 0 0 4096 0 0 0 0 17 1 0 0
/proc/31888/statm: 220564 213037 65 8 0 220236 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 882256

Child status: 1
Real time (s): 2.38482
CPU time (s): 2.35664
CPU user time (s): 1.27781
CPU system time (s): 1.07883
CPU usage (%): 98.8182
Max. virtual memory (cumulated for all children) (KiB): 921372

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

runsolver used 0.004999 s user time and 0.014997 s system time

The end

Launcher Data (download as text)

Begin job on node1 on Tue Jan 16 20:19:00 UTC 2007


IDJOB= 268373
IDBENCH= 3997
IDSOLVER= 90
FILE ID= node1/268373-1168978740

PBS_JOBID= 3565964

Free space on /tmp= 66563 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-5000-5000.xml
COMMAND LINE= /tmp/evaluation/268373-1168978740/VALCSP /tmp/evaluation/268373-1168978740/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node1/watcher-268373-1168978740 -o ROOT/results/node1/solver-268373-1168978740 -C 1800 -M 900  /tmp/evaluation/268373-1168978740/VALCSP /tmp/evaluation/268373-1168978740/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  18de54b00f9f9844eda77aa609528237

RANDOM SEED= 573612651

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.234
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.234
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:       1615032 kB
Buffers:         48392 kB
Cached:         273696 kB
SwapCached:       3768 kB
Active:         183792 kB
Inactive:       183428 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1615032 kB
SwapTotal:     4192956 kB
SwapFree:      4165612 kB
Dirty:            1012 kB
Writeback:           0 kB
Mapped:          55804 kB
Slab:            58500 kB
Committed_AS:  7165672 kB
PageTables:       2300 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= 66563 MiB



End job on node1 on Tue Jan 16 20:19:04 UTC 2007