Trace number 225626

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 3.09653 3.13474

General information on the benchmark

Nametightness/tightness0.9/
rand-2-40-180-84-900-51_ext.xml
MD5SUM942a82469df4d0e2584a31b71974ee56
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.816874
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints84
Maximum constraint arity2
Maximum domain size180
Number of constraints which are defined in extension84
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
40 47 122 96 21 130 134 101 90 25 15 38 108 74 20 19 93 154 28 13 161 90 6 56 0 72 23 38 3 110 109 87 64 21 8 34 45 88 99 91

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/node4/watcher-225626-1168296161 -o ROOT/results/node4/solver-225626-1168296161 -C 1800 -M 900 /tmp/evaluation/225626-1168296161/solver2 /tmp/evaluation/225626-1168296161/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.39 1.23 1.13 5/82 8361
/proc/meminfo: memFree=1322432/2055920 swapFree=4182144/4192956
[pid=8360] ppid=8357 vsize=5352 CPUtime=0
/proc/8360/stat : 8360 (solver2) S 8357 8360 7035 0 -1 4194304 295 26 0 0 0 0 0 0 19 0 1 0 178011958 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/8360/statm: 1338 232 194 169 0 49 0

[startup+0.107398 s]
/proc/loadavg: 1.39 1.23 1.13 5/82 8361
/proc/meminfo: memFree=1322432/2055920 swapFree=4182144/4192956
[pid=8360] ppid=8357 vsize=5352 CPUtime=0
/proc/8360/stat : 8360 (solver2) S 8357 8360 7035 0 -1 4194304 353 334 0 0 0 0 0 0 17 0 1 0 178011958 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/8360/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.515436 s]
/proc/loadavg: 1.39 1.23 1.13 5/82 8361
/proc/meminfo: memFree=1322432/2055920 swapFree=4182144/4192956
[pid=8360] ppid=8357 vsize=5352 CPUtime=0.27
/proc/8360/stat : 8360 (solver2) S 8357 8360 7035 0 -1 4194304 376 2230 0 0 0 0 23 4 16 0 1 0 178011958 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/8360/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 5352

[startup+1.33651 s]
/proc/loadavg: 1.39 1.23 1.13 3/88 8420
/proc/meminfo: memFree=1309520/2055920 swapFree=4182144/4192956
[pid=8360] ppid=8357 vsize=5352 CPUtime=0.27
/proc/8360/stat : 8360 (solver2) S 8357 8360 7035 0 -1 4194304 376 2230 0 0 0 0 23 4 16 0 1 0 178011958 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/8360/statm: 1338 242 203 169 0 49 0
[pid=8413] ppid=8360 vsize=2540 CPUtime=1.03
/proc/8413/stat : 8413 (bordewijk) R 8360 8360 7035 0 -1 4194304 536 0 0 0 102 1 0 0 25 0 1 0 178011987 2600960 380 18446744073709551615 134512640 134912576 4294956752 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/8413/statm: 635 380 177 97 0 213 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 7892

[startup+2.97367 s]
/proc/loadavg: 1.39 1.23 1.13 3/88 8422
/proc/meminfo: memFree=1308304/2055920 swapFree=4182144/4192956
[pid=8360] ppid=8357 vsize=5352 CPUtime=1.63
/proc/8360/stat : 8360 (solver2) S 8357 8360 7035 0 -1 4194304 397 3260 0 0 0 0 151 12 16 0 1 0 178011958 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/8360/statm: 1338 242 203 169 0 49 0
[pid=8421] ppid=8360 vsize=4108 CPUtime=1.3
/proc/8421/stat : 8421 (standalone) R 8360 8360 7035 0 -1 4194304 481 0 0 0 129 1 0 0 25 0 1 0 178012124 4206592 456 18446744073709551615 134512640 134775488 4294956896 18446744073709551615 134554206 0 0 4096 0 0 0 0 17 1 0 0
/proc/8421/statm: 1027 456 137 64 0 342 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 9460

Child status: 0
Real time (s): 3.13474
CPU time (s): 3.09653
CPU user time (s): 2.94955
CPU system time (s): 0.146977
CPU usage (%): 98.7812
Max. virtual memory (cumulated for all children) (KiB): 9868

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.94955
system time used= 0.146977
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4157
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= 79
involuntary context switches= 70

runsolver used 0.009998 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Mon Jan  8 22:42:44 UTC 2007


IDJOB= 225626
IDBENCH= 5882
FILE ID= node4/225626-1168296161

PBS_JOBID= 3502058

Free space on /tmp= 66291 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.9/rand-2-40-180-84-900-51_ext.xml
COMMAND LINE= /tmp/evaluation/225626-1168296161/solver2 /tmp/evaluation/225626-1168296161/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-225626-1168296161 -o ROOT/results/node4/solver-225626-1168296161 -C 1800 -M 900  /tmp/evaluation/225626-1168296161/solver2 /tmp/evaluation/225626-1168296161/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  942a82469df4d0e2584a31b71974ee56

RANDOM SEED= 462536753

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.223
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.223
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:       1322912 kB
Buffers:         91916 kB
Cached:         536504 kB
SwapCached:       2552 kB
Active:         396960 kB
Inactive:       273468 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1322912 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:           24828 kB
Writeback:           0 kB
Mapped:          51496 kB
Slab:            47508 kB
Committed_AS:  5132088 kB
PageTables:       2276 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= 66281 MiB



End job on node4 on Mon Jan  8 22:42:47 UTC 2007