-
Notifications
You must be signed in to change notification settings - Fork 4
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
Attempt to do a comparison of forced UseVirtualTag #7
base: master
Are you sure you want to change the base?
Attempt to do a comparison of forced UseVirtualTag #7
Conversation
let compilerForkToTest = @"https://github.com/forki/visualfsharp" | ||
let compilerHashes = ["71c8798e19d6e15d3e6a98c80da658aa5ed2c630"; "ee0baed"] | ||
let compilerForkToTest = @"https://github.com/manofstick/visualfsharp" | ||
let compilerHashes = ["5c931e3149ebdd5d1e5f9721a3c6dbfb63e9d1c6"; "9d5e36a7aa66f029640aa05f96bd7b54907aef81"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we need some way to alias. I assume branch names will just work
|
this looks awesome. Only question is how trustworthy my perf framework is... |
Well a bit more what I was expecting: Compiler: 32c530ebe42f34a863a9e55b682f90685e658125 But times obviously jump around a bit; because the unmodified changeset went from: Compiler: 9d5e36a7aa66f029640aa05f96bd7b54907aef81 Which is an almost 2% change; so probably hard to detect any minor changes, but atleast should detect any major problems... |
Shouldn't really change the performance at all, so just check that that is true, within the scope of the AppVeyor environment...
See if the results are consistent...
Just creating PR to get AppVeyor to do some work...
This is just a shotgun approach to UseVirtualTag, and still tweaks are required, but should be a reasonable baseline...