Trace number 216773

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-08SAT 0.366943 0.379181

General information on the benchmark

Namerlfap/rlfapScensMod/
scen2-f24.xml
MD5SUM5c81ef8039e928ad204d17c019cf929c
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.252961
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints1235
Maximum constraint arity2
Maximum domain size22
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1235
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
72 310 100 338 30 268 254 16 86 324 268 30 128 366 16 254 324 86 156 394 156 394 268 30 142 380 30 268 44 282 16 254 16 254 254 16 324 86 254 16 254 16 338 100 338 100 254 16 100 338 100 338 16 254 86 324 16 254 366 128 72 310 142 380 394 156 324 86 16 254 352 114 352 114 30 268 128 366 30 268 44 282 58 296 114 352 268 30 58 296 114 352 114 352 366 128 282 44 16 254 16 254 72 310 16 254 128 366 16 254 44 282 72 310 100 338 86 324 86 324 30 268 268 30 30 268 380 142 44 282 282 44 268 30 30 268 100 338 128 366 296 58 58 296 366 128 156 394 30 268 16 254 310 72 296 58 16 254 254 16 338 100 268 30 86 324 156 394 30 268 296 58 114 352 100 338 16 254 30 268 100 338 86 324 282 44 114 352 44 282 128 366 58 296 282 44 114 352 268 30

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/node14/watcher-216773-1168294616 -o ROOT/results/node14/solver-216773-1168294616 -C 1800 -M 900 /tmp/evaluation/216773-1168294616/solver /tmp/evaluation/216773-1168294616/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.60 1.45 1.21 6/89 26224
/proc/meminfo: memFree=1375224/2055920 swapFree=4163780/4192956
[pid=26221] ppid=26219 vsize=5352 CPUtime=0
/proc/26221/stat : 26221 (solver) S 26219 26221 22754 0 -1 4194304 295 164 0 0 0 0 0 0 16 0 1 0 177856924 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 212234462020 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/26221/statm: 1338 232 194 169 0 49 0
[pid=26222] ppid=26221 vsize=0 CPUtime=0
/proc/26222/stat : 26222 (solver) R 26221 26221 22754 0 -1 4194372 26 0 0 0 0 0 0 0 21 0 1 0 177856924 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 65538 0 0 0 17 0 0 0
/proc/26222/statm: 0 0 0 0 0 0 0

[startup+0.110777 s]
/proc/loadavg: 1.60 1.45 1.21 6/89 26224
/proc/meminfo: memFree=1375224/2055920 swapFree=4163780/4192956
[pid=26221] ppid=26219 vsize=5352 CPUtime=0.02
/proc/26221/stat : 26221 (solver) S 26219 26221 22754 0 -1 4194304 376 2245 0 0 0 0 1 1 16 0 1 0 177856924 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 212234462020 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/26221/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.379181
CPU time (s): 0.366943
CPU user time (s): 0.199969
CPU system time (s): 0.166974
CPU usage (%): 96.7725
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.199969
system time used= 0.166974
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4719
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= 91
involuntary context switches= 34

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node14 on Mon Jan  8 22:16:58 UTC 2007


IDJOB= 216773
IDBENCH= 5100
FILE ID= node14/216773-1168294616

PBS_JOBID= 3501888

Free space on /tmp= 66256 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScensMod/scen2-f24.xml
COMMAND LINE= /tmp/evaluation/216773-1168294616/solver /tmp/evaluation/216773-1168294616/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-216773-1168294616 -o ROOT/results/node14/solver-216773-1168294616 -C 1800 -M 900  /tmp/evaluation/216773-1168294616/solver /tmp/evaluation/216773-1168294616/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  5c81ef8039e928ad204d17c019cf929c

RANDOM SEED= 925884940

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.227
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.227
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:       1375976 kB
Buffers:         30960 kB
Cached:         258064 kB
SwapCached:       4056 kB
Active:         525676 kB
Inactive:       112880 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1375976 kB
SwapTotal:     4192956 kB
SwapFree:      4163780 kB
Dirty:           10984 kB
Writeback:           0 kB
Mapped:         359192 kB
Slab:            25636 kB
Committed_AS:  6200708 kB
PageTables:       2796 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= 66256 MiB



End job on node14 on Mon Jan  8 22:17:05 UTC 2007