Update ci_on_macos.yml (fix CI with latest mac at arm architecture)

[ftshijt]

What?

CI fix for MacOS

[ftshijt]

FYI: actions/setup-python#808

[ftshijt]

Umm, it is not as easy as I thought since some c compiling is also having issues with M1 arm...

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.32%. Comparing base (1ea3fdf) to head (a615131).
Report is 28 commits behind head on master.

❗ Current head a615131 differs from pull request most recent head f8fd91a

Please upload reports for the commit f8fd91a to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5785      +/-   ##
==========================================
- Coverage   62.77%   54.32%   -8.46%     
==========================================
  Files         153      771     +618     
  Lines       16958    70626   +53668     
==========================================
+ Hits        10646    38366   +27720     
- Misses       6312    32260   +25948     

Flag	Coverage Δ
test_integration_espnet1	?
test_python_espnet2	52.70% <ø> (?)
test_utils	20.61% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ftshijt]

Hi guys @sw005320 @kamo-naoyuki , I'm trying to fix the CI issue with MacOS but am not sure about the next move. Would be great if you have any comments:

The current issue is mostly from the change of MacOS-latest version being switched to M1 chip with arm architecture. After I change the ci test to arm architecture, two external tools start to have issues:

• We can use 2.4.12 version of SCTK to fix the issue (thanks to usnistgov/SCTK@6eebc2c ).
• The Sph2pipe however, does not have an upgrade option and the exact issue from our CI has not been fixed since this Feb [Mac OS] error: implicitly declaring library function 'strdup' robd003/sph2pipe#3 )

For the following fixes, we may think of removing sph2pipe from the default installation for MacOS test specifically (we still need it for other tests) or use our own fixed fork of the sph2pipe instead of their old release. May I ask which one you would prefer?

[sw005320]

Hi @ftshijt,
Thanks for taking care of this!

My preference is

For the following fixes, we may think of removing sph2pipe from the default installation for MacOS test specifically (we still need it for other tests)

We may need this legacy format in the Linux environment, but we don't need it for MacOS.