Trace number 238008

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
sugar 0.40? 1.27 2.06607

General information on the benchmark

Namehaystacks/
haystacks_30.xml
MD5SUMd19752845e2bb544181045abea63b2d0
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 benchmark63.7613
SatisfiableNO
(Un)Satisfiability was proved
Number of variables900
Number of constraints13079
Maximum constraint arity2
Maximum domain size30
Number of constraints which are defined in extension0
Number of constraints which are defined in intension13079
Global constraints used (with number of constraints)

Solver Data (download as text)

0.05	c # Sugar v0-40 (/tmp/evaluation/238008-1170108592/sugar-v0-40.jar)
0.05	
0.05	c # MAIN  BEGIN : /tmp/evaluation/238008-1170108592/unknown.xml [Mon Jan 29 23:09:55 2007]
0.05	c # CONVERT_XML  BEGIN : /tmp/evaluation/238008-1170108592/unknown.xml /tmp/evaluation/238008-1170108592/sugar1272.csp [Mon Jan 29 23:09:55 2007]
0.05	c # CMD : java -Xms200M -Xmx600M -jar /tmp/evaluation/238008-1170108592/sugar-v0-40.jar -convert /tmp/evaluation/238008-1170108592/unknown.xml /tmp/evaluation/238008-1170108592/sugar1272.csp
0.17	c BEGIN convert /tmp/evaluation/238008-1170108592/unknown.xml
1.29	c END convert (1.121839 seconds)
1.33	c # CONVERT_XML  END : /tmp/evaluation/238008-1170108592/sugar1272.csp 383891 bytes (1 seconds) [Mon Jan 29 23:09:56 2007]
1.33	c # CONVERT_XML  CPU : 0 = 0 + 0 + 0 + 0
1.33	
1.33	c # GENERATE_SAT  BEGIN : /tmp/evaluation/238008-1170108592/sugar1272.bcnf [Mon Jan 29 23:09:56 2007]
1.33	c # CMD : java -Xms200M -Xmx600M -jar /tmp/evaluation/238008-1170108592/sugar-v0-40.jar -bcnf -map /tmp/evaluation/238008-1170108592/sugar1272.map /tmp/evaluation/238008-1170108592/sugar1272.csp /tmp/evaluation/238008-1170108592/sugar1272.bcnf
1.45	c BEGIN parse /tmp/evaluation/238008-1170108592/sugar1272.csp
2.01	c jp.ac.kobe_u.cs.sugar.SugarException: mul(sub(V352, V420), sub(V420, V352)) is not coef linear expression
2.01	c 	at jp.ac.kobe_u.cs.sugar.LinearExpression.toLinearExpression(LinearExpression.java:97)
2.01	c 	at jp.ac.kobe_u.cs.sugar.LinearExpression.toLinearExpression(LinearExpression.java:77)
2.01	c 	at jp.ac.kobe_u.cs.sugar.LinearExpression.toLinearExpression(LinearExpression.java:80)
2.01	c 	at jp.ac.kobe_u.cs.sugar.LinearExpression.(LinearExpression.java:56)
2.01	c 	at jp.ac.kobe_u.cs.sugar.CSPParser.parseLE(CSPParser.java:312)
2.01	c 	at jp.ac.kobe_u.cs.sugar.CSPParser.parseComparison(CSPParser.java:386)
2.01	c 	at jp.ac.kobe_u.cs.sugar.CSPParser.parse(CSPParser.java:469)
2.01	c 	at jp.ac.kobe_u.cs.sugar.CSPParser.parse(CSPParser.java:541)
2.01	c 	at jp.ac.kobe_u.cs.sugar.CSPParser.parse(CSPParser.java:568)
2.01	c 	at jp.ac.kobe_u.cs.sugar.CSPParser.parse(CSPParser.java:586)
2.01	c 	at jp.ac.kobe_u.cs.sugar.CSPParser.parse(CSPParser.java:600)
2.01	c 	at jp.ac.kobe_u.cs.sugar.Sugar.encode(Sugar.java:187)
2.01	c 	at jp.ac.kobe_u.cs.sugar.Sugar.execute(Sugar.java:435)
2.01	c 	at jp.ac.kobe_u.cs.sugar.Sugar.main(Sugar.java:451)
2.05	s UNKNOWN
2.05	c # ERROR /tmp/evaluation/238008-1170108592/sugar1272.bcnf is not generated, at /tmp/evaluation/238008-1170108592/sugar line 310.
2.05	
2.05	c # MAIN  END :  (2 seconds) [Mon Jan 29 23:09:57 2007]
2.05	c # MAIN  CPU : 0.67 = 0 + 0 + 0.62 + 0.05
2.05

Verifier Data (download as text)

ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer: UNKNOWN

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node10/watcher-238008-1170108592 -o ROOT/results/node10/solver-238008-1170108592 -C 1800 -M 900 /tmp/evaluation/238008-1170108592/solver /tmp/evaluation/238008-1170108592 /tmp/evaluation/238008-1170108592/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.62 1.91 2.06 5/87 1273
/proc/meminfo: memFree=1393872/2055920 swapFree=4192812/4192956
[pid=1272] ppid=1270 vsize=18540 CPUtime=0
/proc/1272/stat : 1272 (runsolver) R 1270 1272 1207 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 30814516 18984960 279 18446744073709551615 4194304 4267372 548682069040 18446744073709551615 214919867687 0 0 4096 24578 0 0 0 17 1 0 0
/proc/1272/statm: 4635 279 244 17 0 2626 0

