Trace number 201842

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 1.63175 1.63912

General information on the benchmark

Namerlfap/rlfapScens/
scen3.xml
MD5SUMf0a2bd3f50a529cea49f9ef816c8636b
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 benchmark1.00984
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables400
Number of constraints2760
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2760
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
72 310 72 310 114 352 16 254 100 338 30 268 114 352 442 680 16 254 30 268 254 16 114 352 30 268 44 282 100 338 72 310 128 366 428 666 86 324 156 394 296 58 86 324 16 254 352 114 254 16 16 254 30 268 16 254 366 128 58 296 394 156 456 694 58 296 254 16 44 282 428 666 30 268 30 268 254 16 512 750 324 86 394 156 254 16 254 16 338 100 338 100 254 16 456 694 114 352 72 310 16 254 44 282 86 324 142 380 254 16 30 268 100 338 114 352 44 282 86 324 16 254 338 100 338 100 72 310 72 310 352 114 680 442 142 380 30 268 338 100 338 100 86 324 156 394 100 338 44 282 282 44 30 268 366 128 128 366 58 296 142 380 30 268 100 338 16 254 30 268 428 666 44 282 30 268 394 156 128 366 128 366 30 268 470 708 86 324 16 254 428 666 352 114 44 282 30 268 72 310 44 282 268 30 30 268 338 100 58 296 30 268 16 254 58 296 44 282 100 338 128 366 428 666 268 30 100 338 352 114 254 16 100 338 156 394 72 310 338 100 114 352 16 254 268 30 352 114 282 44 366 128 58 296 352 114 268 30 30 268 380 142 30 268 282 44 268 30 352 114 114 352 338 100 30 268 30 268 44 282 296 58 366 128 16 254 30 268 128 366 428 666 16 254 16 254 58 296 58 296 16 254 142 380 16 254 16 254 254 16 442 680 268 30 338 100 156 394 156 394 268 30 268 30 114 352 86 324 30 268 128 366 100 338 30 268 282 44 100 338 366 128 16 254 86 324 16 254 30 268 114 352 394 156 86 324 268 30 100 338 30 268 100 338 30 268 282 44 380 142 114 352 44 282 470 708 156 394 44 282 44 282 114 352 30 268 100 338 114 352 268 30 282 44 352 114 16 254 414 652

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/node9/watcher-201842-1168290650 -o ROOT/results/node9/solver-201842-1168290650 -C 1800 -M 900 /tmp/evaluation/201842-1168290650/solver2 /tmp/evaluation/201842-1168290650/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.15 1.03 1.01 3/82 4951
/proc/meminfo: memFree=1789648/2055920 swapFree=4191880/4192956
[pid=4950] ppid=4948 vsize=5352 CPUtime=0
/proc/4950/stat : 4950 (solver2) S 4948 4950 1428 0 -1 4194304 331 190 0 0 0 0 0 0 19 0 1 0 177460398 5480448 241 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/4950/statm: 1338 241 202 169 0 49 0

[startup+0.106222 s]
/proc/loadavg: 1.15 1.03 1.01 3/82 4951
/proc/meminfo: memFree=1789648/2055920 swapFree=4191880/4192956
[pid=4950] ppid=4948 vsize=5352 CPUtime=0.04
/proc/4950/stat : 4950 (solver2) S 4948 4950 1428 0 -1 4194304 376 2262 0 0 0 0 3 1 16 0 1 0 177460398 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/4950/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5352

[startup+0.514263 s]
/proc/loadavg: 1.15 1.03 1.01 3/82 4951
/proc/meminfo: memFree=1789648/2055920 swapFree=4191880/4192956
[pid=4950] ppid=4948 vsize=5352 CPUtime=0.04
/proc/4950/stat : 4950 (solver2) S 4948 4950 1428 0 -1 4194304 376 2262 0 0 0 0 3 1 16 0 1 0 177460398 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/4950/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5352

[startup+1.33535 s]
/proc/loadavg: 1.15 1.03 1.01 2/82 4966
/proc/meminfo: memFree=1797520/2055920 swapFree=4191880/4192956
[pid=4950] ppid=4948 vsize=5352 CPUtime=0.63
/proc/4950/stat : 4950 (solver2) S 4948 4950 1428 0 -1 4194304 397 5356 0 0 0 0 30 33 15 0 1 0 177460398 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/4950/statm: 1338 242 203 169 0 49 0
[pid=4964] ppid=4950 vsize=6516 CPUtime=0.68
/proc/4964/stat : 4964 (standalone) R 4950 4950 1428 0 -1 4194304 1127 0 0 0 62 6 0 0 22 0 1 0 177460462 6672384 1044 18446744073709551615 134512640 134775488 4294956880 18446744073709551615 134527024 0 0 4096 0 0 0 0 17 0 0 0
/proc/4964/statm: 1629 1044 136 64 0 944 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 11868

Child status: 0
Real time (s): 1.63912
CPU time (s): 1.63175
CPU user time (s): 1.22981
CPU system time (s): 0.401938
CPU usage (%): 99.5502
Max. virtual memory (cumulated for all children) (KiB): 11868

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.22981
system time used= 0.401938
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6925
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= 101
involuntary context switches= 82

runsolver used 0.008998 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Mon Jan  8 21:10:53 UTC 2007


IDJOB= 201842
IDBENCH= 3787
FILE ID= node9/201842-1168290650

PBS_JOBID= 3501753

Free space on /tmp= 66525 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScens/scen3.xml
COMMAND LINE= /tmp/evaluation/201842-1168290650/solver2 /tmp/evaluation/201842-1168290650/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-201842-1168290650 -o ROOT/results/node9/solver-201842-1168290650 -C 1800 -M 900  /tmp/evaluation/201842-1168290650/solver2 /tmp/evaluation/201842-1168290650/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  f0a2bd3f50a529cea49f9ef816c8636b

RANDOM SEED= 631135672

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.231
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.231
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:       1790064 kB
Buffers:         14632 kB
Cached:         152248 kB
SwapCached:        264 kB
Active:         116428 kB
Inactive:        97576 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1790064 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:           24728 kB
Writeback:           0 kB
Mapped:          58880 kB
Slab:            36844 kB
Committed_AS:  5113908 kB
PageTables:       2160 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= 66537 MiB



End job on node9 on Mon Jan  8 21:10:55 UTC 2007