Please consider disabling fsnotify in certain architectures

[TheTincho]

Hi,

As noted in bug fsnotify/fsnotify#130, fsnotify fails to work correctly (or at all) in arm64, ppc64 and ppc64el.

This was preventing prometheus to be accepted in Debian testing, so while this is solved upstream, I hacked together a patch to disable fsnotify and rely only on refresh intervals in those architectures. You might want to consider applying something similar, so prom keeps working.

[fabxc]

That seems sane 👍

On Tue, Mar 29, 2016, 3:14 AM Martín Ferrari notifications@github.com
wrote:

Hi,

As noted in bug fsnotify/fsnotify#130
fsnotify/fsnotify#130, fsnotify fails to work
correctly (or at all) in arm64, ppc64 and ppc64el.

This was preventing prometheus to be accepted in Debian testing, so while
this is solved upstream, I hacked together a patch to disable fsnotify
and rely only on refresh intervals in those architectures. You might want
to consider applying something similar, so prom keeps working.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1507

[TheTincho]

As a data point, the new Debian release with this patch applies compiles and passes tests in all arches: https://buildd.debian.org/status/package.php?p=prometheus

[brian-brazil]

Do you want to send on a PR with that patch?

[TheTincho]

Sure, will do.

I see the fsnotify people are moving to fix this issue, but it might take a while, as it might involve getting fixes into golang itself.

[TheTincho]

Done.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.