ci: add an action to test mirage #8061
Conversation
emillon
changed the title
|
@TheLortex This should correspond to the testing strategy you've showed me before; let me know what you think. (I included |
|
I introduced the cross-compilation regression fixed in 3.8.1 but mirage-www does not seem to trigger the issue. |
|
I updated the test to build caldav instead but still can't repro #7875 unfortunately |
|
I forgot to post an update: I updated this to use the caldav unikernel and was able to reproduce the issue. So it's in a reviewable state now. |
|
@emillon Can you run the action here so we can see it? Or does it not work from PRs? |
|
You can see the previous runs here. |
|
it does not run in PRs. you'll be able to trigger that manually once it has landed in main. |
This gives us a known-good configuration of Mirage to test against. The vast majority of the changes on the Dune side will not affect this, so it is not useful to add this to the regular CI; instead, this gives us a manual run to trigger at release time or on changes for which that can be useful. Signed-off-by: Etienne Millon <me@emillon.org>
* ci: add an action to test mirage This gives us a known-good configuration of Mirage to test against. The vast majority of the changes on the Dune side will not affect this, so it is not useful to add this to the regular CI; instead, this gives us a manual run to trigger at release time or on changes for which that can be useful. Signed-off-by: Etienne Millon <me@emillon.org>
* ci: add an action to test mirage This gives us a known-good configuration of Mirage to test against. The vast majority of the changes on the Dune side will not affect this, so it is not useful to add this to the regular CI; instead, this gives us a manual run to trigger at release time or on changes for which that can be useful. Signed-off-by: Etienne Millon <me@emillon.org>
This gives us a known-good configuration of Mirage to test against. The vast majority of the changes on the Dune side will not affect this, so it is not useful to add this to the regular CI; instead, this gives us a manual run to trigger at release time or on changes for which that can be useful.