Trace number 1083674

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
Mistral-prime 1.313SAT 0.067988 0.0755541

DiagnosticValue
ASSIGNMENTS98
CHECKS2019

General information on the benchmark

Namecsp/rlfapScensMod/
normalized-scen6-w1.xml
MD5SUM5fcf1b567ccbc0fe4804b04f5a0a591b
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.067988
Satisfiable
(Un)Satisfiability was proved
Number of variables200
Number of constraints319
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension319
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.02	c mistral-prime version 1.313
0.00/0.07	s SATISFIABLE
0.00/0.07	v 16 254 428 666 254 16 16 254 254 16 254 16 652 414 100 338 324 86 16 254 694 456 30 268 680 442 254 16 254 16 708 470 254 16 526 764 652 414 736 498 16 254 652 414 254 16 30 268 254 16 16 254 16 254 16 254 254 16 352 114 254 16 30 268 254 16 254 16 44 282 16 254 324 86 254 16 30 268 512 750 268 30 428 666 16 254 666 428 540 778 268 30 268 30 30 268 30 268 268 30 414 652 764 526 722 484 254 16 708 470 16 254 526 764 764 526 268 30 338 100 30 268 484 722 526 764 268 30 428 666 324 86 750 512 428 666 666 428 268 30 428 666 30 268 268 30 708 470 254 16 16 254 296 58 16 254 456 694 442 680 254 16 86 324 778 540 254 16 268 30 764 526 456 694 428 666 254 16 254 16 324 86 428 666 428 666 268 30 708 470 30 268 666 428 268 30 680 442 30 268
0.00/0.07	d CHECKS 2019
0.00/0.07	d ASSIGNMENTS 98

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.2.5 (c) roussel@cril.univ-artois.fr

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1083674-1215229248/watcher-1083674-1215229248 -o /tmp/evaluation-result-1083674-1215229248/solver-1083674-1215229248 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1083674-1215229248.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): 2200 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.16 2.04 2.01 4/81 4681
/proc/meminfo: memFree=1176392/2055920 swapFree=4180808/4192956
[pid=4681] ppid=4679 vsize=18572 CPUtime=0
/proc/4681/stat : 4681 (runsolver) R 4679 4681 4223 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 2001894586 19017728 292 996147200 4194304 4296836 548682068496 18446744073709551615 257203694887 0 0 4096 24578 0 0 0 17 1 0 0
/proc/4681/statm: 4643 292 257 25 0 2626 0

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

Child status: 0
Real time (s): 0.0755541
CPU time (s): 0.067988
CPU user time (s): 0.05999
CPU system time (s): 0.007998
CPU usage (%): 89.9859
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node65 at 2008-07-05 05:40:48
IDJOB=1083674
IDBENCH=57499
IDSOLVER=358
FILE ID=node65/1083674-1215229248
PBS_JOBID= 7881866
Free space on /tmp= 66492 MiB

SOLVER NAME= Mistral-prime 1.313
BENCH NAME= CPAI08/csp/rlfapScensMod/normalized-scen6-w1.xml
COMMAND LINE= HOME/xsolve BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1083674-1215229248/watcher-1083674-1215229248 -o /tmp/evaluation-result-1083674-1215229248/solver-1083674-1215229248 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1083674-1215229248.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 5fcf1b567ccbc0fe4804b04f5a0a591b
RANDOM SEED=860653455

node65.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.231
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.231
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:       1176872 kB
Buffers:         15052 kB
Cached:         125916 kB
SwapCached:       5980 kB
Active:         741728 kB
Inactive:        82928 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1176872 kB
SwapTotal:     4192956 kB
SwapFree:      4180808 kB
Dirty:            1616 kB
Writeback:           0 kB
Mapped:         699808 kB
Slab:            38116 kB
Committed_AS:  4733952 kB
PageTables:       3216 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= 66492 MiB
End job on node65 at 2008-07-05 05:40:48