Trace number 207613

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 0.918859 0.927267

General information on the benchmark

Namefapp/test01-04/test01/
test01-0150-10.xml
MD5SUMca801d693e5f281aecf2d953ed79f03d
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 benchmark0.918859
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables150
Number of constraints1460
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1460
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
-2700 -2720 -2524 2220 -2584 -2644 -2280 2416 -2684 -2700 -2160 -2616 -2332 2532 2132 -2396 -2576 -2632 2120 -2660 -2672 -2644 -2508 -2656 -2236 2384 -2624 -2436 2624 -2524 -2236 -2412 -2660 -2680 -2608 -2560 -2240 -2212 -2544 -2220 -2472 -2560 -2660 2180 -2300 -2252 -2472 -2160 2492 -2468 -2676 -2548 -2684 -2604 -2480 -2680 -2700 -2204 -2440 -2160 -2600 -2636 -2648 -2388 -2700 2372 -2196 -2696 -2172 -2260 -2564 -2656 2640 -2688 -2660 -2328 2432 -2300 2524 -2276 2240 -2660 -2236 -2260 -2508 -2644 -2372 -2200 2636 2324 -2676 -2600 -2684 2564 -2364 2620 2536 -2164 -2392 -2280 2288 -2656 2584 -2672 -2432 -2700 2408 -2348 -2660 -2576 -2664 2180 -2584 -2700 2192 -2596 -2416 -2684 -2660 -2196 2260 2580 -2636 -2644 -2220 2568 -2288 -2696 -2700 -2700 2624 -2248 -2432 -2644 -2200 -2632 -2176 -2696 -2660 -2448 2136 2344 2376 2644 -2152 2484 -2660 -2456 -2604 -2700

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/node15/watcher-207613-1168293942 -o ROOT/results/node15/solver-207613-1168293942 -C 1800 -M 900 /tmp/evaluation/207613-1168293942/solver /tmp/evaluation/207613-1168293942/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.84 0.96 0.98 5/83 2618
/proc/meminfo: memFree=1660984/2055920 swapFree=4174172/4192956
[pid=2617] ppid=2615 vsize=5352 CPUtime=0
/proc/2617/stat : 2617 (solver) R 2615 2617 32314 0 -1 4194304 313 190 0 0 0 0 0 0 19 0 1 0 177789407 5480448 241 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 240472615583 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/2617/statm: 1338 241 202 169 0 49 0
[pid=2621] ppid=2617 vsize=5352 CPUtime=0
/proc/2621/stat : 2621 (solver) R 2617 2617 32314 0 -1 4194368 21 0 0 0 0 0 0 0 19 0 1 0 177789407 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 240472616231 0 0 4096 0 0 0 0 17 1 0 0
/proc/2621/statm: 0 0 0 0 0 0 0

[startup+0.108191 s]
/proc/loadavg: 0.84 0.96 0.98 5/83 2618
/proc/meminfo: memFree=1660984/2055920 swapFree=4174172/4192956
[pid=2617] ppid=2615 vsize=5352 CPUtime=0.03
/proc/2617/stat : 2617 (solver) S 2615 2617 32314 0 -1 4194304 376 2259 0 0 0 0 2 1 16 0 1 0 177789407 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 240472613700 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2617/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5352

[startup+0.51626 s]
/proc/loadavg: 0.84 0.96 0.98 5/83 2618
/proc/meminfo: memFree=1660984/2055920 swapFree=4174172/4192956
[pid=2617] ppid=2615 vsize=5352 CPUtime=0.03
/proc/2617/stat : 2617 (solver) S 2615 2617 32314 0 -1 4194304 376 2259 0 0 0 0 2 1 16 0 1 0 177789407 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 240472613700 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2617/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.927267
CPU time (s): 0.918859
CPU user time (s): 0.515921
CPU system time (s): 0.402938
CPU usage (%): 99.0932
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.515921
system time used= 0.402938
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6248
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= 103
involuntary context switches= 47

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node15 on Mon Jan  8 22:05:45 UTC 2007


IDJOB= 207613
IDBENCH= 4301
FILE ID= node15/207613-1168293942

PBS_JOBID= 3501854

Free space on /tmp= 66314 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/test01-04/test01/test01-0150-10.xml
COMMAND LINE= /tmp/evaluation/207613-1168293942/solver /tmp/evaluation/207613-1168293942/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node15/watcher-207613-1168293942 -o ROOT/results/node15/solver-207613-1168293942 -C 1800 -M 900  /tmp/evaluation/207613-1168293942/solver /tmp/evaluation/207613-1168293942/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  ca801d693e5f281aecf2d953ed79f03d

RANDOM SEED= 502494848

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.276
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.276
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:       1661864 kB
Buffers:         31852 kB
Cached:         274264 kB
SwapCached:       5800 kB
Active:         229676 kB
Inactive:       111732 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1661864 kB
SwapTotal:     4192956 kB
SwapFree:      4174172 kB
Dirty:           21864 kB
Writeback:           0 kB
Mapped:          45252 kB
Slab:            37608 kB
Committed_AS:  5356204 kB
PageTables:       2220 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= 66312 MiB



End job on node15 on Mon Jan  8 22:05:47 UTC 2007