Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[mtouch] Detect when we run into the 32-bit arm size limitation, and report a better error. Fixes #6526.#6855

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
rolfbjarne merged 3 commits intodotnet:xcode11fromrolfbjarne:issue-6526
Aug 28, 2019

Conversation

@rolfbjarne
Copy link
Member

Also limit the output from the native compiler, so that we don't overload the
IDEs with output if the native compiler produces tens of thousands of errors.

Fixes#6526.

…report a better error.Fixesdotnet#6526.Also limit the output from the native compiler, so that we don't overload theIDEs with output if the native compiler produces tens of thousands of errors.Fixesdotnet#6526.
Copy link
Contributor

@spouliotspouliot left a comment

Choose a reason for hiding this comment

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

minor

varmsg=$"Process exited with code{p.ExitCode}, command:\n{path}";
if(output!=null&&output.Length>0)
msg+=$"\n{output}";
Console.Error.WriteLine(msg);
Copy link
Contributor

Choose a reason for hiding this comment

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

why not just do aConsole.Error.WriteLine (output); to avoid creating a new (possibly very large) string ? e.g.

Console.Error.WriteLine($"Process exited with code{p.ExitCode}, command:\n{path}");if(output!=null&&output.Length>0){Console.Error.WriteLine();Console.Error.WriteLine(output);}

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

There are other comments that explain this: we do things in parallel, and having multiple CWLs means it will be much more likely that other threads will write to stdout at the same time, interspersing their output with this output, and making a big incomprehensible mess out of it all.

spouliot reacted with thumbs up emoji
Copy link
Contributor

Choose a reason for hiding this comment

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

yep, seen it (later) but maybe we could re-use theStringBuilder instance here ? e.g. callInsert to pre-pendmsg and a new line and then a singleToString withWriteLine ?

rolfbjarne reacted with thumbs up emoji
// There can be thousands of these, but we only need one.
reported_5107=true;
exceptions.Add(ErrorHelper.CreateError(5107,"The assembly '{0}' can't be AOT-compiled for 32-bit architectures because the native code is too big for the 32-bit ARM architecture.",Path.GetFileNameWithoutExtension(OutputFile)));
}
Copy link
Contributor

Choose a reason for hiding this comment

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

can't we share that same logic instead of having it in two places ?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

I'll look into that

@monojenkins
Copy link
Collaborator

Build success
Build succeeded
API Diff (from stable)
API Diff (from PR only) (no change)
Generator Diff (no change)
Test run succeeded

Copy link
Contributor

@spouliotspouliot left a comment

Choose a reason for hiding this comment

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

❤️

@monojenkins
Copy link
Collaborator

Build failure
Build succeeded
API Diff (from stable)
API Diff (from PR only) (no change)
Generator Diff (no change)
🔥Test run failed 🔥

Test results

56 tests failed, 37 tests passed.

