Skip to content
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

introduce mcs-devel.xml #20

Merged
merged 4 commits into from
Jul 18, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,19 @@ The manifest files stored here come in three categories:
of the seL4 code and proof repositories. It is updated automatically by CI jobs.
It points to specific revision hashes, and should generally not be modified manually.

- development manifests such as `devel.xml` and `mcs.xml`: these are for proof
development and typically point to branch names of the verification
- `mcs.xml`: this manifest stores the latest tested-as-working combination of
the seL4 code and proof repositories for the MCS proofs (the `rt` branch in
the `l4v` repository). It is updated automatically by CI jobs. It points to
specific revision hashes, and should generally not be modified manually.

- development manifests such as `devel.xml` and `mcs-devel.xml`: these are for
proof development and typically point to branch names of the verification
repositories in combination with a fixed revision hash of the seL4 code
repository. The seL4 revision in `devel.xml` is updated automatically by CI
jobs for code changes in seL4 that are not visible to the proofs. It should be
updated manually or using the [version bump][] script whenever proofs are
updated in sync with the code. This will then trigger a CI run and, if
successful, a corresponding update in `default.xml`.
repository. The seL4 revision in `devel.xml` and `mcs-devel.xml` is updated
automatically by CI jobs for code changes in seL4 that are not visible to the
proofs. It should be updated manually or using the [version bump][] script
whenever proofs are updated in sync with the code. This will then trigger a CI
run and, if successful, a corresponding update in `default.xml` or `mcs.xml`.

- release version manifests such as `12.0.0.xml`: these store the repository
version configuration for official releases of seL4. Use these to check proofs
Expand Down
16 changes: 16 additions & 0 deletions mcs-devel.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2021, Data61, CSIRO
SPDX-License-Identifier: BSD-2-Clause
-->
<manifest>
<remote name="verification" fetch="."/>
<default remote="verification" revision="master"/>

<project name="HOL" path="HOL4" revision="successful-decompile" />
<project name="graph-refine" />
<project name="isabelle" revision="ts-2024" />
<project name="l4v" revision="rt" />
<project name="polyml" path="HOL4/polyml" revision="successful-decompile"/>
<project name="seL4" revision="3c2c5ba18a87371bb289d1cc0ff561ae61d008db"/>
</manifest>