Dummy commit to attempt to recreate prerelease artifacts #51627
Merged
Conversation
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
|
@bors r+ p=100 |
|
📌 Commit 852b2ca has been approved by |
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
|
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.
|
☀️ Test successful - status-appveyor, status-travis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.