Trace number 204705

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 1.63575 1.64243

General information on the benchmark

Namefapp/fapp16-20/fapp17/
fapp17-0300-10.xml
MD5SUMf7d83e5046cff98a2f782fbfcef83f73
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.63575
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables300
Number of constraints3865
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3865
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
-2640 -2180 2356 2592 -2544 2400 2608 2460 2396 2132 2176 2460 2608 2460 2416 2136 2544 2628 -2380 2136 2600 2520 2200 2456 2372 -2284 2492 2692 2380 2496 2424 2460 2528 -2504 -2720 -2588 2440 2128 2680 2604 -2424 2600 2652 2504 -2536 -2304 2560 -2536 2420 -2456 -2500 2652 -2496 2284 2176 -2720 2220 -2644 -2224 2456 -2664 2288 -2504 2136 -2396 2176 2536 2568 2296 2680 2628 2376 2176 2408 2176 2416 2536 -2192 2256 -2256 2420 2628 2692 -2504 2544 2516 2460 2676 2552 2504 2612 2136 2168 -2148 2316 2168 -2416 2416 2604 2456 2456 2420 2356 -2456 2368 2680 2380 2668 2496 2576 -2184 2360 -2196 2720 2176 2188 2380 2164 2140 2324 -2256 2680 2336 2656 2544 -2420 2136 2504 2264 -2504 2416 -2720 2500 -2240 2152 2504 -2236 2232 -2612 2416 2324 2316 2504 2568 2144 2668 -2176 2692 2420 2368 2544 -2480 2568 2456 2528 -2180 2544 2136 2420 2644 2324 2152 2616 2184 2456 2456 2208 2276 -2544 -2376 2456 2668 2692 -2616 -2704 2568 2328 2652 2668 2544 -2236 2420 -2652 2276 2524 -2400 2200 2460 -2264 2396 2420 2652 2168 2476 2324 -2244 2636 2608 2332 -2504 -2524 2288 2436 2628 2284 2416 2144 -2204 -2496 2136 -2396 -2416 2652 2640 2484 -2120 -2416 2296 2384 -2196 2668 2420 2440 2204 2316 -2272 2548 2304 2416 2396 2504 2480 -2284 -2380 2708 2496 -2168 2472 -2208 2132 2456 2536 2416 2160 2488 -2628 2608 2416 2416 2544 -2128 2628 -2384 2264 2568 2416 2484 2172 2524 2544 2220 2172 2496 -2376 2588 2296 2332 -2136 2628 2568 2456 2292 2668 2544 2448 2144 -2456 2184 -2176 2456 2440 2628 2508 2512 -2416 2192 -2532 2180 -2484 2164 2532 -2492 2284 2248 -2436 -2276 -2248 2240 -2668 2436

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/node7/watcher-204705-1168293505 -o ROOT/results/node7/solver-204705-1168293505 -C 1800 -M 900 /tmp/evaluation/204705-1168293505/solver2 /tmp/evaluation/204705-1168293505/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.93 1.28 1.63 4/81 31807
/proc/meminfo: memFree=1627072/2055920 swapFree=4192812/4192956
[pid=31806] ppid=31804 vsize=5352 CPUtime=0
/proc/31806/stat : 31806 (solver2) R 31804 31806 29041 0 -1 4194304 313 190 0 0 0 0 0 0 19 0 1 0 177746120 5480448 241 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 244671113887 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/31806/statm: 1338 241 202 169 0 49 0
[pid=31810] ppid=31806 vsize=5352 CPUtime=0
/proc/31810/stat : 31810 (solver2) R 31806 31806 29041 0 -1 4194368 19 0 0 0 0 0 0 0 19 0 1 0 177746121 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 4334492 0 0 4096 0 0 0 0 17 1 0 0
/proc/31810/statm: 1338 242 203 169 0 49 0

[startup+0.10601 s]
/proc/loadavg: 0.93 1.28 1.63 4/81 31807
/proc/meminfo: memFree=1627072/2055920 swapFree=4192812/4192956
[pid=31806] ppid=31804 vsize=5352 CPUtime=0.08
/proc/31806/stat : 31806 (solver2) S 31804 31806 29041 0 -1 4194304 376 2296 0 0 0 0 7 1 16 0 1 0 177746120 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 244671112004 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/31806/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5352

[startup+0.514061 s]
/proc/loadavg: 0.93 1.28 1.63 4/81 31807
/proc/meminfo: memFree=1627072/2055920 swapFree=4192812/4192956
[pid=31806] ppid=31804 vsize=5352 CPUtime=0.08
/proc/31806/stat : 31806 (solver2) S 31804 31806 29041 0 -1 4194304 376 2296 0 0 0 0 7 1 16 0 1 0 177746120 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 244671112004 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/31806/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5352

[startup+1.33514 s]
/proc/loadavg: 0.93 1.28 1.63 2/82 31819
/proc/meminfo: memFree=1600632/2055920 swapFree=4192812/4192956
[pid=31806] ppid=31804 vsize=5352 CPUtime=1.14
/proc/31806/stat : 31806 (solver2) S 31804 31806 29041 0 -1 4194304 397 8388 0 0 0 0 53 61 16 0 1 0 177746120 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 244671112004 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/31806/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 1.14
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 1.64243
CPU time (s): 1.63575
CPU user time (s): 0.867868
CPU system time (s): 0.767883
CPU usage (%): 99.5933
Max. virtual memory (cumulated for all children) (KiB): 29272

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.867868
system time used= 0.767883
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 11292
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= 149
involuntary context switches= 63

runsolver used 0.003999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node7 on Mon Jan  8 21:58:27 UTC 2007


IDJOB= 204705
IDBENCH= 4049
FILE ID= node7/204705-1168293505

PBS_JOBID= 3501814

Free space on /tmp= 66536 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp16-20/fapp17/fapp17-0300-10.xml
COMMAND LINE= /tmp/evaluation/204705-1168293505/solver2 /tmp/evaluation/204705-1168293505/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node7/watcher-204705-1168293505 -o ROOT/results/node7/solver-204705-1168293505 -C 1800 -M 900  /tmp/evaluation/204705-1168293505/solver2 /tmp/evaluation/204705-1168293505/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  f7d83e5046cff98a2f782fbfcef83f73

RANDOM SEED= 763576918

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:       1627552 kB
Buffers:         76120 kB
Cached:         237088 kB
SwapCached:          0 kB
Active:         254668 kB
Inactive:       118512 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1627552 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           28368 kB
Writeback:           0 kB
Mapped:          79016 kB
Slab:            40220 kB
Committed_AS:  5428140 kB
PageTables:       2192 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= 66532 MiB



End job on node7 on Mon Jan  8 21:58:29 UTC 2007