Trace number 268696

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 1.01684 1.03691

DiagnosticValue
CHECKS2220920
NODES50

General information on the benchmark

NamejobShop/jobShop-ewddr2/
ewddr2-10-by-5-2.xml
MD5SUM73130d269177845cbb8ba266629965f4
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.036993
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size151
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.01	s SATISFIABLE
1.01	v 0 78 127 135 176 37 43 85 93 105 62 70 102 115 160 29 53 93 102 115 21 27 42 57 66 70 80 115 127 144 4 43 57 69 129 0 4 12 32 43 15 27 69 85 96 12 21 29 54 77 
1.01	d CHECKS 2.22092e+06
1.01	d NODES 50

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/node63/watcher-268696-1168979749 -o ROOT/results/node63/solver-268696-1168979749 -C 1800 -M 900 /tmp/evaluation/268696-1168979749/VALCSP /tmp/evaluation/268696-1168979749/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: 1.35 1.57 1.18 4/68 8284
/proc/meminfo: memFree=1843568/2055920 swapFree=4192812/4192956
[pid=8283] ppid=8281 vsize=1732 CPUtime=0
/proc/8283/stat : 8283 (VALCSP) R 8281 8283 8053 0 -1 4194304 176 0 0 0 0 0 0 0 18 0 1 0 45473546 1773568 154 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529344 0 0 4096 0 0 0 0 17 1 0 0
/proc/8283/statm: 433 154 64 8 0 105 0

[startup+0.104061 s]
/proc/loadavg: 1.35 1.57 1.18 4/68 8284
/proc/meminfo: memFree=1843568/2055920 swapFree=4192812/4192956
[pid=8283] ppid=8281 vsize=4240 CPUtime=0.09
/proc/8283/stat : 8283 (VALCSP) R 8281 8283 8053 0 -1 4194304 805 0 0 0 9 0 0 0 18 0 1 0 45473546 4341760 783 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529355 0 0 4096 0 0 0 0 17 1 0 0
/proc/8283/statm: 1060 783 64 8 0 732 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4240

[startup+0.512103 s]
/proc/loadavg: 1.35 1.57 1.18 4/68 8284
/proc/meminfo: memFree=1843568/2055920 swapFree=4192812/4192956
[pid=8283] ppid=8281 vsize=11236 CPUtime=0.5
/proc/8283/stat : 8283 (VALCSP) R 8281 8283 8053 0 -1 4194304 2574 0 0 0 50 0 0 0 21 0 1 0 45473546 11505664 2552 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528612 0 0 4096 0 0 0 0 17 1 0 0
/proc/8283/statm: 2809 2552 64 8 0 2481 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 11236

Child status: 0
Real time (s): 1.03691
CPU time (s): 1.01684
CPU user time (s): 0.997848
CPU system time (s): 0.018997
CPU usage (%): 98.0645
Max. virtual memory (cumulated for all children) (KiB): 18496

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node63 on Tue Jan 16 20:35:56 UTC 2007


IDJOB= 268696
IDBENCH= 5255
IDSOLVER= 90
FILE ID= node63/268696-1168979749

PBS_JOBID= 3566237

Free space on /tmp= 66561 MiB

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

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  73130d269177845cbb8ba266629965f4

RANDOM SEED= 873348950

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.216
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.216
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:       1840648 kB
Buffers:          2116 kB
Cached:         137004 kB
SwapCached:        144 kB
Active:          38484 kB
Inactive:       121004 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1840648 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             212 kB
Writeback:           0 kB
Mapped:          30448 kB
Slab:            41368 kB
Committed_AS:   426260 kB
PageTables:       1764 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= 66565 MiB



End job on node63 on Tue Jan 16 20:36:08 UTC 2007