Uh oh!
There was an error while loading. Please reload this page.
Use artifacts layout in place of bin dir - #51
Conversation
jashook
commented
Nov 14, 2019
Also I asked @sbomer and @AaronRobinsonMSFT for a review |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
sbomer
commented
Nov 14, 2019
The rest looks ok to me. |
jkoritzinsky
left a comment
There was a problem hiding this comment.
Arcade uses log instead of logs for the logs directory under artifacts.
Also, is this going to output to the artifacts directory in the root or an artifacts directory under src/coreclr?
safern
commented
Nov 15, 2019
Based on the changes I think it will be in the root, and that’s how it should be to be consistent, one central location. |
jashook
commented
Nov 15, 2019
This will put the artifacts folder under |
jkoritzinsky
commented
Nov 15, 2019
I think we should change it to output to the root artifacts folder so all of the outputs follow the Arcade convention for location. |
ViktorHofer
commented
Nov 15, 2019
Yeah, the artifacts folder should under the repo root. |
trylek
commented
Nov 17, 2019
The change is getting pretty big - would there be any chance to merge in some parts of it that are sufficiently stable already? I completely agree that additional side cleanups like deleting bit-rotten or obsolete files should come next to avoid further complicating this change that is already complex enough. |
jashook
commented
Nov 17, 2019
I believe this change should pass CI with the last commit. We will see. Note dotnet/jitutils#227 should fixes the formatting jobs. |
jashook
commented
Nov 17, 2019
I do not have further plans to change this if this change passes CI. |
jashook
commented
Nov 17, 2019
libraries ci checkout failure seems weird. @ViktorHofer |
jashook
commented
Nov 17, 2019
Also seems unrelated to the change. |
jashook
commented
Nov 18, 2019
This change finally passed CI. Merging. Will start documentation after this goes in. |
jashook
commented
Nov 18, 2019
Looks like I merged in place of squashed. That is very annoying. |
You just merged and the repo's not public yet. You can force push to correct it. |
jashook
commented
Nov 18, 2019
Done, I hate re-writing history. Hope this doesn't happen again. |
stephentoub
commented
Nov 18, 2019
jashook
commented
Nov 18, 2019
This seems to have been added as part of the rebase I did which squashed the merge changes I had... :( |
And it changed the commit title? Looks like characters were deleted. That in and of itself isn't a big deal.. I just want to make sure something else worse didn't get messed up. |
jashook
commented
Nov 18, 2019
I didn't notice that, I have no idea why that happened. |
Looking closer. |
jashook
commented
Nov 18, 2019
I cannot explain why, but that commit title is how git displayed in my local enlistment. History before the rebase one my machine was: |
jashook
commented
Nov 18, 2019
On first guess, it was too long, but Tomas' change looks like it has more characters.. |
jashook
commented
Nov 18, 2019
I really apologize, I can do another push to amend the commit. Although admittedly I really would prefer to not much much more. @stephentoub let me know. |
stephentoub
commented
Nov 18, 2019
If the only problem is the title on that commit, just leave it. |
No diff on contents. The history (minus the commit title you pointed) out looks correct to me. Minus the silly bit where I am added to the author in the github history. The git log itself correctly does not have me as an author. |

No description provided.