Skip to content
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

Fix a break in perf runs #17855

Merged
merged 2 commits into from
Mar 15, 2017
Merged

Fix a break in perf runs #17855

merged 2 commits into from
Mar 15, 2017

Conversation

jaredpar
Copy link
Member

No description provided.

@jaredpar
Copy link
Member Author

test perf please

@jaredpar
Copy link
Member Author

CC @rchande, @jasonmalinowski, @TyOverby

Will merge once perf test is green.

@rchande
Copy link
Contributor

rchande commented Mar 14, 2017 via email

@jaredpar
Copy link
Member Author

@rchande

Note that Jenkins will mark the run as green even if the error I mentioned occurs

Sounds like something we should fix

Log is ready to view.

@rchande
Copy link
Contributor

rchande commented Mar 14, 2017

@jaredpar So there aren't any errors from PowerShell but it still looks like the perf runner isn't getting invoke. @TyOverby any ideas?

@rchande
Copy link
Contributor

rchande commented Mar 14, 2017

It also looks like we aren't installing the BenchView tools. Are we actually entering the body of the conditional on line 109?

@jaredpar
Copy link
Member Author

@rchande think I figured out the conditional issue. Pushed another change.

@rchande
Copy link
Contributor

rchande commented Mar 14, 2017

test perf please

@rchande
Copy link
Contributor

rchande commented Mar 14, 2017

@jaredpar , still seeing issues:

15:47:47 The term 'env:GIT_BRANCH' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
15:47:47 System.Management.Automation.CommandNotFoundException: The term 'env:GIT_BRANCH' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
15:47:47    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
15:47:47    at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
15:47:47    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
15:47:47    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

@jaredpar
Copy link
Member Author

test perf please

@rchande
Copy link
Contributor

rchande commented Mar 14, 2017

@jaredpar Looks like we're producing results now, but none of the perf subsystem's logs are appearing in the console output. Any idea what's up with that?

@jaredpar
Copy link
Member Author

test perf please

@rchande
Copy link
Contributor

rchande commented Mar 15, 2017

@jaredpar looks good. Thanks!

@jaredpar jaredpar merged commit 339fc32 into dotnet:master Mar 15, 2017
@jaredpar jaredpar deleted the fix-perf branch March 15, 2017 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants