Trace number 1097937

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
spider 2008-06-14UNSAT 0.100983 0.106936

DiagnosticValue
ASSIGNMENTS7
CHECKS4342

General information on the benchmark

Namecsp/composed-75-1-40/
normalized-composed-75-1-40-5_ext.xml
MD5SUMcda0453d2dc2adf7f01e5f798439ac6b
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.048992
Satisfiable
(Un)Satisfiability was proved
Number of variables83
Number of constraints662
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension662
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.09/0.10	s UNSATISFIABLE
0.09/0.10	d CHECKS 4342
0.09/0.10	d ASSIGNMENTS 7

Verifier Data (download as text)

No possible verification on an UNSAT instance

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-1097937-1215282951/watcher-1097937-1215282951 -o /tmp/evaluation-result-1097937-1215282951/solver-1097937-1215282951 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/run -c HOME/instance-1097937-1215282951.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: 1.98 2.00 2.00 4/84 23793
/proc/meminfo: memFree=1616504/2055920 swapFree=4180444/4192956
[pid=23793] ppid=23791 vsize=18572 CPUtime=0
/proc/23793/stat : 23793 (runsolver) R 23791 23793 21491 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 2007264711 19017728 292 996147200 4194304 4296836 548682068480 18446744073709551615 213112122663 0 0 4096 24578 0 0 0 17 1 0 0
/proc/23793/statm: 4643 292 257 25 0 2626 0

[startup+0.0896721 s]
/proc/loadavg: 1.98 2.00 2.00 4/84 23793
/proc/meminfo: memFree=1616504/2055920 swapFree=4180444/4192956
[pid=23793] ppid=23791 vsize=7808 CPUtime=0.08
/proc/23793/stat : 23793 (ld-linux.so.2) R 23791 23793 21491 0 -1 4194304 1564 0 0 0 7 1 0 0 18 0 1 0 2007264711 7995392 1295 996147200 1448431616 1448550632 4294956272 18446744073709551615 134541609 0 0 4096 0 0 0 0 17 1 0 0
/proc/23793/statm: 1952 1295 341 29 0 942 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 7808

[startup+0.101662 s]
/proc/loadavg: 1.98 2.00 2.00 4/84 23793
/proc/meminfo: memFree=1616504/2055920 swapFree=4180444/4192956
[pid=23793] ppid=23791 vsize=7948 CPUtime=0.09
/proc/23793/stat : 23793 (ld-linux.so.2) R 23791 23793 21491 0 -1 4194304 1582 0 0 0 8 1 0 0 18 0 1 0 2007264711 8138752 1313 996147200 1448431616 1448550632 4294956272 18446744073709551615 134546342 0 0 4096 0 0 0 0 17 1 0 0
/proc/23793/statm: 1987 1313 342 29 0 977 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7948

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

Child status: 0
Real time (s): 0.106936
CPU time (s): 0.100983
CPU user time (s): 0.086986
CPU system time (s): 0.013997
CPU usage (%): 94.433
Max. virtual memory (cumulated for all children) (KiB): 7948

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

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node68 at 2008-07-05 20:35:51
IDJOB=1097937
IDBENCH=59583
IDSOLVER=328
FILE ID=node68/1097937-1215282951
PBS_JOBID= 7882296
Free space on /tmp= 66528 MiB

SOLVER NAME= spider 2008-06-14
BENCH NAME= CPAI08/csp/composed-75-1-40/normalized-composed-75-1-40-5_ext.xml
COMMAND LINE= HOME/run -c BENCHNAME
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1097937-1215282951/watcher-1097937-1215282951 -o /tmp/evaluation-result-1097937-1215282951/solver-1097937-1215282951 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/run -c HOME/instance-1097937-1215282951.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= cda0453d2dc2adf7f01e5f798439ac6b
RANDOM SEED=950850963

node68.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.261
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.261
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:       1616984 kB
Buffers:         55112 kB
Cached:         220452 kB
SwapCached:       6772 kB
Active:         260268 kB
Inactive:       124500 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1616984 kB
SwapTotal:     4192956 kB
SwapFree:      4180444 kB
Dirty:            1476 kB
Writeback:           0 kB
Mapped:         119476 kB
Slab:            39396 kB
Committed_AS:  5045404 kB
PageTables:       1912 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= 66524 MiB
End job on node68 at 2008-07-05 20:35:52