Trace number 207373

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.89971 1.90879

General information on the benchmark

Namefapp/test01-04/test02/
test02-0250-9.xml
MD5SUMd4598e7df9c6cd251da4bae6f1b00f2b
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.89971
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables250
Number of constraints2462
Maximum constraint arity2
Maximum domain size350
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2462
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
-2900 -2540 -2876 -2352 -2592 -2352 -2596 -2448 -2648 -2864 -2380 -2484 2376 -2352 -2352 2652 2400 2244 -2688 -2392 -2712 -2556 2516 2720 -2820 -2776 -2512 -2352 -2656 -2228 -2412 -2664 -2296 -2484 -2336 -2592 2904 -2392 -2864 -2292 -2688 -2416 -2612 -2816 -2336 -2304 2332 -2328 -2556 -2824 2876 2804 2600 -2420 -2532 2220 -2736 -2700 -2916 2752 -2876 2784 -2392 -2688 2828 -2424 -2400 2632 -2876 -2896 2628 2460 2712 2596 2696 -2636 -2916 -2328 -2824 2608 -2584 2876 -2916 2220 2540 2844 2596 -2708 2260 -2392 -2408 -2856 2460 2268 2588 -2688 -2464 -2660 -2668 -2916 -2876 2352 -2564 -2792 -2636 2832 2552 -2368 2660 2248 -2568 -2916 -2648 2340 2288 -2392 -2584 -2520 -2440 -2392 -2904 2700 -2264 -2380 -2500 -2636 2528 2624 2544 2824 -2500 -2892 2544 -2392 -2544 2864 -2916 2376 -2372 2628 -2352 -2312 -2452 -2504 -2752 2672 -2888 -2480 2220 -2352 -2568 -2368 -2376 -2576 -2692 2848 -2568 -2616 -2440 -2648 2320 -2700 2648 -2648 -2568 2220 2760 -2460 -2256 -2876 2648 -2916 2620 -2260 -2632 2588 -2792 2780 -2864 2372 -2916 -2860 -2604 -2500 -2876 -2788 -2392 -2652 2836 -2612 2752 2820 -2476 2740 2552 2572 -2660 -2560 2888 2852 -2792 -2436 2340 -2916 -2416 -2344 -2688 -2444 -2688 -2876 2440 -2580 -2800 -2296 -2472 -2516 -2608 -2628 2304 2672 -2436 -2352 -2360 -2608 -2252 2444 -2560 -2332 -2664 -2392 -2748 -2876 -2260 -2860 2696 -2848 -2760 -2544 2624 2220 2260 -2352 -2584 -2572 -2284 -2916 -2876 2396 -2260 -2592

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-207373-1168293881 -o ROOT/results/node16/solver-207373-1168293881 -C 1800 -M 900 /tmp/evaluation/207373-1168293881/solver /tmp/evaluation/207373-1168293881/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.81 1.22 1.49 5/82 26375
/proc/meminfo: memFree=1423624/2055920 swapFree=4191880/4192956
[pid=26374] ppid=26372 vsize=5352 CPUtime=0
/proc/26374/stat : 26374 (solver) R 26372 26374 24263 0 -1 4194304 295 0 0 0 0 0 0 0 19 0 1 0 177783177 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962370884 0 65536 4100 65538 0 0 0 17 1 0 0
/proc/26374/statm: 1338 232 194 169 0 49 0
[pid=26376] ppid=26374 vsize=0 CPUtime=0
/proc/26376/stat : 26376 (solver) Z 26374 26374 24263 0 -1 4194380 26 0 0 0 0 0 0 0 15 0 1 0 177783177 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 65538 18446744071563351923 0 0 17 1 0 0
/proc/26376/statm: 0 0 0 0 0 0 0
[pid=26377] ppid=26374 vsize=0 CPUtime=0
/proc/26377/stat : 26377 (grep) Z 26374 26374 24263 0 -1 4194316 164 0 0 0 0 0 0 0 15 0 1 0 177783177 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 1 0 0
/proc/26377/statm: 0 0 0 0 0 0 0

[startup+0.103375 s]
/proc/loadavg: 0.81 1.22 1.49 5/82 26375
/proc/meminfo: memFree=1423624/2055920 swapFree=4191880/4192956
[pid=26374] ppid=26372 vsize=5352 CPUtime=0.07
/proc/26374/stat : 26374 (solver) S 26372 26374 24263 0 -1 4194304 376 2275 0 0 0 0 5 2 16 0 1 0 177783177 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962370884 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/26374/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5352

[startup+0.511299 s]
/proc/loadavg: 0.81 1.22 1.49 5/82 26375
/proc/meminfo: memFree=1423624/2055920 swapFree=4191880/4192956
[pid=26374] ppid=26372 vsize=5352 CPUtime=0.07
/proc/26374/stat : 26374 (solver) S 26372 26374 24263 0 -1 4194304 376 2275 0 0 0 0 5 2 16 0 1 0 177783177 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962370884 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/26374/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5352

[startup+1.33214 s]
/proc/loadavg: 0.81 1.22 1.49 2/82 26388
/proc/meminfo: memFree=1414728/2055920 swapFree=4191880/4192956
[pid=26374] ppid=26372 vsize=5352 CPUtime=0.88
/proc/26374/stat : 26374 (solver) S 26372 26374 24263 0 -1 4194304 396 6546 0 0 0 0 33 55 16 0 1 0 177783177 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 231962370884 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/26374/statm: 1338 242 203 169 0 49 0
[pid=26388] ppid=26374 vsize=10240 CPUtime=0.42
/proc/26388/stat : 26388 (standalone) R 26374 26374 24263 0 -1 4194304 1972 0 0 0 29 13 0 0 21 0 1 0 177783267 10485760 1945 18446744073709551615 134512640 134775488 4294956880 18446744073709551615 4154186659 0 0 4096 0 0 0 0 17 1 0 0
/proc/26388/statm: 2560 1945 136 64 0 1875 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 15592

Child status: 0
Real time (s): 1.90879
CPU time (s): 1.89971
CPU user time (s): 1.19982
CPU system time (s): 0.699893
CPU usage (%): 99.5241
Max. virtual memory (cumulated for all children) (KiB): 15600

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.19982
system time used= 0.699893
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9000
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= 123
involuntary context switches= 99

runsolver used 0.000999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node16 on Mon Jan  8 22:04:43 UTC 2007


IDJOB= 207373
IDBENCH= 4286
FILE ID= node16/207373-1168293881

PBS_JOBID= 3501849

Free space on /tmp= 66512 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/test01-04/test02/test02-0250-9.xml
COMMAND LINE= /tmp/evaluation/207373-1168293881/solver /tmp/evaluation/207373-1168293881/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node16/watcher-207373-1168293881 -o ROOT/results/node16/solver-207373-1168293881 -C 1800 -M 900  /tmp/evaluation/207373-1168293881/solver /tmp/evaluation/207373-1168293881/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  d4598e7df9c6cd251da4bae6f1b00f2b

RANDOM SEED= 933211367

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:       1424304 kB
Buffers:         91808 kB
Cached:         432772 kB
SwapCached:        448 kB
Active:         353368 kB
Inactive:       219484 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1424304 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:           11864 kB
Writeback:           0 kB
Mapped:          66496 kB
Slab:            43904 kB
Committed_AS:  4962604 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= 66511 MiB



End job on node16 on Mon Jan  8 22:04:47 UTC 2007