System Eiger not recognized after upgrade

I have realized that Eiger is not recognized any longer after the recent system upgrade, using the updated config.py available in my fork and especially the updated folder cscs-checks in the branch alps-21.04 under my fork. The list of matched checks is empty since the system is not set in reframe.log:

$ grep SYSTEM reframe.log 
  RFM_SYSTEM=<not set>

This happened after I merged the latest ReFrame master in my fork on Friday April 23rd: I now need to add --system eiger, otherwise RFM_SYSTEM is not set, as shown above. The last commit is below, do you think there’s any change that might affect mapping uan0[2-3] to eiger? https://github.com/lucamar/reframe/commit/0ecb419edea6c3692521c97cdf3bd44b67125414

The issue occurs both with the last reframe script 3.6.0-dev.3+0ecb419e and with the one provided by the latest stable release 3.5.3 too: it does not occur if I don’t use the flag -c ~/GitHub/lucamar/reframe/cscs-checks -R with the update list of checks:

ssh eiger
ml reframe
reframe -C /users/lucamar/GitHub/lucamar/reframe/config/cscs.py -l 

[List of matched checks]
- VcSimdTest (found in '/apps/eiger/UES/jenkins/1.4.0/software/reframe/3.5.3/cscs-checks/microbenchmarks/cpu/simd/vc.py')
Found 1 check(s)

If I use the updated list of checks instead, the system is not set and the list of matched checks is empty:

ssh eiger
ml reframe
reframe -C /users/lucamar/GitHub/lucamar/reframe/config/cscs.py -c ~/GitHub/lucamar/reframe/cscs-checks -R -l

[List of matched checks]
Found 0 check(s)

I don’t know if I have introduced a regression in the checks, but the system Eiger was recognized before I merged commit 0ecb419edea6c3692521c97cdf3bd44b67125414 last Friday without setting it manually. I have compared the check vc.py:

diff -BEiyw --suppress-common-lines ~/GitHub/lucamar/reframe/cscs-checks/microbenchmarks/cpu/simd/vc.py /apps/eiger/UES/jenkins/1.4.0/software/reframe/3.5.3/cscs-checks/microbenchmarks/cpu/simd/vc.py
        if self.current_system.name in ['eiger', 'pilatus']:  |	        self.valid_prog_environs = ['builtin']
             self.valid_prog_environs = ['cpeGNU']	      <
        else:						      <
             self.valid_prog_environs = ['PrgEnv-gnu']	      <
							      <
            'module list',				      <
                'speedup': (1.32, -0.2, 0.2, '')	      <
            },						      <
            'pilatus:mc': {				      <

Any advice would be really appreciated, thanks in advance!

[vkarak]

In our case, it is now confirmed that the difference was due to how /etc/xthostname was defined. I guess we can close this issue now.

[vkarak]

Even with that config, I can’t reproduce the error:

[19:18:31] karakasv@uan02 [~/Devel/reframe][(68c78f07...)]
$ ./bin/reframe -C config/cscs.py --show-config=systems/0/name
./bin/reframe: could not initialize the graylog handler; ignoring ...
"generic"

Perhaps, there was a system change and now the /etc/xthostname is available and makes ReFrame pick this up instead of hostname as pointed out by @teojgo.