[chore](workflow) Fix the BE UT (Clang) workflow#16847
Merged
Merged
Conversation
Contributor
Author
|
p0 |
morningman
pushed a commit
that referenced
this pull request
Feb 18, 2023
Fix the BE UT (Clang) workflow
yagagagaga
pushed a commit
to yagagagaga/doris
that referenced
this pull request
Mar 9, 2023
Fix the BE UT (Clang) workflow
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Proposed changes
Remove the command
apt upgradein theBE UT (Clang)workflow.Problem summary
Recently, the runner-image was updated frequently and some bugs were introduced which made our workflow
BE UT (Clang)fail. See https://github.com/apache/doris/actions/runs/4195816421.Actually, in
BE UT (Clang)workflow, we don't need to execute the commandapt upgrade. We can remove it and fix the issues.Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...