-
-
Notifications
You must be signed in to change notification settings - Fork 286
Bump v1.1.0 compatibility test to v1.2.1 #883
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
442aef2
Bump v1.1.0 compatibility test to v1.2.0
chenrui333 a239d4e
Upgrade MacOS from HighSierra to Mojave
chenrui333 b73c99c
Empty commit to trigger a new build
chenrui333 98df247
Bump bazel to v1.2.1
chenrui333 55ba080
Fix sha for 0.28.0
chenrui333 2b17f1e
Revert "Upgrade MacOS from HighSierra to Mojave"
chenrui333 1114752
Update sha for 0.28.0 to HEAD
chenrui333 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 hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
It looks like we are no longer testing with an older version (we used to test with the oldest and the newest that worked and hoped all the ones in the middle would work).
We should probably find the sha that we switched away from 0.28.0 and put the label here or remove this table.
Since we don't test the oldest that works we don't really know what versions work for which shas, so if we are just going to test with 1, we should probably remove the table (since it isn't very accurate).
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 am fine either way as I am always using the latest though.
Uh oh!
There was an error while loading. Please reload this page.
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.
Another thing I can think about this is to introduce more testing in the bazelci and it would cover more bazel versions.
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.
It's hard for many orgs to update large builds with many rules not all of which support the latest versions. It is much more of a service to tell users the versions that work for each version of bazel rather than them having to git-bisect it.
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.
yeah, that is why I think this sha version table might be still quite useful 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.
Sure, I will revert my 0.28.0 HEAD change.
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.
+1 to explicitly labeling the default commit.
@chenrui333 Id love for you to do this here but you can feel free to do it in a separate PR or not at all and I’ll do it.
Thanks!
Uh oh!
There was an error while loading. Please reload this page.
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.
@ittaiz I guess I missed on the default commit, do you prefer HEAD or you prefer explicit SHA (which is current HEAD)?
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.
This is great. I miswrote. I meant labeling in the Travis config and the test script the default Bazel version (not commit).
I’ll merge this as is.
If you can follow up with a PR with this I’d be grateful :)
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.
Sure, I can file a follow up PR on this.