Trace number 209099

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 2007-01-08SAT 1.3108 1.35403

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-4.xml
MD5SUM51d70101c37b283f2266144f11c69f10
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.3108
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)

c 
c 
c 
c solution file
c 
c 

SAT
-2604 -2424 -2656 -2548 -2292 -2656 -2476 -2532 2504 2320 -2280 -2568 -2436 2412 -2492 -2560 -2604 -2552 -2296 -2616 2592 -2552 -2320 2520 -2532 -2468 2624 -2648 2616 2372 -2608 -2468 2616 -2368 2512 -2512 -2640 2548 -2420 -2456 2544 -2336 2472 -2464 2420 -2456 -2528 -2616 -2468 2528 2440 -2656 -2336 -2456 -2308 2332 -2352 -2428 2448 -2320 2508 -2344 -2464 -2540 2428 2480 -2532 -2408 -2656 -2344 2644 2344 2600 -2532 -2324 2608 2292 -2632 -2608 2320 2280 2348 2280 2416 -2540 -2540 2568 2572 -2496 -2568 -2320 2408 -2572 -2532 -2544 2512 -2520 -2492 -2580 -2608 2584 -2648 -2552 -2512 -2540 -2460 2568 -2608 -2392 -2320 -2440 2280 2416 -2656 -2336 -2532 -2464 -2616 2368 -2656 2504 2500 -2448 2320 -2296 -2348 2420 -2400 -2352 -2460 -2600 2584 -2436 -2460 2336 -2492 -2564 -2352 2600 -2608 -2308 -2648 -2476 -2284 -2460 2616 -2360 2576 -2408 -2392 -2656 2584 2508 -2440 2532 -2384 -2640 2296 -2512 -2580 2480 -2572 2568 -2392 2656 -2640 -2492 -2420 -2656 -2460 2392 -2616 -2280 -2408 -2332 -2336 -2500 -2384 2376 -2376 -2568 -2384 -2616 -2280 2616 -2608 -2420 2320 2588 -2400 2480 -2352 -2280 2624 -2416 -2616 -2376 2504 -2280 -2552

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/node17/watcher-209099-1168294340 -o ROOT/results/node17/solver-209099-1168294340 -C 1800 -M 900 /tmp/evaluation/209099-1168294340/solver /tmp/evaluation/209099-1168294340/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.27 1.52 1.25 5/83 2906
/proc/meminfo: memFree=1467968/2055920 swapFree=4192812/4192956
[pid=2905] ppid=2902 vsize=5352 CPUtime=0
/proc/2905/stat : 2905 (solver) S 2902 2905 1488 0 -1 4194304 295 164 0 0 0 0 0 0 16 0 1 0 177829343 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/2905/statm: 1338 232 194 169 0 49 0
[pid=2907] ppid=2905 vsize=0 CPUtime=0
/proc/2907/stat : 2907 (solver) D 2905 2905 1488 0 -1 4194372 26 0 0 0 0 0 0 0 21 0 1 0 177829343 0 0 18446744073709551615 0 0 0 0 0 0 2147483391 4096 65538 18446744072099781622 0 0 17 0 0 0
/proc/2907/statm: 0 0 0 0 0 0 0

[startup+0.104735 s]
/proc/loadavg: 1.27 1.52 1.25 5/83 2906
/proc/meminfo: memFree=1467968/2055920 swapFree=4192812/4192956
[pid=2905] ppid=2902 vsize=5352 CPUtime=0.04
/proc/2905/stat : 2905 (solver) S 2902 2905 1488 0 -1 4194304 376 2268 0 0 0 0 3 1 16 0 1 0 177829343 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/2905/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5352

[startup+0.512774 s]
/proc/loadavg: 1.27 1.52 1.25 5/83 2906
/proc/meminfo: memFree=1467968/2055920 swapFree=4192812/4192956
[pid=2905] ppid=2902 vsize=5352 CPUtime=0.04
/proc/2905/stat : 2905 (solver) S 2902 2905 1488 0 -1 4194304 376 2268 0 0 0 0 3 1 16 0 1 0 177829343 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/2905/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5352

[startup+1.33387 s]
/proc/loadavg: 1.27 1.52 1.25 3/88 2935
/proc/meminfo: memFree=1455640/2055920 swapFree=4192812/4192956
[pid=2905] ppid=2902 vsize=5352 CPUtime=0.59
/proc/2905/stat : 2905 (solver) S 2902 2905 1488 0 -1 4194304 396 5318 0 0 0 0 25 34 15 0 1 0 177829343 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/2905/statm: 1338 242 203 169 0 49 0
[pid=2934] ppid=2905 vsize=6692 CPUtime=0.68
/proc/2934/stat : 2934 (standalone) R 2905 2905 1488 0 -1 4194304 1147 0 0 0 61 7 0 0 23 0 1 0 177829407 6852608 1120 18446744073709551615 134512640 134775488 4294956880 18446744073709551615 4157721263 0 0 4096 0 0 0 0 17 1 0 0
/proc/2934/statm: 1673 1120 137 64 0 988 0
Current children cumulated CPU time (s) 1.27
Current children cumulated vsize (KiB) 12044

Child status: 0
Real time (s): 1.35403
CPU time (s): 1.3108
CPU user time (s): 0.889864
CPU system time (s): 0.420936
CPU usage (%): 96.8072
Max. virtual memory (cumulated for all children) (KiB): 12044

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.889864
system time used= 0.420936
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6890
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= 118
involuntary context switches= 86

runsolver used 0.001999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node17 on Mon Jan  8 22:12:23 UTC 2007


IDJOB= 209099
IDBENCH= 4495
FILE ID= node17/209099-1168294340

PBS_JOBID= 3501883

Free space on /tmp= 66308 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp01/fapp01-0200-4.xml
COMMAND LINE= /tmp/evaluation/209099-1168294340/solver /tmp/evaluation/209099-1168294340/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-209099-1168294340 -o ROOT/results/node17/solver-209099-1168294340 -C 1800 -M 900  /tmp/evaluation/209099-1168294340/solver /tmp/evaluation/209099-1168294340/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  51d70101c37b283f2266144f11c69f10

RANDOM SEED= 275882086

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.236
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.236
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:       1468912 kB
Buffers:         81296 kB
Cached:         375528 kB
SwapCached:          0 kB
Active:         324692 kB
Inactive:       193300 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1468912 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           21648 kB
Writeback:           0 kB
Mapped:          76760 kB
Slab:            54136 kB
Committed_AS:  5124896 kB
PageTables:       2076 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= 66305 MiB



End job on node17 on Mon Jan  8 22:12:30 UTC 2007