Comments (5)
from l4v.
Thanks a lot Thomas!
I was considering changing the names of the files i.e renaming the files, but your suggestion is more appropriate since their sizes were 0. Thus, I removed the files from the log then all three tests worked fine. However, one of the tests which was skipped previously " CRefine" -due to dependency -has failed. The message is below and a small question. I do appreciate your advise on how to fix it!
Note: I had run this "CRefine" test independently before I managed to fix Refine test. So I removed it from the log file as well and then I retested it after the fix, but yet it gives the error 137: " Ignoring duplicate rewrite rule". The error message asks to see the log file -please see the full error message below. Thus, when I use zless CRefine, I can see the error "Ignoring duplicate rewrite rule" associated to some files such as:
file=~/Desktop/verification/l4v/proof/crefine/Arch_C.thy^
~/Desktop/verification/l4v/proof/crefine/Invoke_C.thy
Does this mean that I need to remove/rename crefine from proof directory as well- then retest? It seems like the proofs are corrupted maybe following the first independent building for CRefine? Or does the new sel4 modifications on CRfeine e.g on " Refine_c.thy" led to this? I have seen a comment for example on Refine_c.thy states that ;
" New testfile for graph-refine export with new handling code. Also
some slight tweaks to some CRefine proofs that will be needed to
remove DONT_TRANSLATE markers from certain key places in the seL4
code. These proofs are also compatible with previous seL4."
Again, I will appreciate your advise!
Thanks in advance.
Error 137:
CRefine: theory Refine_C
/home/ssrgv/Desktop/verification/isabelle/lib/scripts/run-polyml-5.6: line 100: 28276 Killed "$POLY" -q -i $ML_OPTIONS
CRefine FAILED
(see also /home/ssrgv/.isabelle/heaps-ARM-home-ssrgv-Desktop-verification-isabelle/polyml-5.6_x86_64-linux/log/CRefine)
theory "Refine_C"
53.794s elapsed time, 179.736s cpu time, 52.884s GC time
Ignoring duplicate rewrite rule:
seL4_NonArchObjectTypeCount <equiv> 5
Ignoring duplicate rewrite rule:
ccorres_underlying ?sr1 ?<Gamma>1 ?r1 ?xf1 ?arrel1 ?axf1 ?P1 ?P'1 ?hs1
(liftM ?t1 ?f1) ?g1 <equiv>
ccorres_underlying ?sr1 ?<Gamma>1 (?r1 <circ> ?t1) ?xf1
(?arrel1 <circ> ?t1) ?axf1 ?P1 ?P'1 ?hs1 ?f1 ?g1
Bad Simplifier context: renamed bound variable ":001" to ":001a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":000" to ":000a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":000" to ":000a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":001" to ":001a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":000" to ":000a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":000" to ":000a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":000" to ":000a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":000" to ":000a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Bad Simplifier context: renamed bound variable ":001" to ":001a" (line 2786 of "~/Desktop/verification/l4v/proof/crefine/Retype_C.thy")
Ignoring duplicate rewrite rule:
objBits ?v <equiv> objBitsKO (injectKO ?v)
Unfinished session(s): CRefine
Finished at Wed Dec 21 00:29:28 EST 2016
0:20:48 elapsed time, 1:08:42 cpu time, factor 3.30
../misc/isa-common.mk:48: recipe for target 'CRefine' failed
make: *** [CRefine] Error 137
40/43 tests succeeded.
Another two tests were skipped due to dependency.
from l4v.
Interesting, the log file seems to have only warnings, no errors, and it looks like the proof part actually finished successfully (theory "Refine_C"'/53.794s elapsed time, 179.736s cpu time, 52.884s GC time).
It's possible that there was not enough RAM for polyml to prepare the image that is written to disk in the end. RAM requirements for CRefine are about 16GB currently, I think. Did the machine have that much available?
from l4v.
Looking at our regression test, CRefine without constrained memory finishes with the following:
CRefine passed ( 0:59:44 real, 3:10:32 cpu, 24.34GB)
This means your run probably did not complete the proof (20:48min elapsed time from the log), but memory might indeed be the problem.
The messages "Ignoring duplicate rewrite rule" and "Bad Simplifier context" are warnings and are expected output in the log file. Would you be able to attach the complete log file?
from l4v.
Thanks a lot for your explanation!
Yes, it seems like a memory issue! I checked the system information, the RAM falls short below 16 G. Its installed physical RAM is 16 G, but its total physical RAM is 15.9 G and the usable RAM is 15.6 G. It seems like a small part of the RAM is preserved to the hardware.
To make sure that this lack of memory was the reason, I ran the system monitor application to observe the traffic while running the test. In deed, the point that the monitor reported ~15.6 G used with 99.7% usage of the RAM corresponded to the point it reached Refine_c in the log file. Then the machine became slow for a short while, then the warning message showed up and then the test stopped as can be seen in the attachments.
For the full log please see the attachments:
test results logs.zip
Thanks so much for the explanations!
from l4v.
Related Issues (20)
- Cleanup post-x64 comments
- Document mysterious useful comments for ctac and ceqv
- SIMPL: don't print `_'proc`
- CI artifact upload uses clashing artifact names
- Methods such as monadic_rewrite_symb_exec_r should warn that discharging side-conditions failed
- Safer vcg in CRefine
- Sub-term to free variable lifting tactic
- Have wp warn when resulting in a goal with a schematic assumption. HOT 15
- Some way of blocking `simp` from unifying schematics HOT 1
- Decide on style for `[def]rule_tac ... [and ...] in ...` HOT 7
- Investigate further use of `none_top/none_bot` in the proofs
- Enhance C Parser to allow named array bounds HOT 3
- Can Isabelle's custom functions and data types be combined with the C-parser?
- take L4V_PLAT into account in rebuilds
- support strongest-postcondition reasoning HOT 1
- Should we reduce DSpec to sys-init operations only? HOT 3
- Faster requalify command for arch-split (`arch_requalify_*`?) HOT 2
- port haskell translator improvements from `rt` to `master`
- Remove or alter use of `stateAssert`
- consolidate definitions of `tcbs_of'`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from l4v.