Trace number 209002

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 1.73373 1.8051

General information on the benchmark

Namefapp/fapp01-05/fapp05/
fapp05-0350-6.xml
MD5SUMb7c19f015f837daea9cb8aeec5a1b404
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 benchmark1.65875
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables350
Number of constraints4665
Maximum constraint arity2
Maximum domain size270
Number of constraints which are defined in extension0
Number of constraints which are defined in intension4665
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/node40/watcher-209002-1168428245 -o ROOT/results/node40/solver-209002-1168428245 -C 1800 -M 900 /tmp/evaluation/209002-1168428245/solver2 /tmp/evaluation/209002-1168428245/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.03 0.66 0.26 4/68 5591
/proc/meminfo: memFree=1916240/2055920 swapFree=4191892/4192956
[pid=5590] ppid=5588 vsize=5352 CPUtime=0
/proc/5590/stat : 5590 (solver2) R 5588 5590 4094 0 -1 4194304 308 190 0 0 0 0 0 0 19 0 1 0 191225050 5480448 237 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 264519779318 0 0 4100 65536 0 0 0 17 1 0 0
/proc/5590/statm: 1338 239 200 169 0 49 0

[startup+0.106604 s]
/proc/loadavg: 1.03 0.66 0.26 4/68 5591
/proc/meminfo: memFree=1916240/2055920 swapFree=4191892/4192956
[pid=5590] ppid=5588 vsize=5352 CPUtime=0
/proc/5590/stat : 5590 (solver2) S 5588 5590 4094 0 -1 4194304 353 334 0 0 0 0 0 0 17 0 1 0 191225050 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 264519607108 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/5590/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.514648 s]
/proc/loadavg: 1.03 0.66 0.26 4/68 5591
/proc/meminfo: memFree=1916240/2055920 swapFree=4191892/4192956
[pid=5590] ppid=5588 vsize=5352 CPUtime=0.08
/proc/5590/stat : 5590 (solver2) S 5588 5590 4094 0 -1 4194304 376 2310 0 0 0 0 6 2 15 0 1 0 191225050 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 264519607108 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/5590/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5352

[startup+1.33475 s]
/proc/loadavg: 1.03 0.66 0.26 2/69 5603
/proc/meminfo: memFree=1885000/2055920 swapFree=4191892/4192956
[pid=5590] ppid=5588 vsize=5352 CPUtime=0.08
/proc/5590/stat : 5590 (solver2) S 5588 5590 4094 0 -1 4194304 376 2310 0 0 0 0 6 2 15 0 1 0 191225050 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 264519607108 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/5590/statm: 1338 242 203 169 0 49 0
[pid=5603] ppid=5590 vsize=28152 CPUtime=1.16
/proc/5603/stat : 5603 (bordewijk) R 5590 5590 4094 0 -1 4194304 7319 0 0 0 54 62 0 0 25 0 1 0 191225066 28827648 6430 18446744073709551615 134512640 134912576 4294956752 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/5603/statm: 7038 6430 217 97 0 6319 0
Current children cumulated CPU time (s) 1.24
Current children cumulated vsize (KiB) 33504

Child status: 0
Real time (s): 1.8051
CPU time (s): 1.73373
CPU user time (s): 0.777881
CPU system time (s): 0.955854
CPU usage (%): 96.0466
Max. virtual memory (cumulated for all children) (KiB): 33504

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

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node40 on Wed Jan 10 11:24:13 UTC 2007


IDJOB= 209002
IDBENCH= 4489
FILE ID= node40/209002-1168428245

PBS_JOBID= 3523862

Free space on /tmp= 66536 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp05/fapp05-0350-6.xml
COMMAND LINE= /tmp/evaluation/209002-1168428245/solver2 /tmp/evaluation/209002-1168428245/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node40/watcher-209002-1168428245 -o ROOT/results/node40/solver-209002-1168428245 -C 1800 -M 900  /tmp/evaluation/209002-1168428245/solver2 /tmp/evaluation/209002-1168428245/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  b7c19f015f837daea9cb8aeec5a1b404

RANDOM SEED= 628898797

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.239
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.239
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:       1916592 kB
Buffers:          2840 kB
Cached:          69784 kB
SwapCached:          0 kB
Active:          62616 kB
Inactive:        29348 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1916592 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:           22592 kB
Writeback:           0 kB
Mapped:          28552 kB
Slab:            33152 kB
Committed_AS:  4220904 kB
PageTables:       1620 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 node40 on Wed Jan 10 11:24:26 UTC 2007