Trace number 209195

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.89471 1.9118

General information on the benchmark

Namefapp/fapp01-05/fapp03/
fapp03-0300-8.xml
MD5SUMa5626f805a0c21e1617c11a14c43910c
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.89471
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables300
Number of constraints4377
Maximum constraint arity2
Maximum domain size250
Number of constraints which are defined in extension0
Number of constraints which are defined in intension4377
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
-2292 -2612 -2600 -2428 -2316 -2252 2464 -2400 2336 -2420 -2292 -2184 2292 2420 2568 -2500 -2356 2576 -2652 -2656 2164 -2440 2172 -2288 2600 2224 2372 -2596 2200 2396 -2264 -2508 -2656 -2424 -2600 -2564 2516 2400 -2200 -2516 -2228 -2304 2288 -2200 -2160 -2568 2596 2160 2180 2252 2560 -2612 -2196 2556 -2452 2264 2552 -2508 -2640 -2356 -2456 -2584 -2560 2248 2440 -2452 -2432 -2548 2444 -2480 -2436 -2484 -2460 -2600 2468 -2224 2432 -2520 -2220 2544 -2212 -2472 -2264 2304 -2252 -2616 2424 -2572 -2576 2304 -2376 -2352 -2616 -2580 -2528 2372 2628 2200 -2544 2600 2372 2560 2364 -2564 -2324 2260 -2600 -2360 2604 -2408 -2504 2652 -2656 2412 2412 -2336 -2656 -2536 -2200 -2612 -2464 -2548 -2240 2252 2304 2644 2616 -2548 -2212 2380 2412 -2572 -2640 -2400 -2468 2492 -2564 2532 -2340 -2244 2180 -2432 -2536 2404 2632 2212 2172 -2308 -2184 -2532 2372 -2344 2652 -2560 -2608 -2608 2556 2224 -2556 2568 2412 -2188 2564 -2228 -2332 -2220 2360 -2588 -2500 -2344 -2316 -2440 -2568 -2508 2480 -2612 -2448 -2588 2592 2524 -2316 2476 2520 2616 -2580 -2624 2200 -2268 -2160 2336 -2592 2544 -2500 -2300 -2568 2348 -2204 -2408 -2600 2328 -2520 2548 -2368 -2588 2480 2452 -2528 -2440 2300 -2584 -2160 -2448 2160 -2540 -2600 -2560 -2576 -2380 2460 -2612 2468 -2160 -2640 -2648 2316 -2560 -2620 -2372 -2600 2376 -2604 -2204 -2604 2408 -2480 2560 -2440 2388 -2296 -2208 -2652 -2216 2332 2616 -2300 2588 -2656 -2576 2604 -2572 2508 -2636 -2496 2616 2200 2392 -2528 -2524 -2640 2276 -2400 -2584 -2616 -2608 2488 -2332 2600 -2340 -2444 -2604 -2392 -2176 2472 -2484 2560 2212 2444 2644 2460 -2436 -2612 2456 -2332 -2236 2248 2228 2268 2348 -2304 -2468 2616 -2184 -2644 -2608 -2260 -2656 -2276 -2572 -2496 2380

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/node9/watcher-209195-1168294359 -o ROOT/results/node9/solver-209195-1168294359 -C 1800 -M 900 /tmp/evaluation/209195-1168294359/solver /tmp/evaluation/209195-1168294359/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.72 1.93 1.90 7/88 31646
/proc/meminfo: memFree=1717736/2055920 swapFree=4191880/4192956
[pid=31644] ppid=31642 vsize=5352 CPUtime=0
/proc/31644/stat : 31644 (solver) S 31642 31644 29349 0 -1 4194304 295 0 0 0 0 0 0 0 20 0 1 0 177831704 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/31644/statm: 1338 232 194 169 0 49 0
[pid=31645] ppid=31644 vsize=0 CPUtime=0
/proc/31645/stat : 31645 (solver) R 31644 31644 29349 0 -1 4194372 26 0 0 0 0 0 0 0 21 0 1 0 177831704 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 65538 0 0 0 17 0 0 0
/proc/31645/statm: 0 0 0 0 0 0 0
[pid=31647] ppid=31644 vsize=0 CPUtime=0
/proc/31647/stat : 31647 (grep) D 31644 31644 29349 0 -1 4194308 164 0 0 0 0 0 0 0 17 0 1 0 177831704 0 0 18446744073709551615 0 0 0 0 0 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/31647/statm: 0 0 0 0 0 0 0

[startup+0.104614 s]
/proc/loadavg: 1.72 1.93 1.90 7/88 31646
/proc/meminfo: memFree=1717736/2055920 swapFree=4191880/4192956
[pid=31644] ppid=31642 vsize=5352 CPUtime=0.08
/proc/31644/stat : 31644 (solver) S 31642 31644 29349 0 -1 4194304 376 2304 0 0 0 0 6 2 16 0 1 0 177831704 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/31644/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5352

[startup+0.512655 s]
/proc/loadavg: 1.72 1.93 1.90 7/88 31646
/proc/meminfo: memFree=1717736/2055920 swapFree=4191880/4192956
[pid=31644] ppid=31642 vsize=5352 CPUtime=0.08
/proc/31644/stat : 31644 (solver) S 31642 31644 29349 0 -1 4194304 376 2304 0 0 0 0 6 2 16 0 1 0 177831704 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/31644/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5352

[startup+1.33375 s]
/proc/loadavg: 1.74 1.94 1.90 3/88 31657
/proc/meminfo: memFree=1690920/2055920 swapFree=4191880/4192956
[pid=31644] ppid=31642 vsize=5352 CPUtime=1.12
/proc/31644/stat : 31644 (solver) S 31642 31644 29349 0 -1 4194304 396 8730 0 0 0 0 54 58 16 0 1 0 177831704 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/31644/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 1.12
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 1.9118
CPU time (s): 1.89471
CPU user time (s): 1.17082
CPU system time (s): 0.723889
CPU usage (%): 99.1062
Max. virtual memory (cumulated for all children) (KiB): 30204

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.17082
system time used= 0.723889
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 11481
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= 163
involuntary context switches= 100

runsolver used 0.002999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Mon Jan  8 22:12:44 UTC 2007


IDJOB= 209195
IDBENCH= 4501
FILE ID= node9/209195-1168294359

PBS_JOBID= 3501793

Free space on /tmp= 66526 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp03/fapp03-0300-8.xml
COMMAND LINE= /tmp/evaluation/209195-1168294359/solver /tmp/evaluation/209195-1168294359/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-209195-1168294359 -o ROOT/results/node9/solver-209195-1168294359 -C 1800 -M 900  /tmp/evaluation/209195-1168294359/solver /tmp/evaluation/209195-1168294359/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  a5626f805a0c21e1617c11a14c43910c

RANDOM SEED= 694798009

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.231
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.231
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:       1718416 kB
Buffers:         25532 kB
Cached:         211456 kB
SwapCached:        264 kB
Active:         153048 kB
Inactive:       132608 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1718416 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:           11544 kB
Writeback:           0 kB
Mapped:          61492 kB
Slab:            36640 kB
Committed_AS:  5139180 kB
PageTables:       2284 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= 66523 MiB



End job on node9 on Mon Jan  8 22:12:48 UTC 2007