Trace number 200163

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
VALCSP 3.0SAT 1.06084 1.07314

DiagnosticValue
CHECKS2053950
NODES50

General information on the benchmark

NamejobShop/jobShop-enddr2/
enddr2-10-by-5-3.xml
MD5SUM9395c389369aaeeeb08dff599b8a5b25
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.036994
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size143
Number of constraints which are defined in extension0
Number of constraints which are defined in intension265
Global constraints used (with number of constraints)

Solver Data (download as text)

1.06	s SATISFIABLE
1.06	v 33 42 81 92 102 0 45 140 150 168 0 8 39 54 58 8 15 26 58 67 35 50 124 140 156 58 69 102 114 130 15 26 54 65 76 42 50 92 102 117 25 69 114 124 142 0 19 65 81 92 
1.06	d CHECKS 2.05395e+06
1.06	d NODES 50
1.06

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/node17/watcher-200163-1168141708 -o ROOT/results/node17/solver-200163-1168141708 -C 1800 -M 900 /tmp/evaluation/200163-1168141708/VALCSP /tmp/evaluation/200163-1168141708/unknown.xml 

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.04 2.03 2.11 5/88 5601
/proc/meminfo: memFree=1675096/2055920 swapFree=4192812/4192956
[pid=5600] ppid=5598 vsize=1732 CPUtime=0
/proc/5600/stat : 5600 (VALCSP) R 5598 5600 1584 0 -1 4194304 170 0 0 0 0 0 0 0 20 0 1 0 162565562 1773568 148 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530948 0 0 4096 0 0 0 0 17 1 0 0
/proc/5600/statm: 433 148 64 8 0 105 0

[startup+0.106899 s]
/proc/loadavg: 2.04 2.03 2.11 5/88 5601
/proc/meminfo: memFree=1675096/2055920 swapFree=4192812/4192956
[pid=5600] ppid=5598 vsize=4240 CPUtime=0.09
/proc/5600/stat : 5600 (VALCSP) R 5598 5600 1584 0 -1 4194304 812 0 0 0 9 0 0 0 20 0 1 0 162565562 4341760 790 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530881 0 0 4096 0 0 0 0 17 1 0 0
/proc/5600/statm: 1060 790 64 8 0 732 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4240

[startup+0.515942 s]
/proc/loadavg: 2.04 2.03 2.11 5/88 5601
/proc/meminfo: memFree=1675096/2055920 swapFree=4192812/4192956
[pid=5600] ppid=5598 vsize=11104 CPUtime=0.5
/proc/5600/stat : 5600 (VALCSP) R 5598 5600 1584 0 -1 4194304 2522 0 0 0 49 1 0 0 24 0 1 0 162565562 11370496 2500 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530236 0 0 4096 0 0 0 0 17 1 0 0
/proc/5600/statm: 2776 2500 64 8 0 2448 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 11104

Child status: 0
Real time (s): 1.07314
CPU time (s): 1.06084
CPU user time (s): 1.03384
CPU system time (s): 0.026995
CPU usage (%): 98.8535
Max. virtual memory (cumulated for all children) (KiB): 19816

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.03384
system time used= 0.026995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4785
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= 8
involuntary context switches= 25

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node17 on Sun Jan  7 03:48:28 UTC 2007


IDJOB= 200163
IDBENCH= 3692
FILE ID= node17/200163-1168141708

PBS_JOBID= 3477799

Free space on /tmp= 66327 MiB

BENCH NAME= HOME/pub/bench/CPAI06/jobShop/jobShop-enddr2/enddr2-10-by-5-3.xml
COMMAND LINE= /tmp/evaluation/200163-1168141708/VALCSP /tmp/evaluation/200163-1168141708/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-200163-1168141708 -o ROOT/results/node17/solver-200163-1168141708 -C 1800 -M 900  /tmp/evaluation/200163-1168141708/VALCSP /tmp/evaluation/200163-1168141708/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  9395c389369aaeeeb08dff599b8a5b25

RANDOM SEED= 416937285

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.236
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.236
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:       1675576 kB
Buffers:         57048 kB
Cached:         179660 kB
SwapCached:          0 kB
Active:         176076 kB
Inactive:       125164 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1675576 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          85144 kB
Slab:            63908 kB
Committed_AS:  4182892 kB
PageTables:       2284 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= 66327 MiB



End job on node17 on Sun Jan  7 03:48:29 UTC 2007