-
Notifications
You must be signed in to change notification settings - Fork 277
Continuous docker #4884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continuous docker #4884
Conversation
nmanthey
commented
Jul 8, 2019
- Each commit message has a non-empty body, explaining why the change was made.
- Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md. (added none)
- The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/ (only change to tooling)
- Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message). (no tests included)
- My PR is restricted to a single feature or bugfix.
- White-space or formatting changes outside the feature-related changed lines are in commits of their own.
This script allows to run commands inside a Docker container easily. The current directory, as well as the home directory are mounted inside the container, and the user id of the calling user is used, or, in case sudo is specified, the root user will be chosen. This way, file write operations inside the container can be visible to the outside, which allows to debug more easily, e.g. build failures.
The existing solution to build Xen did not allow to easily retrieve the build artifacts after the build, not files that allow to work on bug fixes in the tool chain. The new approach builds Xen inside the CBMC tree, so that all files are available afterwards. Note, CBMC is also build within the container, so that the relevant tools can be used inside the container as well.
We are interested in being able to compile the Linux kernel with goto-gcc. To not be required to have all tools available on a local machine, this change provides a docker setup that allows to build the Linux kernel natively, as well as with goto-gcc via the wrapper one-line-scan. Similarly to the Xen tooling, the build files, as well as logs and files for debugging are accessible after the run is complete.
The presented commits allow to compile Xen and the Linux kernel with goto-gcc, which, once fixed, could be useful to make sure changes to goto-gcc to not break these builds. Given these commits, adding more projects should be straight-forward. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR failed Diffblue compatibility checks (cbmc commit: a15047b).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/118337550
Status will be re-evaluated on next push.
Common spurious failures include: the cbmc commit has disappeared in the mean time (e.g. in a force-push); the author is not in the list of contributors (e.g. first-time contributors); compatibility was already broken by an earlier merge.
Codecov Report
@@ Coverage Diff @@
## develop #4884 +/- ##
===========================================
- Coverage 69.09% 69.09% -0.01%
===========================================
Files 1298 1298
Lines 106944 106947 +3
===========================================
+ Hits 73895 73896 +1
- Misses 33049 33051 +2
Continue to review full report at Codecov.
|