Trace number 237382

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.907861 0.91901

General information on the benchmark

Nameos-gp/
gp10-08-1093.xml
MD5SUMf2d50c563873b0a18a3cc88920688123
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.348946
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1094
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1000
Global constraints used (with number of constraints)

Solver Data (download as text)

0.21	c 
0.21	c Parsing xml file
0.21	c 	domains...............    0
0.21	c 	variables.............    0
0.21	c 	predicates............    0
0.21	c 	constraints........... 0.07
0.21	c Allocating memory
0.21	c 
0.21	c time limit = -1
0.21	c heuristic = dom/wdeg
0.21	c restart policy = No restart
0.21	c 
0.21	c Solving
0.21	c
0.90	s SATISFIABLE
0.90	v 1093 1090 108 407 695 1084 0 1082 1083 1030 418 0 1085 565 1030 1038 1078 1064 71 794 15 975 1089 1 407 0 684 782 685 742 695 89 516 478 1084 1078 1077 1051 1039 0 63 478 0 418 1083 515 1074 1039 1038 1082 107 1089 372 1076 6 1 920 1031 1028 386 742 62 1084 1082 1075 15 79 1030 690 1028 14 534 386 506 1074 14 1003 975 0 63 1 71 107 783 0 108 800 445 6 782 920 516 515 800 684 445 685 1 565 788 0
0.90	d          SAT      5490 BTS      0.76 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/node55/watcher-237382-1168347769 -o ROOT/results/node55/solver-237382-1168347769 -C 1800 -M 900 /tmp/evaluation/237382-1168347769/mistral/bin/solver /tmp/evaluation/237382-1168347769/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

/proc/loadavg: 2.15 2.24 2.07 5/73 20616
/proc/meminfo: memFree=1590320/2055920 swapFree=4192192/4192956
[pid=20615] ppid=20613 vsize=540 CPUtime=0
/proc/20615/stat : 20615 (solver) R 20613 20615 19310 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 183175274 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 6849316 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/20615/statm: 135 26 21 92 0 18 0

[startup+0.103144 s]
/proc/loadavg: 2.15 2.24 2.07 5/73 20616
/proc/meminfo: memFree=1590320/2055920 swapFree=4192192/4192956
[pid=20615] ppid=20613 vsize=13400 CPUtime=0.09
/proc/20615/stat : 20615 (solver) R 20613 20615 19310 0 -1 4194304 2430 0 0 0 8 1 0 0 18 0 1 0 183175274 13721600 2398 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8144049 0 0 4096 0 0 0 0 17 1 0 0
/proc/20615/statm: 3350 2398 715 92 0 1694 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 13400

[startup+0.511172 s]
/proc/loadavg: 2.15 2.24 2.07 5/73 20616
/proc/meminfo: memFree=1590320/2055920 swapFree=4192192/4192956
[pid=20615] ppid=20613 vsize=23452 CPUtime=0.49
/proc/20615/stat : 20615 (solver) R 20613 20615 19310 0 -1 4194304 4969 0 0 0 47 2 0 0 21 0 1 0 183175274 24014848 4937 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134792840 0 0 4096 0 0 0 0 17 1 0 0
/proc/20615/statm: 5863 4937 718 92 0 4207 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 23452

Child status: 0
Real time (s): 0.91901
CPU time (s): 0.907861
CPU user time (s): 0.881865
CPU system time (s): 0.025996
CPU usage (%): 98.7869
Max. virtual memory (cumulated for all children) (KiB): 23456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.881865
system time used= 0.025996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4991
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= 23

runsolver used 0.002999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node55 on Tue Jan  9 13:02:50 UTC 2007


IDJOB= 237382
IDBENCH= 6917
FILE ID= node55/237382-1168347769

PBS_JOBID= 3503570

Free space on /tmp= 66561 MiB

BENCH NAME= HOME/pub/bench/CPAI06/os-gp/gp10-08-1093.xml
COMMAND LINE= /tmp/evaluation/237382-1168347769/mistral/bin/solver /tmp/evaluation/237382-1168347769/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node55/watcher-237382-1168347769 -o ROOT/results/node55/solver-237382-1168347769 -C 1800 -M 900  /tmp/evaluation/237382-1168347769/mistral/bin/solver /tmp/evaluation/237382-1168347769/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  f2d50c563873b0a18a3cc88920688123

RANDOM SEED= 135816732

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.218
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.218
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:       1590800 kB
Buffers:         26920 kB
Cached:         165864 kB
SwapCached:        268 kB
Active:         306868 kB
Inactive:       101996 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1590800 kB
SwapTotal:     4192956 kB
SwapFree:      4192192 kB
Dirty:            3088 kB
Writeback:           0 kB
Mapped:         225896 kB
Slab:            41528 kB
Committed_AS:  4312548 kB
PageTables:       2060 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= 66561 MiB



End job on node55 on Tue Jan  9 13:02:51 UTC 2007