Trace number 268573

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.2681 12.3699

DiagnosticValue
CHECKS9322820
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-8.xml
MD5SUMc1b791b97abe156da51c58ae8c63048a
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.55776
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.34	s SATISFIABLE
12.34	v -2636 -2396 2576 -2588 -2280 2552 -2464 -2532 -2464 2320 -2280 -2640 2416 -2292 -2492 2656 -2644 -2552 -2280 2608 -2640 -2508 -2340 -2616 -2640 -2496 2616 -2648 2604 -2332 -2600 -2428 -2628 -2464 -2548 -2512 -2588 2572 2440 2492 2556 2320 2488 2504 -2464 -2368 -2532 -2580 -2432 -2540 -2484 -2656 -2348 -2404 -2336 2320 -2364 -2472 -2484 -2320 2468 2320 2436 2512 -2536 -2516 -2492 -2436 -2648 -2364 2604 2480 -2628 -2532 -2344 -2588 -2292 2600 -2600 2280 2280 2376 2356 -2364 2472 2596 2564 -2600 -2532 -2640 -2396 -2424 2572 -2532 -2456 2528 -2476 2488 2512 2616 -2596 2628 -2568 2512 -2436 2416 2580 -2524 -2380 2320 -2468 -2320 2376 2588 2360 -2528 -2456 2604 2476 -2656 -2416 -2552 2384 -2284 -2412 -2308 -2436 -2424 -2376 -2476 -2596 -2556 -2424 2424 -2372 2532 -2596 -2340 2552 -2584 -2348 2656 2456 -2304 -2432 2592 2384 -2656 -2444 -2416 -2620 -2656 -2532 2464 -2332 -2440 -2592 -2400 2528 -2556 -2444 2292 -2572 2324 2564 -2636 2492 -2472 -2644 2400 2408 -2616 -2436 -2424 -2332 -2404 2476 -2404 -2364 -2388 -2624 2280 2536 -2324 -2616 -2608 2456 -2316 -2548 -2424 -2428 -2368 2280 2596 -2408 -2616 -2336 -2416 -2300 -2552 
12.34	d CHECKS 9.32282e+06
12.34	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/node16/watcher-268573-1168979479 -o ROOT/results/node16/solver-268573-1168979479 -C 1800 -M 900 /tmp/evaluation/268573-1168979479/VALCSP /tmp/evaluation/268573-1168979479/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: 1.75 1.86 1.55 3/86 18192
/proc/meminfo: memFree=1379288/2055920 swapFree=4191880/4192956
[pid=18191] ppid=18189 vsize=1468 CPUtime=0
/proc/18191/stat : 18191 (VALCSP) R 18189 18191 17795 0 -1 4194304 114 0 0 0 0 0 0 0 20 0 1 0 246342732 1503232 92 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 7640699 0 0 4096 0 0 0 0 17 1 0 0
/proc/18191/statm: 367 92 64 8 0 39 0

[startup+0.104075 s]
/proc/loadavg: 1.75 1.86 1.55 3/86 18192
/proc/meminfo: memFree=1379288/2055920 swapFree=4191880/4192956
[pid=18191] ppid=18189 vsize=3580 CPUtime=0.09
/proc/18191/stat : 18191 (VALCSP) R 18189 18191 17795 0 -1 4194304 640 0 0 0 9 0 0 0 20 0 1 0 246342732 3665920 618 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529359 0 0 4096 0 0 0 0 17 1 0 0
/proc/18191/statm: 895 618 64 8 0 567 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3580

[startup+0.511999 s]
/proc/loadavg: 1.75 1.86 1.55 3/86 18192
/proc/meminfo: memFree=1379288/2055920 swapFree=4191880/4192956
[pid=18191] ppid=18189 vsize=8860 CPUtime=0.49
/proc/18191/stat : 18191 (VALCSP) R 18189 18191 17795 0 -1 4194304 1964 0 0 0 49 0 0 0 24 0 1 0 246342732 9072640 1942 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528582 0 0 4096 0 0 0 0 17 1 0 0
/proc/18191/statm: 2215 1942 64 8 0 1887 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 8860

[startup+1.33585 s]
/proc/loadavg: 1.75 1.86 1.55 3/86 18192
/proc/meminfo: memFree=1363736/2055920 swapFree=4191880/4192956
[pid=18191] ppid=18189 vsize=19552 CPUtime=1.31
/proc/18191/stat : 18191 (VALCSP) R 18189 18191 17795 0 -1 4194304 4613 0 0 0 130 1 0 0 25 0 1 0 246342732 20021248 4591 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529392 0 0 4096 0 0 0 0 17 1 0 0
/proc/18191/statm: 4888 4591 64 8 0 4560 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 19552

[startup+2.97854 s]
/proc/loadavg: 1.77 1.87 1.55 3/86 18192
/proc/meminfo: memFree=1349912/2055920 swapFree=4191880/4192956
[pid=18191] ppid=18189 vsize=40144 CPUtime=2.94
/proc/18191/stat : 18191 (VALCSP) R 18189 18191 17795 0 -1 4194304 9785 0 0 0 292 2 0 0 25 0 1 0 246342732 41107456 9763 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528600 0 0 4096 0 0 0 0 17 1 0 0
/proc/18191/statm: 10036 9763 64 8 0 9708 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 40144

[startup+6.25693 s]
/proc/loadavg: 1.77 1.87 1.55 3/86 18192
/proc/meminfo: memFree=1306968/2055920 swapFree=4191880/4192956
[pid=18191] ppid=18189 vsize=80668 CPUtime=6.19
/proc/18191/stat : 18191 (VALCSP) R 18189 18191 17795 0 -1 4194304 19918 0 0 0 613 6 0 0 25 0 1 0 246342732 82604032 19896 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529341 0 0 4096 0 0 0 0 17 1 0 0
/proc/18191/statm: 20167 19896 64 8 0 19839 0
Current children cumulated CPU time (s) 6.19
Current children cumulated vsize (KiB) 80668

Child status: 0
Real time (s): 12.3699
CPU time (s): 12.2681
CPU user time (s): 12.0882
CPU system time (s): 0.179972
CPU usage (%): 99.1773
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 12.0882
system time used= 0.179972
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= 494

runsolver used 0.014997 s user time and 0.043993 s system time

The end

Launcher Data (download as text)

Begin job on node16 on Tue Jan 16 20:31:19 UTC 2007


IDJOB= 268573
IDBENCH= 4490
IDSOLVER= 90
FILE ID= node16/268573-1168979479

PBS_JOBID= 3565980

Free space on /tmp= 66564 MiB

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

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  c1b791b97abe156da51c58ae8c63048a

RANDOM SEED= 737700201

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:       1379768 kB
Buffers:         61552 kB
Cached:         487168 kB
SwapCached:        448 kB
Active:         199768 kB
Inactive:       399644 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1379768 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:             804 kB
Writeback:           0 kB
Mapped:          69760 kB
Slab:            61572 kB
Committed_AS:  6801128 kB
PageTables:       2316 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 node16 on Tue Jan 16 20:31:31 UTC 2007