Trace number 204081

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_s 2007-01-08SAT 0.206968 0.226276

General information on the benchmark

Namedomino/
domino-100-100.xml
MD5SUMfe5d3a596c95f9421040a43fb0a74448
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.021996
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints100
Maximum constraint arity2
Maximum domain size100
Number of constraints which are defined in extension0
Number of constraints which are defined in intension100
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node2/watcher-204081-1168293284 -o ROOT/results/node2/solver-204081-1168293284 -C 1800 -M 900 /tmp/evaluation/204081-1168293284/solver2 /tmp/evaluation/204081-1168293284/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.40 1.80 1.78 8/86 30695
/proc/meminfo: memFree=1673296/2055920 swapFree=4191880/4192956
[pid=30690] ppid=30685 vsize=5352 CPUtime=0
/proc/30690/stat : 30690 (solver2) S 30685 30690 28047 0 -1 4194304 295 0 0 0 0 0 0 0 21 0 1 0 177724321 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 206381310788 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/30690/statm: 1338 232 194 169 0 49 0
[pid=30693] ppid=30690 vsize=0 CPUtime=0
/proc/30693/stat : 30693 (solver2) R 30690 30690 28047 0 -1 4194372 26 0 0 0 0 0 0 0 21 0 1 0 177724321 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 65538 0 0 0 17 0 0 0
/proc/30693/statm: 0 0 0 0 0 0 0
[pid=30694] ppid=30690 vsize=3676 CPUtime=0
/proc/30694/stat : 30694 (grep) R 30690 30690 28047 0 -1 4194304 161 0 0 0 0 0 0 0 18 0 1 0 177724322 3764224 126 18446744073709551615 4194304 4274172 548682069536 18446744073709551615 206381142528 0 0 4096 0 0 0 0 17 1 0 0
/proc/30694/statm: 0 0 0 0 0 0 0

[startup+0.105944 s]
/proc/loadavg: 1.40 1.80 1.78 8/86 30695
/proc/meminfo: memFree=1673296/2055920 swapFree=4191880/4192956
[pid=30690] ppid=30685 vsize=5352 CPUtime=0.01
/proc/30690/stat : 30690 (solver2) S 30685 30690 28047 0 -1 4194304 376 2227 0 0 0 0 0 1 16 0 1 0 177724321 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 206381310788 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/30690/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.226276
CPU time (s): 0.206968
CPU user time (s): 0.088986
CPU system time (s): 0.117982
CPU usage (%): 91.467
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.088986
system time used= 0.117982
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3564
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= 73
involuntary context switches= 37

runsolver used 0.003999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Mon Jan  8 21:54:46 UTC 2007


IDJOB= 204081
IDBENCH= 3999
FILE ID= node2/204081-1168293284

PBS_JOBID= 3501800

Free space on /tmp= 66321 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-100-100.xml
COMMAND LINE= /tmp/evaluation/204081-1168293284/solver2 /tmp/evaluation/204081-1168293284/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-204081-1168293284 -o ROOT/results/node2/solver-204081-1168293284 -C 1800 -M 900  /tmp/evaluation/204081-1168293284/solver2 /tmp/evaluation/204081-1168293284/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  fe5d3a596c95f9421040a43fb0a74448

RANDOM SEED= 439895025

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.259
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	: 5931.00
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.259
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:       1674128 kB
Buffers:         56236 kB
Cached:         214388 kB
SwapCached:        288 kB
Active:         236536 kB
Inactive:        94440 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1674128 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:           21888 kB
Writeback:           0 kB
Mapped:          78596 kB
Slab:            35544 kB
Committed_AS:  4623836 kB
PageTables:       2252 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= 66320 MiB



End job on node2 on Mon Jan  8 21:54:48 UTC 2007