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 noJit builds #114

Closed
wants to merge 1 commit into from
Closed

fix noJit builds #114

wants to merge 1 commit into from

Conversation

rajatd
Copy link
Contributor

@rajatd rajatd commented Jan 15, 2016

fix noJit builds

Closes #112

@msftclas
Copy link

Hi @rajatd, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!


It looks like you're a Microsoft contributor (Rajat Dua). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@rajatd
Copy link
Contributor Author

rajatd commented Jan 15, 2016

@dilijev can you review this?

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@dotnet-bot test nojit please

@@ -818,6 +825,7 @@ namespace Js
Assert(this->lastInternalFrameInfo.codeAddress);
this->lastInternalFrameInfo.frameConsumed = true;
}
#endif
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To make it more clear can you change this to #endif // ENABLE_NATIVE_CODEGEN and the above #endif to #endif // DBG?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. nested #ifdefs- can get confusing

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

Jenkins is running slowly. I'm confirming locally that the change merged with master compiles and passes tests.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

Looks like the test script is looking for the NoJit binaries in the wrong place for the -disableJit config. That may cause the disablejit checks I triggered to fail. I'll commit an updated script. This change builds, so I think this change will be fine as-is, once it can merge with the new test script.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@dotnet-bot test nojit please

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

LGTM barring checks and the test script issue I mentioned.

@davkean
Copy link

davkean commented Jan 15, 2016

Please stop queuing more builds of the same changes - all you are doing adding more builds to the queue, making Jenkins take even longer.

Jenkins is a shared service between many teams, so be mindful of resources.

//cc @mmitche

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@davkean @mmitche I understand your frustration. We feel it too. In this case I don't believe we're abusing the resource. This change affects the dailies so we need them to run to verify its correctness. As for the extra requeue of all checks, I apologize. I should have reviewed the change first and waited for the update before adding the dailies.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@rajatd All tests pass on my machine when this change is merged on top of #117.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@davkean @mmitche By the way, I've been wondering if there's an easy way to cancel all queued requests that haven't been issued build machines for a given PR? When a new commit is added to a PR and checks re-queue, do the old ones that haven't run yet get cancelled?

@mmitche
Copy link
Contributor

mmitche commented Jan 15, 2016

It doesn't automatically cancel, but looking at the source I'm led to believe it may be able to be done.

Sent from my Windows Phone


From: Doug Ilijevmailto:notifications@github.com
Sent: ‎1/‎14/‎2016 5:51 PM
To: Microsoft/ChakraCoremailto:ChakraCore@noreply.github.com
Cc: Matt Mitchellmailto:mmitche@microsoft.com
Subject: Re: [ChakraCore] fix noJit builds (#114)

@davkeanhttps://github.com/davkean @mmitchehttps://github.com/mmitche I understand your frustration. We feel it too. In this case I don't believe we're abusing the resource. This change affects the dailies so we need them to run to verify its correctness. As for the extra requeue of all checks, I apologize. I should have reviewed the change first and waited for the update before adding the dailies.


Reply to this email directly or view it on GitHubhttps://github.com//pull/114#issuecomment-171843211.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

I cancelled the daily checks that were already triggered on this one as I believe they will fail until #117 gets merged in. I'll re-queue the dailies once that's done.

@davkean
Copy link

davkean commented Jan 15, 2016

@dilijev I was referring to these:

image

I thought these were duplicated because of your double mention of the trigger phrase for your nojit tests, but I was wrong. Apologies. Looking at them, I can't figure out why both sets were triggered:

image

@mmitche Maybe this is just Jenkins/Github catching up with the original request, and then queue again up when the PR branch was updated? They are so close to each other in time.

chakrabot pushed a commit that referenced this pull request Jan 15, 2016
…e correct _BinDir. Unblocks ref #114.

Merge pull request #117 from dilijev:nojit-test
Fix 'jenkins.testone.cmd ... -disablejit' path to use the correct _BinDir. Unblocks ref #114.
@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@rajatd You're good to merge this one once tests pass.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@dotnet-bot test dailies please

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@digitalinfinity Do we currently support ARM builds for the disablejit configuration? Just want to know whether they were supposed to work.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@rajatd I accidentally triggered all the dailies instead of just the relevant ones. Windows 7 daily_x64_debug is a known failing configuration at the moment. I'll trigger another one and then kill it so at least this PR will be yellow instead of red.

@dilijev
Copy link
Contributor

dilijev commented Jan 15, 2016

@dotnet-bot test Windows 7 daily_x64_debug please

@rajatd
Copy link
Contributor Author

rajatd commented Jan 15, 2016

@dilijev , do we have any historical data pertaining to state of arm builds with no-jit?

@dilijev
Copy link
Contributor

dilijev commented Jan 16, 2016

@rajatd Not according to Jenkins (as we only have failed daily builds so far). @digitalinfinity was working on this before so that's why I tagged him. I guess we could try the commit at the time Hitesh originally merged in the addition of the NoJIT configurations and see what happens there.

See 6649f32
See #4

@dilijev
Copy link
Contributor

dilijev commented Jan 16, 2016

I tried from that commit with the current jenkins configs I recently corrected.

jenkins.buildone.cmd arm release "/p:BuildJIT=false"

Produces errors:

Chakra.Runtime.Language.lib(arm_Thunks.obj) : error LNK2001: unresolved external symbol "private: static void * (__cdecl*__cdecl
Js::DynamicProfileInfo::EnsureDynamicProfileInfo(class Js::ScriptFunction *))(class Js::RecyclableObject *,struct Js::CallInfo,..
.)" (?EnsureDynamicProfileInfo@DynamicProfileInfo@Js@@CAP6APAXPAVRecyclableObject@2@UCallInfo@2@ZZPAVScriptFunction@2@@Z) [E:\dev
\Chakra3\core\bin\ChakraCore\ChakraCore.vcxproj]
Chakra.Runtime.Language.lib(arm_Thunks.obj) : error LNK2001: unresolved external symbol "private: static void * (__cdecl*__cdecl
Js::InterpreterStackFrame::EnsureDynamicInterpreterThunk(class Js::ScriptFunction *))(class Js::RecyclableObject *,struct Js::Cal
lInfo,...)" (?EnsureDynamicInterpreterThunk@InterpreterStackFrame@Js@@CAP6APAXPAVRecyclableObject@2@UCallInfo@2@ZZPAVScriptFuncti
on@2@@Z) [E:\dev\Chakra3\core\bin\ChakraCore\ChakraCore.vcxproj]
E:\dev\Chakra3\core\Build\VcBuild\bin\arm_release\ChakraCore.dll : fatal error LNK1120: 2 unresolved externals [E:\dev\Chakra3\co
re\bin\ChakraCore\ChakraCore.vcxproj]

@dilijev
Copy link
Contributor

dilijev commented Jan 16, 2016

Same error as currently. I think your change is good to check in as-is and we'll follow up with the ARM issue in a separate PR.

@dilijev
Copy link
Contributor

dilijev commented Jan 20, 2016

Committed as a0f58b0

@rajatd
Copy link
Contributor Author

rajatd commented Jan 20, 2016

Thanks @dilijev , I was waiting to see the build status turn green

@dilijev
Copy link
Contributor

dilijev commented Jan 20, 2016

@rajatd It was green before I marked as merged. That's how I knew it was in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Daily builds of DisableJIT (x86, x64) are broken.
5 participants