Trace number 196654

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-08UNSAT 2.82757 2.82969

General information on the benchmark

Namefapp/fapp06-10/fapp07/
fapp07-0600-3.xml
MD5SUM26522588cd2fb30ae6473ca7df3ce87f
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark2.6216
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables600
Number of constraints8996
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension8996
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

UNSAT

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node4/watcher-196654-1168284505 -o ROOT/results/node4/solver-196654-1168284505 -C 1800 -M 900 /tmp/evaluation/196654-1168284505/solver2 /tmp/evaluation/196654-1168284505/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.95 1.03 1.12 4/81 9495
/proc/meminfo: memFree=1565568/2055920 swapFree=4182144/4192956
[pid=9494] ppid=9492 vsize=5352 CPUtime=0
/proc/9494/stat : 9494 (solver2) R 9492 9494 6019 0 -1 4194304 313 190 0 0 0 0 0 0 19 0 1 0 176846252 5480448 241 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913214623 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/9494/statm: 1338 241 202 169 0 49 0

[startup+0.102944 s]
/proc/loadavg: 0.95 1.03 1.12 4/81 9495
/proc/meminfo: memFree=1565568/2055920 swapFree=4182144/4192956
[pid=9494] ppid=9492 vsize=5352 CPUtime=0
/proc/9494/stat : 9494 (solver2) S 9492 9494 6019 0 -1 4194304 353 334 0 0 0 0 0 0 20 0 1 0 176846252 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/9494/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.510978 s]
/proc/loadavg: 0.95 1.03 1.12 4/81 9495
/proc/meminfo: memFree=1565568/2055920 swapFree=4182144/4192956
[pid=9494] ppid=9492 vsize=5352 CPUtime=0.14
/proc/9494/stat : 9494 (solver2) S 9492 9494 6019 0 -1 4194304 376 2374 0 0 0 0 12 2 16 0 1 0 176846252 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/9494/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.14
Current children cumulated vsize (KiB) 5352

[startup+1.33106 s]
/proc/loadavg: 0.95 1.03 1.12 2/82 9510
/proc/meminfo: memFree=1544568/2055920 swapFree=4182144/4192956
[pid=9494] ppid=9492 vsize=5352 CPUtime=0.14
/proc/9494/stat : 9494 (solver2) S 9492 9494 6019 0 -1 4194304 376 2374 0 0 0 0 12 2 16 0 1 0 176846252 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/9494/statm: 1338 242 203 169 0 49 0
[pid=9507] ppid=9494 vsize=47888 CPUtime=1.17
/proc/9507/stat : 9507 (bordewijk) R 9494 9494 6019 0 -1 4194304 13176 0 0 0 99 18 0 0 25 0 1 0 176846267 49037312 11289 18446744073709551615 134512640 134912576 4294956752 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/9507/statm: 11972 11289 217 97 0 11253 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 53240

Child status: 0
Real time (s): 2.82969
CPU time (s): 2.82757
CPU user time (s): 1.39979
CPU system time (s): 1.42778
CPU usage (%): 99.925
Max. virtual memory (cumulated for all children) (KiB): 53240

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.39979
system time used= 1.42778
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 20405
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= 244
involuntary context switches= 136

runsolver used 0.005999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Mon Jan  8 19:28:27 UTC 2007


IDJOB= 196654
IDBENCH= 3364
FILE ID= node4/196654-1168284505

PBS_JOBID= 3501655

Free space on /tmp= 66286 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp06-10/fapp07/fapp07-0600-3.xml
COMMAND LINE= /tmp/evaluation/196654-1168284505/solver2 /tmp/evaluation/196654-1168284505/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-196654-1168284505 -o ROOT/results/node4/solver-196654-1168284505 -C 1800 -M 900  /tmp/evaluation/196654-1168284505/solver2 /tmp/evaluation/196654-1168284505/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  26522588cd2fb30ae6473ca7df3ce87f

RANDOM SEED= 369782858

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.223
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.223
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:       1565984 kB
Buffers:         74996 kB
Cached:         312840 kB
SwapCached:       2552 kB
Active:         285728 kB
Inactive:       144100 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1565984 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:           31520 kB
Writeback:           0 kB
Mapped:          51464 kB
Slab:            45064 kB
Committed_AS:  5124644 kB
PageTables:       2232 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= 66286 MiB



End job on node4 on Mon Jan  8 19:28:30 UTC 2007