apply a workaround fix for the release blocker issue
Signed-off-by: onur-ozkan <work@onurozkan.dev>
This commit is contained in:
parent
ab3924b298
commit
614dc1c933
1 changed files with 12 additions and 1 deletions
|
@ -129,8 +129,19 @@ pub fn get_closest_merge_commit(
|
|||
git.current_dir(git_dir);
|
||||
}
|
||||
|
||||
let channel = include_str!("../../ci/channel");
|
||||
|
||||
let merge_base = {
|
||||
if CiEnv::is_ci() {
|
||||
if CiEnv::is_ci() &&
|
||||
// FIXME: When running on rust-lang managed CI and it's not a nightly build,
|
||||
// `git_upstream_merge_base` fails with an error message similar to this:
|
||||
// ```
|
||||
// called `Result::unwrap()` on an `Err` value: "command did not execute successfully:
|
||||
// cd \"/checkout\" && \"git\" \"merge-base\" \"origin/master\" \"HEAD\"\nexpected success, got: exit status: 1\n"
|
||||
// ```
|
||||
// Investigate and resolve this issue instead of skipping it like this.
|
||||
(channel == "nightly" || !CiEnv::is_rust_lang_managed_ci_job())
|
||||
{
|
||||
git_upstream_merge_base(config, git_dir).unwrap()
|
||||
} else {
|
||||
// For non-CI environments, ignore rust-lang/rust upstream as it usually gets
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue