Trace number 231530

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.544916 0.552834

General information on the benchmark

Namegeom/
geo50-20-d4-75-17_ext.xml
MD5SUM4658794fd82f442cbc94e3f54b52c9d0
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.125979
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints410
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension410
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
7 4 16 11 19 7 14 1 6 10 8 2 18 9 1 7 11 11 3 1 13 12 11 15 9 14 20 13 1 14 2 6 9 11 17 2 12 1 11 7 4 2 18 3 1 9 14 6 11 13

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-231530-1168318138 -o ROOT/results/node4/solver-231530-1168318138 -C 1800 -M 900 /tmp/evaluation/231530-1168318138/solver2 /tmp/evaluation/231530-1168318138/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: 0.54 1.29 1.68 4/81 15440
/proc/meminfo: memFree=1299528/2055920 swapFree=4182144/4192956
[pid=15439] ppid=15437 vsize=5352 CPUtime=0
/proc/15439/stat : 15439 (solver2) R 15437 15439 14353 0 -1 4194304 313 190 0 0 0 0 0 0 19 0 1 0 180209619 5480448 241 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913382501 0 0 4100 65536 0 0 0 17 1 0 0
/proc/15439/statm: 1338 241 202 169 0 49 0

[startup+0.10409 s]
/proc/loadavg: 0.54 1.29 1.68 4/81 15440
/proc/meminfo: memFree=1299528/2055920 swapFree=4182144/4192956
[pid=15439] ppid=15437 vsize=5352 CPUtime=0.05
/proc/15439/stat : 15439 (solver2) S 15437 15439 14353 0 -1 4194304 376 2242 0 0 0 0 4 1 16 0 1 0 180209619 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/15439/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5352

[startup+0.51213 s]
/proc/loadavg: 0.54 1.29 1.68 4/81 15440
/proc/meminfo: memFree=1299528/2055920 swapFree=4182144/4192956
[pid=15439] ppid=15437 vsize=5352 CPUtime=0.48
/proc/15439/stat : 15439 (solver2) S 15437 15439 14353 0 -1 4194304 397 3131 0 0 0 0 42 6 15 0 1 0 180209619 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/15439/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.552834
CPU time (s): 0.544916
CPU user time (s): 0.469928
CPU system time (s): 0.074988
CPU usage (%): 98.5677
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.469928
system time used= 0.074988
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3945
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= 84
involuntary context switches= 29

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Tue Jan  9 04:49:00 UTC 2007


IDJOB= 231530
IDBENCH= 6471
FILE ID= node4/231530-1168318138

PBS_JOBID= 3502626

Free space on /tmp= 66520 MiB

BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-17_ext.xml
COMMAND LINE= /tmp/evaluation/231530-1168318138/solver2 /tmp/evaluation/231530-1168318138/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-231530-1168318138 -o ROOT/results/node4/solver-231530-1168318138 -C 1800 -M 900  /tmp/evaluation/231530-1168318138/solver2 /tmp/evaluation/231530-1168318138/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  4658794fd82f442cbc94e3f54b52c9d0

RANDOM SEED= 799681731

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:       1300008 kB
Buffers:         98260 kB
Cached:         552736 kB
SwapCached:       2552 kB
Active:         425900 kB
Inactive:       267332 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1300008 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:           12344 kB
Writeback:           0 kB
Mapped:          51656 kB
Slab:            47668 kB
Committed_AS:  5288604 kB
PageTables:       2232 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= 66519 MiB



End job on node4 on Tue Jan  9 04:49:03 UTC 2007