Trace number 233344

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
Mistral 2006-12-04SAT 0.304953 0.312851

General information on the benchmark

Nametaillard/os-taillard-15/
os-taillard-15-105-3.xml
MD5SUM69b5565aeb2925a1d5ec2e6bae551819
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.280956
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size993
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3150
Global constraints used (with number of constraints)

Solver Data (download as text)

0.20	c 
0.20	c Parsing xml file
0.20	c 	domains...............    0
0.20	c 	variables.............    0
0.20	c 	predicates............    0
0.20	c 	constraints........... 0.22
0.25	c Allocating memory
0.25	c 
0.25	c time limit = -1
0.25	c heuristic = dom/wdeg
0.25	c restart policy = No restart
0.25	c 
0.25	c Solving
0.25	c
0.30	s SATISFIABLE
0.30	v 886 0 564 196 510 88 268 79 346 717 449 51 161 181 62 618 261 88 905 381 458 664 0 573 714 173 843 72 495 315 493 684 365 433 520 728 180 0 637 276 90 588 814 93 868 565 92 785 753 640 162 452 259 703 622 381 0 819 508 312 789 83 739 546 0 262 162 122 575 603 99 181 346 474 641 517 0 527 90 787 267 656 614 174 773 640 728 363 444 428 339 564 414 703 521 268 0 675 739 448 883 51 82 172 61 819 0 124 883 633 251 51 162 761 172 656 458 528 419 324 698 220 826 276 714 517 261 93 162 614 789 863 0 373 455 540 291 662 448 83 172 901 781 370 0 568 826 696 373 748 0 380 833 862 606 99 533 717 886 196 798 457 662 761 291 178 433 761 681 328 92 606 245 918 0 315 573 162 670 506 347 575 0 363 77 871 324 599 455 180 675 508 195 835 258 527 863 633 241 810 664 339 88 440 178 618 720 578 0 905 556 25 599 901 771 449 72 0 267 622 793 868 370 170 693
0.30	d          SAT         0 BTS      0.02 s

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/node50/watcher-233344-1168325513 -o ROOT/results/node50/solver-233344-1168325513 -C 1800 -M 900 /tmp/evaluation/233344-1168325513/mistral/bin/solver /tmp/evaluation/233344-1168325513/unknown.xml -v 1 

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


[startup+0.104963 s]
/proc/loadavg: 1.92 1.87 1.57 5/80 4354
/proc/meminfo: memFree=1114336/2055920 swapFree=4191892/4192956
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0
/proc/loadavg: 1.92 1.87 1.57 5/80 4354
/proc/meminfo: memFree=1114336/2055920 swapFree=4191892/4192956
[pid=4353] ppid=4351 vsize=8764 CPUtime=0.19
/proc/4353/stat : 4353 (solver) R 4351 4353 3381 0 -1 4194304 1275 0 0 0 19 0 0 0 19 0 1 0 180949937 8974336 1243 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4158768985 0 0 4096 0 0 0 0 17 1 0 0
/proc/4353/statm: 2191 1243 705 92 0 535 0

Child status: 0
Real time (s): 0.312851
CPU time (s): 0.304953
CPU user time (s): 0.291955
CPU system time (s): 0.012998
CPU usage (%): 97.4755
Max. virtual memory (cumulated for all children) (KiB): 9060

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.291955
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2995
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= 13
involuntary context switches= 18

runsolver used 0.007998 s user time and 0.002999 s system time

The end

Launcher Data (download as text)

Begin job on node50 on Tue Jan  9 06:51:54 UTC 2007


IDJOB= 233344
IDBENCH= 6599
FILE ID= node50/233344-1168325513

PBS_JOBID= 3502954

Free space on /tmp= 66557 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-15/os-taillard-15-105-3.xml
COMMAND LINE= /tmp/evaluation/233344-1168325513/mistral/bin/solver /tmp/evaluation/233344-1168325513/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node50/watcher-233344-1168325513 -o ROOT/results/node50/solver-233344-1168325513 -C 1800 -M 900  /tmp/evaluation/233344-1168325513/mistral/bin/solver /tmp/evaluation/233344-1168325513/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  69b5565aeb2925a1d5ec2e6bae551819

RANDOM SEED= 562451818

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.263
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	: 5931.00
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.263
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:       1114816 kB
Buffers:         71116 kB
Cached:         399252 kB
SwapCached:        396 kB
Active:         576396 kB
Inactive:       306516 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1114816 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            3448 kB
Writeback:           0 kB
Mapped:         431368 kB
Slab:            42608 kB
Committed_AS:  5250928 kB
PageTables:       2656 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= 66557 MiB



End job on node50 on Tue Jan  9 06:51:54 UTC 2007