Trace number 204050

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
buggy_2_5 2007-01-08? (MO) 0.078987 2.90078

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)



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/node17/watcher-204050-1168701788 -o ROOT/results/node17/solver-204050-1168701788 -C 1800 -M 900 /tmp/evaluation/204050-1168701788/solver /tmp/evaluation/204050-1168701788/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: 1.36 1.52 0.94 5/87 31455
/proc/meminfo: memFree=1563096/2055920 swapFree=4192812/4192956
[pid=31454] ppid=31452 vsize=18540 CPUtime=0
/proc/31454/stat : 31454 (runsolver) R 31452 31454 29355 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 218573864 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 245482712359 0 0 4096 24578 0 0 0 17 1 0 0
/proc/31454/statm: 4635 279 244 17 0 2626 0

[startup+0.115958 s]
/proc/loadavg: 1.36 1.52 0.94 5/87 31455
/proc/meminfo: memFree=1563096/2055920 swapFree=4192812/4192956
[pid=31454] ppid=31452 vsize=5352 CPUtime=0.06
/proc/31454/stat : 31454 (solver) S 31452 31454 29355 0 -1 4194304 376 2381 0 0 0 0 5 1 17 0 1 0 218573864 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/31454/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 5352

[startup+0.524025 s]
/proc/loadavg: 1.36 1.52 0.94 5/87 31455
/proc/meminfo: memFree=1563096/2055920 swapFree=4192812/4192956
[pid=31454] ppid=31452 vsize=5352 CPUtime=0.06
/proc/31454/stat : 31454 (solver) S 31452 31454 29355 0 -1 4194304 376 2381 0 0 0 0 5 1 17 0 1 0 218573864 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/31454/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 5352

[startup+1.34987 s]
/proc/loadavg: 1.36 1.52 0.94 3/88 31467
/proc/meminfo: memFree=1347664/2055920 swapFree=4192812/4192956
[pid=31454] ppid=31452 vsize=5352 CPUtime=0.06
/proc/31454/stat : 31454 (solver) S 31452 31454 29355 0 -1 4194304 376 2381 0 0 0 0 5 1 17 0 1 0 218573864 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/31454/statm: 1338 242 203 169 0 49 0
[pid=31467] ppid=31454 vsize=384248 CPUtime=1.24
/proc/31467/stat : 31467 (bordewijk) R 31454 31454 29355 0 -1 4194304 71795 0 0 0 89 35 0 0 25 0 1 0 218573874 393469952 71028 18446744073709551615 134512640 134912576 4294956768 18446744073709551615 134640313 0 0 4096 0 0 0 0 17 1 0 0
/proc/31467/statm: 96062 71028 214 97 0 95343 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 389600



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+2.88502 s]
/proc/loadavg: 1.41 1.53 0.95 3/88 31467
/proc/meminfo: memFree=728848/2055920 swapFree=4192812/4192956
[pid=31454] ppid=31452 vsize=5352 CPUtime=0.06
/proc/31454/stat : 31454 (solver) S 31452 31454 29355 0 -1 4194304 376 2381 0 0 0 0 5 1 17 0 1 0 218573864 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/31454/statm: 1338 242 203 169 0 49 0
[pid=31467] ppid=31454 vsize=928956 CPUtime=2.76
/proc/31467/stat : 31467 (bordewijk) R 31454 31454 29355 0 -1 4194304 207989 0 0 0 174 102 0 0 25 0 1 0 218573874 951250944 207222 18446744073709551615 134512640 134912576 4294956768 18446744073709551615 3325655 0 0 4096 0 0 0 0 17 1 0 0
/proc/31467/statm: 232239 207222 214 97 0 231520 0
Current children cumulated CPU time (s) 2.82
Current children cumulated vsize (KiB) 934308

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

[startup+3.00047 s]
/proc/loadavg: 1.41 1.53 0.95 3/88 31467
/proc/meminfo: memFree=728848/2055920 swapFree=4192812/4192956
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0

Child ended because it received signal 15 (SIGTERM)
Real time (s): 2.90078
CPU time (s): 0.078987
CPU user time (s): 0.05999
CPU system time (s): 0.018997
CPU usage (%): 2.72296
Max. virtual memory (cumulated for all children) (KiB): 934308

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

runsolver used 0.007998 s user time and 0.015997 s system time

The end



Launcher Data (download as text)




Begin job on node17 on Sat Jan 13 15:23:11 UTC 2007


IDJOB= 204050
IDBENCH= 3997
IDSOLVER= 83
FILE ID= node17/204050-1168701788

PBS_JOBID= 3547033

Free space on /tmp= 66551 MiB

SOLVER NAME= buggy_2_5 2007-01-08
BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-5000-5000.xml
COMMAND LINE= /tmp/evaluation/204050-1168701788/solver /tmp/evaluation/204050-1168701788/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-204050-1168701788 -o ROOT/results/node17/solver-204050-1168701788 -C 1800 -M 900  /tmp/evaluation/204050-1168701788/solver /tmp/evaluation/204050-1168701788/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  18de54b00f9f9844eda77aa609528237

RANDOM SEED= 246905629

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.236
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.236
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:       1563576 kB
Buffers:         12092 kB
Cached:         148592 kB
SwapCached:          0 kB
Active:         337756 kB
Inactive:        97408 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1563576 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           12160 kB
Writeback:           0 kB
Mapped:         294640 kB
Slab:            41616 kB
Committed_AS:  6722848 kB
PageTables:       2688 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= 66547 MiB



End job on node17 on Sat Jan 13 15:23:14 UTC 2007