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

Document and automate the process to fetch from upstream #8

Merged
merged 1 commit into from
Dec 2, 2021

Conversation

joshpeterson
Copy link

@joshpeterson joshpeterson commented Nov 29, 2021

The process of fetching changes from the upstream dotnet/runtime
repository will be done weekly by a Yamato job. This job will

  1. Fetch from the main branch upstream
  2. Create a branch of unity-main named with the current date
  3. Open a pull request to merge the new branch into unity-main

@joshpeterson
Copy link
Author

You can see an example of the automatically generated pull request here: #7

@joshpeterson
Copy link
Author

I think we have the scripts in a good state now. The latest test PR is #9.

If these make sense, I'll squash the commits down before merging. Let me know!

@joshpeterson joshpeterson requested review from brian-taylor-unity and removed request for btylerUnity November 30, 2021 14:29
@joshpeterson
Copy link
Author

This is working now with a fast-forward merge on main rather than a rebase.

@joshpeterson
Copy link
Author

I've squashed the changes down now into their final form, I hope!

unity/README.md Outdated Show resolved Hide resolved
unity/README.md Outdated Show resolved Hide resolved
The process of fetching changes from the upstream dotnet/runtime
repository will be done weekly by a Yamato job. This job will

1. Fetch from the `main` branch upstream
2. Create a branch of `unity-main` named with the current date
3. Open a pull request to merge the new branch into `unity-main`
@joshpeterson
Copy link
Author

After some discussion with @bholmes, it turns out that he is correct - we don't need to use main in this fork. I've updated the scripts, the docs, and the PR description to use this approach, which is simpler. Please re-review these changes.

unity/README.md Show resolved Hide resolved
@joshpeterson joshpeterson merged commit 8e52e0f into unity-main Dec 2, 2021
@joshpeterson joshpeterson deleted the add-unity-readme branch December 2, 2021 15:25
mrvoorhe pushed a commit that referenced this pull request Jul 11, 2023
…tnet#87189)

This fixes a startup crash on Big Sur:

> error: * Assertion at /Users/runner/work/1/s/src/mono/mono/utils/mono-hwcap-arm64.c:35, condition `res == 0' not met

Because sysctl can't find some of these options:

    $ sysctl hw.optional.armv8_crc32
    hw.optional.armv8_crc32: 1
    $ sysctl hw.optional.arm.FEAT_RDM
    sysctl: unknown oid 'hw.optional.arm.FEAT_RDM'
    $ sysctl hw.optional.arm.FEAT_DotProd
    sysctl: unknown oid 'hw.optional.arm.FEAT_DotProd'
    $ sysctl hw.optional.arm.FEAT_SHA1
    sysctl: unknown oid 'hw.optional.arm.FEAT_SHA1'
    $ sysctl hw.optional.arm.FEAT_SHA256
    sysctl: unknown oid 'hw.optional.arm.FEAT_SHA256'
    $ sysctl hw.optional.arm.FEAT_AES
    sysctl: unknown oid 'hw.optional.arm.FEAT_AES'

Full stack trace:

* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 2.1
  * frame #0: 0x0000010ef37560 libmonosgen-2.0.dylib`monoeg_assertion_message
    frame #1: 0x0000010ef375cc libmonosgen-2.0.dylib`mono_assertion_message + 32
    frame #2: 0x0000010ef40d6c libmonosgen-2.0.dylib`mono_hwcap_arch_init + 544
    frame #3: 0x0000010ef54bd8 libmonosgen-2.0.dylib`mono_hwcap_init + 72
    frame #4: 0x0000010ee14dc0 libmonosgen-2.0.dylib`parse_optimizations + 52
    frame #5: 0x0000010edbed48 libmonosgen-2.0.dylib`mono_init
    frame #6: 0x0000010ee18968 libmonosgen-2.0.dylib`mono_jit_init_version
    frame #7: 0x0000010f48a300 libxamarin-dotnet-debug.dylib`xamarin_bridge_initialize + 216
    frame #8: 0x0000010f4900a4 libxamarin-dotnet-debug.dylib`xamarin_main + 376
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants