Skip to content

Conversation

@danielsn
Copy link
Contributor

Description of changes:

Currently, we rely on the default toolchain on the machine. If its too old, that causes problems like here: https://github.com/aws/s2n-quic/actions/runs/3347681915/jobs/5545938616

Resolved issues:

Resolves #ISSUE-NUMBER

Related RFC:

Optional #ISSUE-NUMBER.

Call-outs:

Testing:

  • How is this change tested?

  • Is this a refactor change?

Checklist

  • Each commit message has a non-empty body, explaining why the change was made
  • Methods or procedures are documented
  • Regression or unit tests are included, or existing tests cover the modified code
  • My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Copy link
Contributor

@celinval celinval left a comment

Choose a reason for hiding this comment

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

I am wondering if we can just download the kani toolchain file that specify the toolchain we use to avoid installing 2 different toolchains.

@danielsn
Copy link
Contributor Author

For now I manually put it in to the script. Making this autopull from the release toolchain would be a nice improvement, I'll file a ticket for that

@danielsn
Copy link
Contributor Author

#9

@danielsn danielsn merged commit e68870a into model-checking:main Oct 28, 2022
@danielsn danielsn deleted the install-toolchain branch October 28, 2022 19:55
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.

2 participants