Trace number 268855

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.1SAT 0.97785 0.981266

DiagnosticValue
CHECKS1960910
NODES64

General information on the benchmark

NamejobShop/
jobShop-e0ddr2/e0ddr2-10-by-5-10.xml
MD5SUMcd420abf4fa5344f1217005e29afc0b6
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.033994
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size134
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)

0.97	s SATISFIABLE
0.97	v 0 10 15 27 32 10 15 58 74 85 19 53 74 88 93 0 7 127 136 148 7 26 46 58 69 32 43 109 117 139 15 23 98 109 117 17 26 32 46 53 32 43 117 127 130 0 35 88 98 108 
0.97	d CHECKS 1.96091e+06
0.97	d NODES 64

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/node24/watcher-268855-1168979942 -o ROOT/results/node24/solver-268855-1168979942 -C 1800 -M 900 /tmp/evaluation/268855-1168979942/VALCSP /tmp/evaluation/268855-1168979942/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: 0.11 0.51 0.67 3/82 5581
/proc/meminfo: memFree=1364080/2055920 swapFree=4192800/4192956
[pid=5580] ppid=5577 vsize=1732 CPUtime=0
/proc/5580/stat : 5580 (VALCSP) R 5577 5580 5470 0 -1 4194304 170 0 0 0 0 0 0 0 18 0 1 0 246391295 1773568 148 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528695 0 0 4096 0 0 0 0 17 1 0 0
/proc/5580/statm: 433 148 64 8 0 105 0

[startup+0.10288 s]
/proc/loadavg: 0.11 0.51 0.67 3/82 5581
/proc/meminfo: memFree=1364080/2055920 swapFree=4192800/4192956
[pid=5580] ppid=5577 vsize=4372 CPUtime=0.09
/proc/5580/stat : 5580 (VALCSP) R 5577 5580 5470 0 -1 4194304 843 0 0 0 9 0 0 0 18 0 1 0 246391295 4476928 821 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 3040891 0 0 4096 0 0 0 0 17 1 0 0
/proc/5580/statm: 1093 821 64 8 0 765 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4372

[startup+0.514921 s]
/proc/loadavg: 0.11 0.51 0.67 3/82 5581
/proc/meminfo: memFree=1364080/2055920 swapFree=4192800/4192956
[pid=5580] ppid=5577 vsize=11500 CPUtime=0.5
/proc/5580/stat : 5580 (VALCSP) R 5577 5580 5470 0 -1 4194304 2631 0 0 0 50 0 0 0 22 0 1 0 246391295 11776000 2609 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529332 0 0 4096 0 0 0 0 17 1 0 0
/proc/5580/statm: 2875 2609 64 8 0 2547 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 11500

Child status: 0
Real time (s): 0.981266
CPU time (s): 0.97785
CPU user time (s): 0.962853
CPU system time (s): 0.014997
CPU usage (%): 99.6519
Max. virtual memory (cumulated for all children) (KiB): 18496

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

runsolver used 0.000999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node24 on Tue Jan 16 20:39:13 UTC 2007


IDJOB= 268855
IDBENCH= 5478
IDSOLVER= 90
FILE ID= node24/268855-1168979942

PBS_JOBID= 3566278

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/jobShop/jobShop-e0ddr2/e0ddr2-10-by-5-10.xml
COMMAND LINE= /tmp/evaluation/268855-1168979942/VALCSP /tmp/evaluation/268855-1168979942/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-268855-1168979942 -o ROOT/results/node24/solver-268855-1168979942 -C 1800 -M 900  /tmp/evaluation/268855-1168979942/VALCSP /tmp/evaluation/268855-1168979942/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  cd420abf4fa5344f1217005e29afc0b6

RANDOM SEED= 215716961

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.234
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.234
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:       1364680 kB
Buffers:         53996 kB
Cached:         504080 kB
SwapCached:          0 kB
Active:         125652 kB
Inactive:       489788 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1364680 kB
SwapTotal:     4192956 kB
SwapFree:      4192800 kB
Dirty:             428 kB
Writeback:           0 kB
Mapped:          76340 kB
Slab:            60800 kB
Committed_AS:  4928504 kB
PageTables:       2196 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= 66564 MiB



End job on node24 on Tue Jan 16 20:39:26 UTC 2007