Trace number 218648

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.13183 1.14757

DiagnosticValue
CHECKS1941640
NODES50

General information on the benchmark

NamejobShop/jobShop-ewddr2/
ewddr2-10-by-5-7.xml
MD5SUM354f4b65140291b23a0e319b036259a3
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.037993
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size153
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.14	s SATISFIABLE
1.14	v 10 16 130 139 144 52 61 139 151 160 46 52 116 130 171 0 16 79 92 111 18 29 39 52 62 10 40 67 79 85 58 85 104 116 124 29 40 52 67 100 0 21 92 104 132 0 10 18 43 46 
1.14	d CHECKS 1.94164e+06
1.14	d NODES 50
1.14

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/node44/watcher-218648-1168253062 -o ROOT/results/node44/solver-218648-1168253062 -C 1800 -M 900 /tmp/evaluation/218648-1168253062/VALCSP /tmp/evaluation/218648-1168253062/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.24 0.58 1.16 5/81 398
/proc/meminfo: memFree=1727304/2055920 swapFree=4191892/4192956
[pid=397] ppid=395 vsize=1600 CPUtime=0
/proc/397/stat : 397 (VALCSP) R 395 397 31863 0 -1 4194304 141 0 0 0 0 0 0 0 20 0 1 0 173705271 1638400 119 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134534240 0 0 4096 0 0 0 0 17 1 0 0
/proc/397/statm: 400 119 62 8 0 72 0

[startup+0.10526 s]
/proc/loadavg: 0.24 0.58 1.16 5/81 398
/proc/meminfo: memFree=1727304/2055920 swapFree=4191892/4192956
[pid=397] ppid=395 vsize=4108 CPUtime=0.09
/proc/397/stat : 397 (VALCSP) R 395 397 31863 0 -1 4194304 780 0 0 0 9 0 0 0 20 0 1 0 173705271 4206592 758 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134531008 0 0 4096 0 0 0 0 17 1 0 0
/proc/397/statm: 1027 758 64 8 0 699 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4108

[startup+0.513298 s]
/proc/loadavg: 0.24 0.58 1.16 5/81 398
/proc/meminfo: memFree=1727304/2055920 swapFree=4191892/4192956
[pid=397] ppid=395 vsize=10972 CPUtime=0.5
/proc/397/stat : 397 (VALCSP) R 395 397 31863 0 -1 4194304 2484 0 0 0 49 1 0 0 24 0 1 0 173705271 11235328 2462 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530975 0 0 4096 0 0 0 0 17 1 0 0
/proc/397/statm: 2743 2462 64 8 0 2415 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 10972

Child status: 0
Real time (s): 1.14757
CPU time (s): 1.13183
CPU user time (s): 1.10483
CPU system time (s): 0.026995
CPU usage (%): 98.6284
Max. virtual memory (cumulated for all children) (KiB): 21004

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.10483
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= 5043
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= 26

runsolver used 0.005999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node44 on Mon Jan  8 10:44:22 UTC 2007


IDJOB= 218648
IDBENCH= 5247
FILE ID= node44/218648-1168253062

PBS_JOBID= 3482007

Free space on /tmp= 66544 MiB

BENCH NAME= HOME/pub/bench/CPAI06/jobShop/jobShop-ewddr2/ewddr2-10-by-5-7.xml
COMMAND LINE= /tmp/evaluation/218648-1168253062/VALCSP /tmp/evaluation/218648-1168253062/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node44/watcher-218648-1168253062 -o ROOT/results/node44/solver-218648-1168253062 -C 1800 -M 900  /tmp/evaluation/218648-1168253062/VALCSP /tmp/evaluation/218648-1168253062/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  354f4b65140291b23a0e319b036259a3

RANDOM SEED= 932214204

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.213
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.213
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:       1727848 kB
Buffers:         35628 kB
Cached:         162628 kB
SwapCached:        304 kB
Active:         163764 kB
Inactive:       108924 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1727848 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            3092 kB
Writeback:           0 kB
Mapped:          92080 kB
Slab:            40532 kB
Committed_AS:  4455868 kB
PageTables:       1964 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= 66544 MiB



End job on node44 on Mon Jan  8 10:44:24 UTC 2007