-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix noJit builds #114
Conversation
Hi @rajatd, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
TTYL, MSBOT; |
@dilijev can you review this? |
@dotnet-bot test nojit please |
@@ -818,6 +825,7 @@ namespace Js | |||
Assert(this->lastInternalFrameInfo.codeAddress); | |||
this->lastInternalFrameInfo.frameConsumed = true; | |||
} | |||
#endif |
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.
To make it more clear can you change this to #endif // ENABLE_NATIVE_CODEGEN
and the above #endif
to #endif // DBG
?
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.
Sure. nested #ifdefs- can get confusing
Jenkins is running slowly. I'm confirming locally that the change merged with master compiles and passes tests. |
Looks like the test script is looking for the NoJit binaries in the wrong place for the |
@dotnet-bot test nojit please |
LGTM barring checks and the test script issue I mentioned. |
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 |
…nDir. Unblocks ref chakra-core#114.
@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. |
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 @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. — |
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. |
@dilijev I was referring to these: 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: @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. |
@rajatd You're good to merge this one once tests pass. |
@dotnet-bot test dailies please |
@digitalinfinity Do we currently support ARM builds for the disablejit configuration? Just want to know whether they were supposed to work. |
@rajatd I accidentally triggered all the dailies instead of just the relevant ones. |
@dotnet-bot test Windows 7 daily_x64_debug please |
@dilijev , do we have any historical data pertaining to state of arm builds with no-jit? |
@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. |
I tried from that commit with the current jenkins configs I recently corrected.
Produces errors:
|
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. |
Committed as a0f58b0 |
Thanks @dilijev , I was waiting to see the build status turn green |
@rajatd It was green before I marked as merged. That's how I knew it was in. |
fix noJit builds
Closes #112