[startup+0.109812 s]
/proc/loadavg: 1.62 1.91 2.06 5/87 1273
/proc/meminfo: memFree=1393872/2055920 swapFree=4192812/4192956
[pid=1272] ppid=1270 vsize=13724 CPUtime=0.04
/proc/1272/stat : 1272 (sugar) S 1270 1272 1207 0 -1 4194304 1112 0 0 0 3 1 0 0 20 0 1 0 30814516 14053376 805 18446744073709551615 4194304 4206940 548682069232 18446744073709551615 214928765026 0 0 4224 16386 18446744071563648864 0 0 17 1 0 0
/proc/1272/statm: 3431 805 368 3 0 531 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 13724

[startup+0.517863 s]
/proc/loadavg: 1.62 1.91 2.06 5/87 1273
/proc/meminfo: memFree=1393872/2055920 swapFree=4192812/4192956
[pid=1272] ppid=1270 vsize=13724 CPUtime=0.04
/proc/1272/stat : 1272 (sugar) S 1270 1272 1207 0 -1 4194304 1121 0 0 0 3 1 0 0 15 0 1 0 30814516 14053376 805 18446744073709551615 4194304 4206940 548682069232 18446744073709551615 214928765026 0 0 4224 16386 18446744071563648864 0 0 17 1 0 0
/proc/1272/statm: 3431 805 368 3 0 531 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 13724

[startup+1.33997 s]
/proc/loadavg: 1.65 1.91 2.06 4/95 1281
/proc/meminfo: memFree=1351120/2055920 swapFree=4192812/4192956
[pid=1272] ppid=1270 vsize=13724 CPUtime=0.04
/proc/1272/stat : 1272 (sugar) S 1270 1272 1207 0 -1 4194304 1178 0 0 0 3 1 0 0 16 0 1 0 30814516 14053376 808 18446744073709551615 4194304 4206940 548682069232 18446744073709551615 214928765026 0 0 4224 16386 18446744071563648864 0 0 17 1 0 0
/proc/1272/statm: 3431 808 370 3 0 531 0
[pid=1274] ppid=1272 vsize=0 CPUtime=1.23
/proc/1274/stat : 1274 (java) Z 1272 1272 1207 0 -1 1036 12450 0 1 0 114 9 0 0 16 0 1 0 30814521 0 0 18446744073709551615 0 0 0 0 0 0 4 0 23759 18446744071563351923 0 0 17 1 0 0
/proc/1274/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 1.27
Current children cumulated vsize (KiB) 13724

Child status: 1

!!! problem with CPU time !!!
wait4(...,&childrusage) returns 1272 and gives childrusage.ru_utime.tv_sec=0 childrusage.ru_utime.tv_usec=658899 childrusage.ru_stime.tv_sec=0 childrusage.ru_stime.tv_usec=71989
CPU time returned by wait4() is 0.730888
while last known CPU time is 1.27

Solver probably didn't/couldn't wait for its children
Using last known CPU time as value...

Real time (s): 2.06607
CPU time (s): 1.27
CPU user time (s): 1.17
CPU system time (s): 0.1
CPU usage (%): 61.4695
Max. virtual memory (cumulated for all children) (KiB): 821124

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.658899
system time used= 0.071989
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9165
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 342
involuntary context switches= 316

runsolver used 0.002999 s user time and 0.012998 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Mon Jan 29 22:09:53 UTC 2007


IDJOB= 238008
IDBENCH= 6976
IDSOLVER= 86
FILE ID= node10/238008-1170108592

PBS_JOBID= 3689957

Free space on /tmp= 66445 MiB

SOLVER NAME= sugar 0.40
BENCH NAME= HOME/pub/bench/CPAI06/haystacks/haystacks_30.xml
COMMAND LINE= /tmp/evaluation/238008-1170108592/solver /tmp/evaluation/238008-1170108592 /tmp/evaluation/238008-1170108592/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-238008-1170108592 -o ROOT/results/node10/solver-238008-1170108592 -C 1800 -M 900  /tmp/evaluation/238008-1170108592/solver /tmp/evaluation/238008-1170108592 /tmp/evaluation/238008-1170108592/unknown.xml

META MD5SUM SOLVER= 0a27e717dfe98d83d9802fe0eea45073
MD5SUM BENCH=  d19752845e2bb544181045abea63b2d0

RANDOM SEED= 3140250

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.232
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.232
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:       1394288 kB
Buffers:         41940 kB
Cached:         188920 kB
SwapCached:          0 kB
Active:         536692 kB
Inactive:        67020 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1394288 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2540 kB
Writeback:           0 kB
Mapped:         392576 kB
Slab:            42052 kB
Committed_AS:  1152376 kB
PageTables:       2836 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= 66445 MiB



End job on node10 on Mon Jan 29 22:09:57 UTC 2007