Skip to content

xen-cbmc: fix ci script #5508

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

Merged
merged 2 commits into from
Sep 30, 2020
Merged

xen-cbmc: fix ci script #5508

merged 2 commits into from
Sep 30, 2020

Conversation

nmanthey
Copy link
Contributor

This script has been broken, and not been picked up in CI until now.

This change fixes the script, as well as makes sure that the relevant
steps are executed, and the resulting build artefacts have the required
goto-cc section in them.

This CI script has been refered to as part of the paper:
"Using model checking tools to triage the severity of security bugs in
the Xen hypervisor", that has been presented at FMCAD 2020.

Signed-off-by: Norbert Manthey nmanthey@amazon.de

  • 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.
  • The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • 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).
  • My commit message includes data points confirming performance improvements (if claimed).
  • 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.

Copy link
Contributor

@NlightNFotis NlightNFotis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix! I would say it's much needed 👍

May I ask why the file was renamed from .yml to .yaml? This has the unfortunate side effect of breaking file revision history, which makes it hard to detect what the actual change here is (the one that actually fixed the broken CI issue).

ln -s goto-cc src/goto-cc/goto-g++

- name: Compile Xen with CBMC via one-line-scan, and check for goto-cc section
run: one-line-scan/one-line-scan --add-to-path $(pwd)/src/cbmc --add-to-path $(pwd)/src/goto-diff --add-to-path $(pwd)/src/goto-cc --no-analysis --trunc-existing --extra-cflags -Wno-error -o CPROVER -j 3 -- make -C xen_4_13 xen -j $(nproc) -k || true

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you split this over multiple lines? This is a bit hard to read.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, will split.

Copy link
Collaborator

@martin-cs martin-cs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean I will stop getting e-mails saying "Run failed: Build and Test Xen" whenever I push to a PR?

Rename the file for consistency with the other files in this directory.

Signed-off-by: Norbert Manthey <nmanthey@amazon.de>
@nmanthey
Copy link
Contributor Author

Thanks for the fix! I would say it's much needed +1

May I ask why the file was renamed from .yml to .yaml? This has the unfortunate side effect of breaking file revision history, which makes it hard to detect what the actual change here is (the one that actually fixed the broken CI issue).

I will split the commit into (1) file rename, and (2) actual diff. The rename is basically for consistency.

Yes, I can split that over multiple lines.

Yes, this fix should stop those PR emails (I hope, I did not push PRs recently ;) )

Copy link
Contributor

@NlightNFotis NlightNFotis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the explanation.

Good to go from me 👍

This script has been broken, and not been picked up in CI until now.

This change fixes the script, as well as makes sure that the relevant
steps are executed, and the resulting build artefacts have the required
goto-cc section in them.

This CI script has been refered to as part of the paper:
"Using model checking tools to triage the severity of security bugs in
the Xen hypervisor", that has been presented at FMCAD 2020.

Signed-off-by: Norbert Manthey <nmanthey@amazon.de>
@codecov
Copy link

codecov bot commented Sep 30, 2020

Codecov Report

Merging #5508 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #5508   +/-   ##
========================================
  Coverage    68.34%   68.34%           
========================================
  Files         1187     1187           
  Lines        98090    98090           
========================================
  Hits         67044    67044           
  Misses       31046    31046           
Flag Coverage Δ
#cproversmt2 42.96% <ø> (ø)
#regression 65.49% <ø> (ø)
#unit 32.25% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3d77d8f...20680de. Read the comment docs.

@NlightNFotis NlightNFotis merged commit 2bc93c2 into diffblue:develop Sep 30, 2020
@tautschnig tautschnig mentioned this pull request Feb 8, 2021
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants