Trace number 247669

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
rjw-solver 2006-12-09Wrong Cert. 0.6549 0.657776

DiagnosticValue
CHECKS287586
NODES33

General information on the benchmark

Namelangford/
langford-3-11-ext.xml
MD5SUMf047fc038009e372113925ae5ca60f88
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 benchmark1.69774
SatisfiableNO
(Un)Satisfiability was proved
Number of variables33
Number of constraints550
Maximum constraint arity2
Maximum domain size33
Number of constraints which are defined in extension550
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.65	v 4 1 3 5 6 7 8 9 10 11 12 2 13 14 15 16 17 18 19 20 21 22 0 23 24 25 26 27 28 29 30 31 32 
0.65	s SATISFIABLE
0.65	d NODES 33
0.65	d CHECKS 287586
c 
c 
c 
c conversion script
c 
c

Verifier Data (download as text)

ERROR: relation in constraint C0 is not satisfied
parm[0]=13
parm[1]=1
Relation contains support tuples
Relation contains (3,0)(4,1)(5,2)(6,3)(7,4)(8,5)(9,6)(10,7)(11,8)(12,9)(13,10)(14,11)(15,12)(16,13)(17,14)(18,15)(19,16)(20,17)(21,18)(22,19)(23,20)(24,21)(25,22)(26,23)(27,24)(28,25)(29,26)(30,27)(31,28)(32,29)

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node14/watcher-247669-1168383426 -o ROOT/results/node14/solver-247669-1168383426 -C 1800 -M 900 /tmp/evaluation/247669-1168383426/solve /tmp/evaluation/247669-1168383426/unknown 1800 

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.46 0.77 0.90 4/81 12581
/proc/meminfo: memFree=1734488/2055920 swapFree=4158768/4192956
[pid=12580] ppid=12578 vsize=5352 CPUtime=0
/proc/12580/stat : 12580 (solve) R 12578 12580 10917 0 -1 4194304 283 174 0 0 0 0 0 0 18 0 1 0 186737814 5480448 229 18446744073709551615 4194304 4889804 548682069344 18446744073709551615 212234463903 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/12580/statm: 1338 229 192 169 0 49 0

[startup+0.102725 s]
/proc/loadavg: 0.46 0.77 0.90 4/81 12581
/proc/meminfo: memFree=1734488/2055920 swapFree=4158768/4192956
[pid=12580] ppid=12578 vsize=5352 CPUtime=0
/proc/12580/stat : 12580 (solve) S 12578 12580 10917 0 -1 4194304 315 174 0 0 0 0 0 0 18 0 1 0 186737814 5480448 229 18446744073709551615 4194304 4889804 548682069344 18446744073709551615 212234462020 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/12580/statm: 1338 229 192 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.510761 s]
/proc/loadavg: 0.46 0.77 0.90 4/81 12581
/proc/meminfo: memFree=1734488/2055920 swapFree=4158768/4192956
[pid=12580] ppid=12578 vsize=5352 CPUtime=0
/proc/12580/stat : 12580 (solve) S 12578 12580 10917 0 -1 4194304 315 174 0 0 0 0 0 0 18 0 1 0 186737814 5480448 229 18446744073709551615 4194304 4889804 548682069344 18446744073709551615 212234462020 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/12580/statm: 1338 229 192 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.657776
CPU time (s): 0.6549
CPU user time (s): 0.643902
CPU system time (s): 0.010998
CPU usage (%): 99.5628
Max. virtual memory (cumulated for all children) (KiB): 5352

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

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node14 on Tue Jan  9 22:57:08 UTC 2007


IDJOB= 247669
IDBENCH= 11649
FILE ID= node14/247669-1168383426

PBS_JOBID= 3522496

Free space on /tmp= 66552 MiB

BENCH NAME= HOME/pub/bench/CPAI06/langford/langford-3-11-ext.xml
COMMAND LINE= /tmp/evaluation/247669-1168383426/solve /tmp/evaluation/247669-1168383426/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node14/convwatcher-247669-1168383426 -o ROOT/results/node14/conversion-247669-1168383426 -C 600 -M 900 /tmp/evaluation/247669-1168383426/conversion /tmp/evaluation/247669-1168383426/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-247669-1168383426 -o ROOT/results/node14/solver-247669-1168383426 -C 1800 -M 900  /tmp/evaluation/247669-1168383426/solve /tmp/evaluation/247669-1168383426/unknown 1800

META MD5SUM SOLVER= 91bbaf997669a18b91ccd2f734d8d9ca
MD5SUM BENCH=  f047fc038009e372113925ae5ca60f88

RANDOM SEED= 780143199

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.227
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.227
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:       1734968 kB
Buffers:         49884 kB
Cached:         185964 kB
SwapCached:       3240 kB
Active:         158200 kB
Inactive:       106424 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1734968 kB
SwapTotal:     4192956 kB
SwapFree:      4158768 kB
Dirty:           11300 kB
Writeback:           0 kB
Mapped:          35520 kB
Slab:            41556 kB
Committed_AS:  6660160 kB
PageTables:       2016 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= 66552 MiB



End job on node14 on Tue Jan  9 22:57:11 UTC 2007