-
Notifications
You must be signed in to change notification settings - Fork 375
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
Test pack and lsp during CI #3067
Merged
+99
−8
Merged
Changes from 20 commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
9515c12
[ ci ] Move external libs outside of Idris2 job
CodingCellist f9873b7
[ ci ] Run extern-libs after Idris2
CodingCellist cde9fe5
[ ci ] Copy setup-jobs from ci-idris2 to extern-libs
CodingCellist 8ec3d40
[ ci ] rm the ci-idris2 dependency from extern-libs
CodingCellist 63ab414
[ ci ] All extern libs depend on self-host
CodingCellist 6f54787
[ ci ] Add extern libs concurrency group
CodingCellist 4c27d3c
[ ci ] Build pack and the LSP as part of ext-libs
CodingCellist 814ecb4
[ ci ] Fix pack URL? RM lsp test for now
CodingCellist cd6226c
[ ci ] Add GH_REF_NAME to pack idris2.commit
CodingCellist 6909bec
[ ci ] Fetch the PR before attempting pack install
CodingCellist af4bd1b
[ ci ] Mark CWD as safe for git-fetch reasons
CodingCellist ddf9d1f
[ ci ] Restore the REF to the commit pack param
CodingCellist d39a52b
[ ci ] Use 'latest' syntax to fix things
CodingCellist 01f83c4
[ ci ] Make linter happy
CodingCellist f9f3eab
[ ci ] Enable the pack-lsp test
CodingCellist 526847d
[ ci ] Don't prompt before building lsp
CodingCellist d739f3e
[ admin ] Merge branch 'main' into ci-pack-lsp
CodingCellist 1f97374
[ ci ] Avoid work duplication in idris2 vs ext-libs
CodingCellist 4d27adc
[ ci ] Rename idris2 CI job to reflect lib building
CodingCellist e827708
[ admin ] Merge branch 'main' into ci-pack-lsp
CodingCellist 8364769
[ ci ] Depend on 'initialise' to make linter happy
CodingCellist 2a96c36
[ ci ] Group pack toml file-writing commands
CodingCellist File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think, after setting
pack.toml
, one needs to callpack fetch
to make surepack
has fetched the correct commit of the branch mentioned inlatest:
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.
The local testing I did with this seemed to correctly get the commit, but I'll @stefan-hoeck just to be sure; afaiu,
pack install pack
is clever enough to fetch the latest/specified Idris2-commit before rebuilding and reinstalling itself : )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.
My knowledge would be that in this case the latest commit at the moment of creation of the docker image would be used instead (without calling
pack fetch
, as I suggest), but right, let's wait for Stefan's answerThere 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.
Did some testing using the docker image rather than my local
pack
install; it seemspack fetch
is indeed redundant:Before, i.e. having just launched a fresh copy of the image:
After creating a matching
pack.toml
and runningpack install pack
:Which matches the latest commit on this branch : )
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.
git fetch
is needed when there were some commits into themain
branch between the docker image creation and running the CI. Since there were no commits intomain
recently, you cannot reproduce this situation