Trace number 268581

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
VALCSP 3.1SAT 12.4201 12.5412

DiagnosticValue
CHECKS9503160
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-9.xml
MD5SUMcef6f21687f99f4d2823ff8263a0f14a
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.44478
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints2053
Maximum constraint arity2
Maximum domain size190
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2053
Global constraints used (with number of constraints)

Solver Data (download as text)

12.51	s SATISFIABLE
12.51	v -2636 2424 -2604 -2280 2420 2524 2552 -2532 -2484 -2328 -2288 -2640 2544 -2428 -2492 2352 2624 -2444 -2320 -2652 -2584 -2512 2320 -2312 -2652 -2452 2604 -2648 2564 -2388 -2600 2572 2616 -2384 -2552 -2484 -2592 -2504 -2464 -2580 -2556 2280 2492 -2444 -2380 -2320 -2524 -2408 -2476 -2600 -2512 -2656 -2396 -2328 -2324 2380 -2428 -2516 -2364 -2432 -2532 2300 -2464 -2512 -2492 -2516 2492 -2480 -2612 -2376 -2584 2440 -2632 -2532 -2328 -2608 -2384 2624 2600 2320 2392 2284 2324 2288 -2556 2596 -2656 -2612 -2620 -2640 2364 2396 -2572 -2532 -2560 2532 -2476 2416 -2596 -2616 -2596 2648 2492 2508 -2504 -2500 2560 2616 2496 -2344 -2452 2280 2424 -2656 -2308 -2456 -2480 -2616 -2440 2656 2520 -2552 -2356 -2356 -2460 -2320 2456 -2452 2452 -2496 -2596 -2528 -2512 -2340 2420 -2532 2596 -2536 -2620 -2632 -2360 -2656 -2504 -2288 -2432 -2564 2412 -2612 2404 -2412 -2368 2644 2464 2412 -2320 -2480 2580 -2348 -2532 -2636 2472 2280 2484 2388 2656 -2636 2492 -2472 2604 -2424 2324 2616 -2324 -2424 -2344 -2376 2544 -2416 2336 -2356 2592 2340 -2564 2316 -2652 -2608 2460 2284 -2320 -2452 -2492 2364 2304 2568 2280 -2616 -2464 2520 2280 -2548 
12.51	d CHECKS 9.50316e+06
12.51	d NODES 200

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/node5/watcher-268581-1168979520 -o ROOT/results/node5/solver-268581-1168979520 -C 1800 -M 900 /tmp/evaluation/268581-1168979520/VALCSP /tmp/evaluation/268581-1168979520/unknown.xml 

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: 2.02 2.00 1.61 5/86 8787
/proc/meminfo: memFree=1428464/2055920 swapFree=4192812/4192956
[pid=8786] ppid=8784 vsize=2128 CPUtime=0
/proc/8786/stat : 8786 (VALCSP) R 8784 8786 8692 0 -1 4194304 287 0 0 0 0 0 0 0 20 0 1 0 226566487 2179072 265 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134532931 0 0 4096 0 0 0 0 17 1 0 0
/proc/8786/statm: 532 265 64 8 0 204 0

[startup+0.105942 s]
/proc/loadavg: 2.02 2.00 1.61 5/86 8787
/proc/meminfo: memFree=1428464/2055920 swapFree=4192812/4192956
[pid=8786] ppid=8784 vsize=3712 CPUtime=0.09
/proc/8786/stat : 8786 (VALCSP) R 8784 8786 8692 0 -1 4194304 676 0 0 0 9 0 0 0 20 0 1 0 226566487 3801088 654 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529329 0 0 4096 0 0 0 0 17 1 0 0
/proc/8786/statm: 928 654 64 8 0 600 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3712

[startup+0.513987 s]
/proc/loadavg: 2.02 2.00 1.61 5/86 8787
/proc/meminfo: memFree=1428464/2055920 swapFree=4192812/4192956
[pid=8786] ppid=8784 vsize=8860 CPUtime=0.5
/proc/8786/stat : 8786 (VALCSP) R 8784 8786 8692 0 -1 4194304 1964 0 0 0 50 0 0 0 24 0 1 0 226566487 9072640 1942 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529332 0 0 4096 0 0 0 0 17 1 0 0
/proc/8786/statm: 2215 1942 64 8 0 1887 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 8860

[startup+1.33508 s]
/proc/loadavg: 2.02 2.00 1.61 3/86 8787
/proc/meminfo: memFree=1412976/2055920 swapFree=4192812/4192956
[pid=8786] ppid=8784 vsize=19288 CPUtime=1.31
/proc/8786/stat : 8786 (VALCSP) R 8784 8786 8692 0 -1 4194304 4577 0 0 0 129 2 0 0 25 0 1 0 226566487 19750912 4555 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528607 0 0 4096 0 0 0 0 17 1 0 0
/proc/8786/statm: 4822 4555 64 8 0 4494 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 19288

[startup+2.97227 s]
/proc/loadavg: 2.01 2.00 1.61 3/86 8787
/proc/meminfo: memFree=1399472/2055920 swapFree=4192812/4192956
[pid=8786] ppid=8784 vsize=39484 CPUtime=2.93
/proc/8786/stat : 8786 (VALCSP) R 8784 8786 8692 0 -1 4194304 9598 0 0 0 289 4 0 0 25 0 1 0 226566487 40431616 9576 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528676 0 0 4096 0 0 0 0 17 1 0 0
/proc/8786/statm: 9871 9576 64 8 0 9543 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 39484

[startup+6.25763 s]
/proc/loadavg: 2.01 2.00 1.61 3/86 8787
/proc/meminfo: memFree=1357040/2055920 swapFree=4192812/4192956
[pid=8786] ppid=8784 vsize=79876 CPUtime=6.19
/proc/8786/stat : 8786 (VALCSP) R 8784 8786 8692 0 -1 4194304 19707 0 0 0 611 8 0 0 25 0 1 0 226566487 81793024 19685 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528636 0 0 4096 0 0 0 0 17 1 0 0
/proc/8786/statm: 19969 19685 64 8 0 19641 0
Current children cumulated CPU time (s) 6.19
Current children cumulated vsize (KiB) 79876

Child status: 0
Real time (s): 12.5412
CPU time (s): 12.4201
CPU user time (s): 12.2331
CPU system time (s): 0.186971
CPU usage (%): 99.0347
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 12.2331
system time used= 0.186971
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 38770
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= 8
involuntary context switches= 483

runsolver used 0.010998 s user time and 0.051992 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Tue Jan 16 20:32:00 UTC 2007


IDJOB= 268581
IDBENCH= 4498
IDSOLVER= 90
FILE ID= node5/268581-1168979520

PBS_JOBID= 3565969

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp01/fapp01-0200-9.xml
COMMAND LINE= /tmp/evaluation/268581-1168979520/VALCSP /tmp/evaluation/268581-1168979520/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-268581-1168979520 -o ROOT/results/node5/solver-268581-1168979520 -C 1800 -M 900  /tmp/evaluation/268581-1168979520/VALCSP /tmp/evaluation/268581-1168979520/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  cef6f21687f99f4d2823ff8263a0f14a

RANDOM SEED= 34210777

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.240
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.240
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:       1428944 kB
Buffers:         48744 kB
Cached:         451192 kB
SwapCached:          0 kB
Active:         202756 kB
Inactive:       349436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1428944 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             412 kB
Writeback:           0 kB
Mapped:          72020 kB
Slab:            59828 kB
Committed_AS:  6261244 kB
PageTables:       2128 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= 66564 MiB



End job on node5 on Tue Jan 16 20:32:13 UTC 2007