Trace number 228454

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 2.33564 2.38206

General information on the benchmark

Nametightness/tightness0.2/
rand-2-40-11-414-200-77_ext.xml
MD5SUMe0232ff1cd663bbf4eff56b536b635e7
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 benchmark2.33264
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints414
Maximum constraint arity2
Maximum domain size11
Number of constraints which are defined in extension414
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
2 3 0 1 7 9 1 9 4 9 2 8 8 8 3 4 8 2 0 3 9 8 5 6 1 0 1 8 1 10 4 10 3 6 2 10 5 3 1 7

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/node16/watcher-228454-1168298636 -o ROOT/results/node16/solver-228454-1168298636 -C 1800 -M 900 /tmp/evaluation/228454-1168298636/solver2 /tmp/evaluation/228454-1168298636/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.98 1.43 1.47 3/87 18994
/proc/meminfo: memFree=1353624/2055920 swapFree=4191880/4192956
[pid=18993] ppid=18991 vsize=5212 CPUtime=0
/proc/18993/stat : 18993 (solver2) R 18991 18993 18017 0 -1 4194304 123 0 0 0 0 0 0 0 21 0 1 0 178258570 5337088 95 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962803524 0 0 4096 0 0 0 0 17 1 0 0
/proc/18993/statm: 1303 95 76 169 0 14 0

[startup+0.103506 s]
/proc/loadavg: 1.98 1.43 1.47 3/87 18994
/proc/meminfo: memFree=1353624/2055920 swapFree=4191880/4192956
[pid=18993] ppid=18991 vsize=5352 CPUtime=0.03
/proc/18993/stat : 18993 (solver2) S 18991 18993 18017 0 -1 4194304 376 2243 0 0 0 0 2 1 20 0 1 0 178258570 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962370884 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/18993/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5352

[startup+0.511427 s]
/proc/loadavg: 1.98 1.43 1.47 3/87 18994
/proc/meminfo: memFree=1353624/2055920 swapFree=4191880/4192956
[pid=18993] ppid=18991 vsize=5352 CPUtime=0.23
/proc/18993/stat : 18993 (solver2) S 18991 18993 18017 0 -1 4194304 397 2873 0 0 0 0 18 5 15 0 1 0 178258570 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962370884 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/18993/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.23
Current children cumulated vsize (KiB) 5352

[startup+1.33228 s]
/proc/loadavg: 1.98 1.43 1.47 3/88 19007
/proc/meminfo: memFree=1351888/2055920 swapFree=4191880/4192956
[pid=18993] ppid=18991 vsize=5352 CPUtime=0.23
/proc/18993/stat : 18993 (solver2) S 18991 18993 18017 0 -1 4194304 397 2873 0 0 0 0 18 5 15 0 1 0 178258570 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962370884 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/18993/statm: 1338 242 203 169 0 49 0
[pid=19007] ppid=18993 vsize=3408 CPUtime=1.05
/proc/19007/stat : 19007 (standalone) R 18993 18993 18017 0 -1 4194304 335 0 0 0 105 0 0 0 25 0 1 0 178258596 3489792 309 18446744073709551615 134512640 134775488 4294956880 18446744073709551615 134554507 0 0 4096 0 0 0 0 17 1 0 0
/proc/19007/statm: 852 309 137 64 0 167 0
Current children cumulated CPU time (s) 1.28
Current children cumulated vsize (KiB) 8760

Child status: 0
Real time (s): 2.38206
CPU time (s): 2.33564
CPU user time (s): 2.26266
CPU system time (s): 0.072988
CPU usage (%): 98.0513
Max. virtual memory (cumulated for all children) (KiB): 8760

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.26266
system time used= 0.072988
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3624
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= 85
involuntary context switches= 114

runsolver used 0.004999 s user time and 0.013997 s system time

The end

Launcher Data (download as text)

Begin job on node16 on Mon Jan  8 23:23:57 UTC 2007


IDJOB= 228454
IDBENCH= 6197
FILE ID= node16/228454-1168298636

PBS_JOBID= 3502151

Free space on /tmp= 66510 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.2/rand-2-40-11-414-200-77_ext.xml
COMMAND LINE= /tmp/evaluation/228454-1168298636/solver2 /tmp/evaluation/228454-1168298636/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node16/watcher-228454-1168298636 -o ROOT/results/node16/solver-228454-1168298636 -C 1800 -M 900  /tmp/evaluation/228454-1168298636/solver2 /tmp/evaluation/228454-1168298636/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  e0232ff1cd663bbf4eff56b536b635e7

RANDOM SEED= 996565695

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.220
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.220
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:       1354040 kB
Buffers:        101960 kB
Cached:         483140 kB
SwapCached:        448 kB
Active:         403904 kB
Inactive:       238848 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1354040 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:           10172 kB
Writeback:           0 kB
Mapped:          76968 kB
Slab:            43900 kB
Committed_AS:  5022152 kB
PageTables:       2380 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= 66510 MiB



End job on node16 on Mon Jan  8 23:24:00 UTC 2007