Skip to content

Dummy commit to attempt to recreate prerelease artifacts #51627

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 1 commit into from
Jun 19, 2018

Conversation

Mark-Simulacrum
Copy link
Member

I am uncertain that this will work, but I think it might.

I believe that due to a rather late start on starting the prerelease deploy/build we may have been deploying around the time of date change which resulted in the manifest getting a different date than the directory the artifacts were uploaded into. I'm uncertain that was the case, but it seems like it.

This is an attempt to re-deploy, hopefully not hitting the same problem.

@Mark-Simulacrum
Copy link
Member Author

@bors r+ p=100

@bors
Copy link
Collaborator

bors commented Jun 19, 2018

📌 Commit 852b2ca has been approved by Mark-Simulacrum

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Jun 19, 2018
@rust-highfive
Copy link
Contributor

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive
Copy link
Contributor

warning Warning warning

  • Pull requests are usually filed against the master branch for this repo, but this one is against stable. Please double check that you specified the right target!

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jun 19, 2018
@bors
Copy link
Collaborator

bors commented Jun 19, 2018

⌛ Testing commit 852b2ca with merge 3eda71b...

bors added a commit that referenced this pull request Jun 19, 2018
Dummy commit to attempt to recreate prerelease artifacts

I am uncertain that this will work, but I think it might.

I believe that due to a rather late start on starting the prerelease deploy/build we may have been deploying around the time of date change which resulted in the manifest getting a different date than the directory the artifacts were uploaded into. I'm uncertain that was the case, but it seems like it.

This is an attempt to re-deploy, hopefully not hitting the same problem.
@bors
Copy link
Collaborator

bors commented Jun 19, 2018

☀️ Test successful - status-appveyor, status-travis
Approved by: Mark-Simulacrum
Pushing 3eda71b to stable...

@bors bors merged commit 852b2ca into rust-lang:stable Jun 19, 2018
@Mark-Simulacrum Mark-Simulacrum deleted the stable-next branch June 19, 2018 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants