Trace number 2074080

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
pcs-restart 0.3.2UNSAT 0.410937 0.420118

DiagnosticValue
ASSIGNMENTS391

General information on the benchmark

Namecsp/os-taillard-5/
normalized-os-taillard-5-95-5.xml
MD5SUM75da09c50b4fcbd9ca6ba4fc2e0eb147
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.015997
Satisfiable
(Un)Satisfiability was proved
Number of variables25
Number of constraints100
Maximum constraint arity2
Maximum domain size293
Number of constraints which are defined in extension0
Number of constraints which are defined in intension100
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c has big domains
0.00/0.01	c big-domain mode
0.00/0.02	c Seed is 1584613364
0.00/0.02	c Constructing HOME/instance-2074080-1247712273.xml  with 700 constraints
0.00/0.03	c Solving 391 backtracks 6 restarts
0.38/0.41	s UNSATISFIABLE
0.38/0.41	d ASSIGNMENTS 391

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2074080-1247712273/watcher-2074080-1247712273 -o /tmp/evaluation-result-2074080-1247712273/solver-2074080-1247712273 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1584613364 HOME/instance-2074080-1247712273.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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


[startup+0 s]
/proc/loadavg: 1.83 1.95 1.98 4/81 12103
/proc/meminfo: memFree=1246968/2055920 swapFree=4192812/4192956
[pid=12103] ppid=12101 vsize=5356 CPUtime=0
/proc/12103/stat : 12103 (pcssolve) R 12101 12103 11570 0 -1 4194304 290 0 0 0 0 0 0 0 25 0 1 0 58294107 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 237788261023 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/12103/statm: 1339 241 200 169 0 50 0
[pid=12104] ppid=12103 vsize=3676 CPUtime=0
/proc/12104/stat : 12104 (fgrep) R 12103 12103 11570 0 -1 4194304 143 0 0 0 0 0 0 0 25 0 1 0 58294108 3764224 110 996147200 4194304 4274172 548682068976 18446744073709551615 237788430418 0 0 4096 0 0 0 0 17 1 0 0
/proc/12104/statm: 919 110 86 19 0 43 0
[pid=12105] ppid=12103 vsize=5356 CPUtime=0
/proc/12105/stat : 12105 (pcssolve) R 12103 12103 11570 0 -1 4194368 0 0 0 0 0 0 0 0 25 0 1 0 58294108 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 237788261023 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/12105/statm: 1339 241 200 169 0 50 0

[startup+0.0349241 s]
/proc/loadavg: 1.83 1.95 1.98 4/81 12103
/proc/meminfo: memFree=1246968/2055920 swapFree=4192812/4192956
[pid=12103] ppid=12101 vsize=4796 CPUtime=0.01
/proc/12103/stat : 12103 (pcs.big) R 12101 12103 11570 0 -1 4194304 910 649 0 0 1 0 0 0 25 0 1 0 58294107 4911104 541 996147200 134512640 135215973 4294956304 18446744073709551615 3039968 0 0 4096 0 0 0 0 17 1 0 0
/proc/12103/statm: 1199 541 403 171 0 124 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 4796

[startup+0.102937 s]
/proc/loadavg: 1.83 1.95 1.98 4/81 12103
/proc/meminfo: memFree=1246968/2055920 swapFree=4192812/4192956
[pid=12103] ppid=12101 vsize=5096 CPUtime=0.08
/proc/12103/stat : 12103 (pcs.big) R 12101 12103 11570 0 -1 4194304 952 649 0 0 8 0 0 0 25 0 1 0 58294107 5218304 583 996147200 134512640 135215973 4294956304 18446744073709551615 134590644 0 0 4096 0 0 0 0 17 1 0 0
/proc/12103/statm: 1274 583 406 171 0 199 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5096

[startup+0.302975 s]
/proc/loadavg: 1.83 1.95 1.98 4/81 12103
/proc/meminfo: memFree=1246968/2055920 swapFree=4192812/4192956
[pid=12103] ppid=12101 vsize=5352 CPUtime=0.28
/proc/12103/stat : 12103 (pcs.big) R 12101 12103 11570 0 -1 4194304 1034 649 0 0 28 0 0 0 25 0 1 0 58294107 5480448 665 996147200 134512640 135215973 4294956304 18446744073709551615 4158960027 0 0 4096 0 0 0 0 17 1 0 0
/proc/12103/statm: 1338 665 406 171 0 263 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 5352

Solver just ended. Dumping a history of the last processes samples

[startup+0.402993 s]
/proc/loadavg: 1.83 1.95 1.98 4/81 12103
/proc/meminfo: memFree=1246968/2055920 swapFree=4192812/4192956
[pid=12103] ppid=12101 vsize=5612 CPUtime=0.38
/proc/12103/stat : 12103 (pcs.big) R 12101 12103 11570 0 -1 4194304 1077 649 0 0 38 0 0 0 25 0 1 0 58294107 5746688 708 996147200 134512640 135215973 4294956304 18446744073709551615 3038760 0 0 4096 0 0 0 0 17 1 0 0
/proc/12103/statm: 1403 708 406 171 0 328 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 5612

Child status: 0
Real time (s): 0.420118
CPU time (s): 0.410937
CPU user time (s): 0.398939
CPU system time (s): 0.011998
CPU usage (%): 97.8147
Max. virtual memory (cumulated for all children) (KiB): 5612

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.398939
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1737
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= 18
involuntary context switches= 36

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node24 at 2009-07-16 04:44:33
IDJOB=2074080
IDBENCH=56052
IDSOLVER=734
FILE ID=node24/2074080-1247712273
PBS_JOBID= 9521478
Free space on /tmp= 66412 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/os-taillard-5/normalized-os-taillard-5-95-5.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2074080-1247712273/watcher-2074080-1247712273 -o /tmp/evaluation-result-2074080-1247712273/solver-2074080-1247712273 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1584613364 HOME/instance-2074080-1247712273.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 75da09c50b4fcbd9ca6ba4fc2e0eb147
RANDOM SEED=1584613364

node24.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.287
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.287
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:       1247448 kB
Buffers:         88024 kB
Cached:         519692 kB
SwapCached:          0 kB
Active:         293292 kB
Inactive:       424832 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1247448 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1892 kB
Writeback:           0 kB
Mapped:         130748 kB
Slab:            75224 kB
Committed_AS:   712928 kB
PageTables:       2084 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= 66408 MiB
End job on node24 at 2009-07-16 04:44:33