Trace number 233586

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
Tramontane 2006-12-04SAT 0.312951 0.325106

General information on the benchmark

Nametaillard/os-taillard-15/
os-taillard-15-105-9.xml
MD5SUMfe28efa0aafddf70d550bdbe6aff7dc4
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.303953
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size982
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.10	c 
0.10	c Parsing xml file
0.10	c 	domains...............    0
0.10	c 	variables.............    0
0.10	c 	predicates............    0
0.10	c 	constraints........... 0.22
0.26	c Allocating memory
0.26	c 
0.26	c time limit = -1
0.26	c heuristic = dom/wdeg
0.26	c restart policy = Geometric increment
0.26	c restart base = 149
0.26	c restart factor = 1.33
0.26	c 
0.26	c Solving
0.26	c
0.31	s SATISFIABLE
0.31	v 351 0 471 671 602 72 89 99 834 519 260 626 748 418 182 721 515 260 677 392 328 455 186 0 761 800 626 831 571 99 344 715 333 675 44 245 778 252 60 307 525 812 193 639 410 745 241 331 98 240 429 0 910 600 351 560 259 143 665 834 709 785 542 889 186 688 252 23 588 259 394 315 635 487 99 324 508 568 747 418 670 799 283 773 0 85 186 72 472 344 461 602 660 396 892 568 177 721 138 0 253 89 490 323 328 679 630 394 259 329 785 0 479 547 186 882 670 589 89 755 92 23 63 561 392 530 715 709 187 0 462 659 796 277 871 490 761 850 344 601 309 525 658 429 0 44 174 563 259 86 277 239 0 213 480 193 742 836 571 138 249 686 69 596 357 0 187 106 706 117 387 834 486 258 601 315 776 99 551 660 472 238 69 277 563 915 259 339 768 596 519 0 251 213 124 725 647 357 567 190 871 461 98 889 412 755 283 0 542 816 0 813 557 124 471 573 190 826 648 245 725 79 344 414 609
0.31	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/node52/watcher-233586-1168326955 -o ROOT/results/node52/solver-233586-1168326955 -C 1800 -M 900 /tmp/evaluation/233586-1168326955/tramontane/bin/solver /tmp/evaluation/233586-1168326955/unknown.xml -res geom -f 3 -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
/proc/loadavg: 2.22 2.07 1.94 5/74 2873
/proc/meminfo: memFree=1343688/2055920 swapFree=4192812/4192956
[pid=2872] ppid=2870 vsize=18540 CPUtime=0
/proc/2872/stat : 2872 (runsolver) R 2870 727 727 0 -1 4194368 4 0 0 0 0 0 0 0 19 0 1 0 181094049 18984960 277 18446744073709551615 4194304 4267372 548682068992 18446744073709551615 273653590327 0 0 4096 24578 0 0 0 17 1 0 0
/proc/2872/statm: 4635 277 242 17 0 2626 0
Current StackSize limit: 10240 KiB


[startup+0.108194 s]
/proc/loadavg: 2.22 2.07 1.94 5/74 2873
/proc/meminfo: memFree=1343688/2055920 swapFree=4192812/4192956
[pid=2872] ppid=2870 vsize=8368 CPUtime=0.09
/proc/2872/stat : 2872 (solver) R 2870 2872 727 0 -1 4194304 1160 0 0 0 9 0 0 0 20 0 1 0 181094049 8568832 1128 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4158648021 0 0 4096 0 0 0 0 17 1 0 0
/proc/2872/statm: 2092 1128 705 92 0 436 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8368

Child status: 0
Real time (s): 0.325106
CPU time (s): 0.312951
CPU user time (s): 0.292955
CPU system time (s): 0.019996
CPU usage (%): 96.2612
Max. virtual memory (cumulated for all children) (KiB): 15524

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.292955
system time used= 0.019996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2983
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= 12
involuntary context switches= 28

runsolver used 0.002999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node52 on Tue Jan  9 07:15:56 UTC 2007


IDJOB= 233586
IDBENCH= 6617
FILE ID= node52/233586-1168326955

PBS_JOBID= 3502947

Free space on /tmp= 66529 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-15/os-taillard-15-105-9.xml
COMMAND LINE= /tmp/evaluation/233586-1168326955/tramontane/bin/solver /tmp/evaluation/233586-1168326955/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node52/watcher-233586-1168326955 -o ROOT/results/node52/solver-233586-1168326955 -C 1800 -M 900  /tmp/evaluation/233586-1168326955/tramontane/bin/solver /tmp/evaluation/233586-1168326955/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  fe28efa0aafddf70d550bdbe6aff7dc4

RANDOM SEED= 784484140

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.232
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.232
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:       1344104 kB
Buffers:         76748 kB
Cached:         453720 kB
SwapCached:          0 kB
Active:         341308 kB
Inactive:       308876 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1344104 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3552 kB
Writeback:           0 kB
Mapped:         131024 kB
Slab:            46632 kB
Committed_AS:  4402780 kB
PageTables:       2064 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= 66529 MiB



End job on node52 on Tue Jan  9 07:15:56 UTC 2007