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

Pango modules.cache contains jenkins builder path #14181

Open
Therzok opened this issue Apr 23, 2019 · 12 comments

Comments

@Therzok
Copy link
Member

@Therzok Therzok commented Apr 23, 2019

Steps to Reproduce

  1. It seems to happen during update of VSMac
  2. Observe sometimes font print out squares
  3. Is it possible that the post-install script is not being run or has errors?

Current Behavior

  1. Cause: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/596552
  2. Symptoms: https://developercommunity.visualstudio.com/content/problem/228583/vs2017-for-mac-setup-%E4%B8%AD%E6%96%87%E4%B9%B1%E7%A0%81.html

Expected Behavior

Fonts should work.

On which platforms did you notice this

[*] macOS
[ ] Linux
[ ] Windows

Version Used:

I think it's been going on for a while

@Therzok

This comment has been minimized.

Copy link
Member Author

@Therzok Therzok commented Apr 23, 2019

@alexischr

This comment has been minimized.

Copy link
Member

@alexischr alexischr commented Apr 23, 2019

I installed Mono JIT compiler version 6.0.0.6 (2019-02/12cadb2b21d Wed Feb 6 03:24:22 PST 2019)

and looked at the installed pango.modules - I see

# Pango Modules file
# Automatically generated file, do not edit
#
# ModulesPath = /Library/Frameworks/Mono.framework/Versions/6.0.0/lib/pango/1.8.0/modules
#
/Library/Frameworks/Mono.framework/Versions/6.0.0/lib/pango/1.8.0/modules/pango-arabic-lang.so ArabicScriptEngineLang PangoEngineLang PangoRenderNone arabic:*
/Library/Frameworks/Mono.framework/Versions/6.0.0/lib/pango/1.8.0/modules/pango-basic-coretext.so BasicScriptEngineCoreText PangoEngineShape PangoRenderCoreText common:
/Library/Frameworks/Mono.framework/Versions/6.0.0/lib/pango/1.8.0/modules/pango-indic-lang.so devaIndicScriptEngineLang PangoEngineLang PangoRenderNone devanagari:*
...

so no builder paths. So yeah the postinstall must be failing under some conditions only. Do you have a reproduction @Therzok ?

alexischr added a commit that referenced this issue Jun 17, 2019
We have several issues (e.g. #14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see #14181)
alexischr added a commit that referenced this issue Jun 18, 2019
We have several issues (e.g. #14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see #14181)
monojenkins added a commit to monojenkins/mono that referenced this issue Jun 19, 2019
We have several issues (e.g. mono#14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see mono#14181)
monojenkins added a commit to monojenkins/mono that referenced this issue Jun 19, 2019
We have several issues (e.g. mono#14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see mono#14181)
monojenkins added a commit to monojenkins/mono that referenced this issue Jun 19, 2019
We have several issues (e.g. mono#14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see mono#14181)
marek-safar added a commit that referenced this issue Jun 19, 2019
We have several issues (e.g. #14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see #14181)
marek-safar added a commit that referenced this issue Jun 19, 2019
We have several issues (e.g. #14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see #14181)
@Therzok Therzok changed the title Pango modules.cache contains jenkins builderp ath Pango modules.cache contains jenkins builder path Jun 27, 2019
alexischr added a commit that referenced this issue Jun 28, 2019
We have several issues (e.g. #14181) where the installer occasionally fails in the postinstall script for unknown causes, on some hosts.

This seems to be sometimes the culpable section and this patch should help trace the issue or alleviate the common symptoms of it (see #14181)
@Therzok

This comment has been minimized.

Copy link
Member Author

@Therzok Therzok commented Aug 28, 2019

Should this be closed?

@Therzok

This comment has been minimized.

Copy link
Member Author

@Therzok Therzok commented Aug 28, 2019

vsts ticked has been closed, I'll close this too and reopen if we see it again.

@Therzok Therzok closed this Aug 28, 2019
@kdubau

This comment has been minimized.

Copy link
Member

@kdubau kdubau commented Oct 8, 2019

You can repro the font rendering issue by installing a different Mono while VS4M is running (perhaps not the smartest idea but might offer some insight).

image

@kdubau

This comment has been minimized.

Copy link
Member

@kdubau kdubau commented Oct 8, 2019

@Therzok I don't have permission to re-open, could you?

@Therzok Therzok reopened this Oct 8, 2019
@Therzok

This comment has been minimized.

Copy link
Member Author

@Therzok Therzok commented Oct 8, 2019

Done!

@lambdageek

This comment has been minimized.

Copy link
Member

@lambdageek lambdageek commented Oct 24, 2019

If this happens to anyone, could you please collect:

  1. The contents of every .log file in /Library/Frameworks/Mono.framework/Versions/Current
  2. the output of:
     cd /Library/Frameworks/Mono.framework/Versions/Current
     file bin/fc-cache bin/pango-querymodules bin/gdk-pixbuf-query-loaders 
@marek-safar

This comment has been minimized.

Copy link
Member

@marek-safar marek-safar commented Oct 28, 2019

I can reproduce it on my machine when Mono installer failed to finish. I don't have any .log file under /Library/Frameworks/Mono.framework/Versions/Current

The output of file gdk-pixbuf-query-loaders

in/fc-cache:                 Mach-O universal binary with 2 architectures: [i386:Mach-O executable i386] [x86_64:Mach-O 64-bit executable x86_64]
bin/fc-cache (for architecture i386):	Mach-O executable i386
bin/fc-cache (for architecture x86_64):	Mach-O 64-bit executable x86_64
bin/pango-querymodules:       Mach-O universal binary with 2 architectures: [i386:Mach-O executable i386] [x86_64:Mach-O 64-bit executable x86_64]
bin/pango-querymodules (for architecture i386):	Mach-O executable i386
bin/pango-querymodules (for architecture x86_64):	Mach-O 64-bit executable x86_64
bin/gdk-pixbuf-query-loaders: Mach-O universal binary with 2 architectures: [i386:Mach-O executable i386] [x86_64:Mach-O 64-bit executable x86_64]
bin/gdk-pixbuf-query-loaders (for architecture i386):	Mach-O executable i386
bin/gdk-pixbuf-query-loaders (for architecture x86_64):	Mach-O 64-bit executable x86_64

That's with Mono JIT compiler version 6.6.0.140 (2019-08/1b2e536b223 Wed Oct 23 17:31:53 EDT 2019)

@lambdageek what else to try?

@alexischr

This comment has been minimized.

Copy link
Member

@alexischr alexischr commented Oct 28, 2019

@marek-safar if you can reproduce the Mono installer failing, could you open the installer, go to Window->Installer Log and collect all output at the "Show all logs" detail level? We hope to see where the postinstall script failed.

@alexischr

This comment has been minimized.

Copy link
Member

@alexischr alexischr commented Oct 28, 2019

@marek-safar Also, does the problem persist when you restart VS4Mac? I was finally able to reproduce with @kdubau 's help, but that problem goes away with a restart, so it is not the persistent problem that some users seem to face.

@marek-safar

This comment has been minimized.

Copy link
Member

@marek-safar marek-safar commented Oct 29, 2019

@alexischr yes, the issue persists after VS4M restart (even machine restart).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.