Failed tests

  • monotouch-test/iOS Unified 32-bits - simulator/Debug: BuildFailure
  • framework-test/iOS Unified 32-bits - simulator/Debug: BuildFailure
  • interdependent-binding-projects/iOS Unified 32-bits - simulator/Debug: BuildFailure
  • dont link/iOS Unified 32-bits - simulator/Release: BuildFailure
  • link all/iOS Unified 32-bits - simulator/Debug: BuildFailure
  • link all/iOS Unified 32-bits - simulator/Release: BuildFailure
  • link sdk/iOS Unified 32-bits - simulator/Debug: BuildFailure
  • link sdk/iOS Unified 32-bits - simulator/Release: BuildFailure
  • monotouch-test/iOS Unified 32-bits - simulator/Debug (static registrar): BuildFailure
  • monotouch-test/iOS Unified 32-bits - simulator/Release (all optimizations): BuildFailure
  • monotouch-test/iOS Unified 64-bits - simulator/Debug: BuildFailure
  • framework-test/iOS Unified 64-bits - simulator/Debug: BuildFailure
  • interdependent-binding-projects/iOS Unified 64-bits - simulator/Debug: BuildFailure
  • dont link/iOS Unified 64-bits - simulator/Release: BuildFailure
  • link all/iOS Unified 64-bits - simulator/Debug: BuildFailure
  • link all/iOS Unified 64-bits - simulator/Release: BuildFailure
  • link sdk/iOS Unified 64-bits - simulator/Debug: BuildFailure
  • link sdk/iOS Unified 64-bits - simulator/Release: BuildFailure
  • monotouch-test/iOS Unified 64-bits - simulator/Debug (static registrar): BuildFailure
  • monotouch-test/iOS Unified 64-bits - simulator/Release (all optimizations): BuildFailure
  • monotouch-test/tvOS - simulator/Debug: BuildFailure
  • framework-test/tvOS - simulator/Debug: BuildFailure
  • mini/tvOS - simulator/Debug: BuildFailure
  • interdependent-binding-projects/tvOS - simulator/Debug: BuildFailure
  • fsharp/tvOS - simulator/Debug: BuildFailure
  • introspection/tvOS - simulator/Debug: BuildFailure
  • dont link/tvOS - simulator/Debug: BuildFailure
  • dont link/tvOS - simulator/Release: BuildFailure
  • link all/tvOS - simulator/Debug: BuildFailure
  • link all/tvOS - simulator/Release: BuildFailure
  • link sdk/tvOS - simulator/Debug: BuildFailure
  • link sdk/tvOS - simulator/Release: BuildFailure
  • mono-native-compat/tvOS - simulator/Debug: BuildFailure
  • mono-native-unified/tvOS - simulator/Debug: BuildFailure
  • monotouch-test/tvOS - simulator/Debug (static registrar): BuildFailure
  • monotouch-test/tvOS - simulator/Release (all optimizations): BuildFailure
  • monotouch-test/watchOS 32-bits - simulator/Debug: BuildFailure
  • framework-test/watchOS 32-bits - simulator/Debug: BuildFailure
  • mini/watchOS 32-bits - simulator/Debug: BuildFailure
  • interdependent-binding-projects/watchOS 32-bits - simulator/Debug: BuildFailure
  • fsharp/watchOS 32-bits - simulator/Debug: BuildFailure
  • introspection/watchOS 32-bits - simulator/Debug: BuildFailure
  • dont link/watchOS 32-bits - simulator/Debug: BuildFailure
  • dont link/watchOS 32-bits - simulator/Release: BuildFailure
  • link all/watchOS 32-bits - simulator/Debug: BuildFailure
  • link all/watchOS 32-bits - simulator/Release: BuildFailure
  • link sdk/watchOS 32-bits - simulator/Debug: BuildFailure
  • link sdk/watchOS 32-bits - simulator/Release: BuildFailure
  • mono-native-compat/watchOS 32-bits - simulator/Debug: BuildFailure
  • mono-native-unified/watchOS 32-bits - simulator/Debug: BuildFailure
  • monotouch-test/watchOS 32-bits - simulator/Debug (static registrar): BuildFailure
  • monotouch-test/watchOS 32-bits - simulator/Release (all optimizations): BuildFailure
  • introspection/tvOS - simulator/Debug (tvOS 10.2): BuildFailure
  • introspection/watchOS 32-bits - simulator/Debug (watchOS 3.2): BuildFailure
  • MSBuild tests/iOS: Failed (Execution failed with exit code 23)
  • MTouch tests/NUnit: Failed (Execution failed with exit code 64)

mtouch.Profile=Profile.iOS;
mtouch.Abi="armv7";
mtouch.Linker=MTouchLinker.DontLink;
/* Once the xcode11 branch has been merged into master, we should be able to do the following instead, which will make the test faster
Copy link
Contributor

Choose a reason for hiding this comment

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

Issue to remember doing that?

@monojenkins
Copy link
Collaborator

Build success
Build succeeded
API Diff (from stable)
API Diff (from PR only) (no change)
Generator Diff (no change)
Test run succeeded

@rolfbjarnerolfbjarne merged commitb8e9c83 intodotnet:xcode11Aug 28, 2019
@rolfbjarnerolfbjarne added bugIf an issue is a bug or a pull request a bug fix note-highlightWorth calling out specifically in release notes labelsAug 29, 2019
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@dalexsotodalexsotodalexsoto approved these changes

@chamonschamonsAwaiting requested review from chamons

+3 more reviewers

@spouliotspouliotspouliot approved these changes

@mandel-macaquemandel-macaquemandel-macaque approved these changes

@VincentDondainVincentDondainVincentDondain approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

bugIf an issue is a bug or a pull request a bug fixnote-highlightWorth calling out specifically in release notes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@rolfbjarne@monojenkins@dalexsoto@spouliot@mandel-macaque@VincentDondain

[8]ページ先頭

©2009-2025 Movatter.jp