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.
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
Use EISOP CF sources #118
Use EISOP CF sources #118
Changes from 25 commits
0897b15
d577777
0ef889c
20aac34
b8bf12d
47820ad
8baeb43
668e364
650470a
782ee08
a611b52
7547ec5
0982d00
c02e2a9
9c608ea
a564409
c07df12
939a0af
f690acc
165f412
a385efa
ff94fe6
4dbed1d
6648806
ac78d1c
02160b6
80311ae
8d43524
49cfc8a
045ffe6
384a077
3594656
593dd1a
8f13645
6b5bf11
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
We have a
SHALLOW
environment variable that users can set to enable this. That might be better than hard-coding (which, admittedly, we do for the JDK, but it's truly huge). I don't remember exactly how much thought we gave to all this, though.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 point of
$SHALLOW
is to allow CIs like GitHub actions to avoid cloning any commits they don't care about. If you're just running tests for CI you don't need to check any past commits out.I think if someone has their own fork of eisop we wouldn't want them to clone only one branch. I would suggest continuing to rely on
$SHALLOW
(defined externally) forchecker-framework
.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.
Not really related to this PR, but:
I wonder if that's worth investigating someday.
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 had a quick look at this post:
https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/
It seems to generally prefer the blob-less mode. For CI, where one only has a single build, continuing to use
--depth 1
seems okay. But as this script is for developer set-up, using blob-less might be better.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.
Let's postpone that to a different PR. It's not related to switching to EISOP.