# Metricbeat/system cpuinfo metricset tests fail on non-amd64 platforms

**URL:** <https://discuss.elastic.co/t/metricbeat-system-cpuinfo-metricset-tests-fail-on-non-amd64-platforms/320929>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [December 9, 2022, 7:52pm UTC](https://discuss.elastic.co/t/metricbeat-system-cpuinfo-metricset-tests-fail-on-non-amd64-platforms/320929 "2022-12-09T19:52:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan\_Albrecht](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_albrecht/32/113479_2.png) [@Jonathan\_Albrecht](https://discuss.elastic.co/u/Jonathan_Albrecht)\
**Post date:** [December 9, 2022, 7:52pm UTC](https://discuss.elastic.co/t/metricbeat-system-cpuinfo-metricset-tests-fail-on-non-amd64-platforms/320929/1 "2022-12-09T19:52:37Z")

</div>

Two tests in `metricbeat/module/system/test_system.py`:

1. `test_core`
2. `test_core_with_cpu_ticks`

fail on at least arm64 and s390x because the parser for `/proc/cpuinfo` only supports linux amd64 cpuinfo file format currently. It looks like the parser is not meant to handle other platforms currently.

Could the tests be skipped for non-amd64 platforms? Or maybe the tests could filter the `proc/cpuinfo` sourced fields on non-amd64? I can file an issue if that helps.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 6, 2023, 9:52pm UTC](https://discuss.elastic.co/t/metricbeat-system-cpuinfo-metricset-tests-fail-on-non-amd64-platforms/320929/2 "2023-01-06T21:52:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.