Arbitrum fork test keeps failing when calling `arbBlockNumber()`

[Abelaby]

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

forge 0.2.0 (de33b6a 2024-03-02T00:15:47.606546623Z)

What command(s) is the bug in?

forge test --mt

Operating System

Linux

Describe the bug

I'm getting the following error when fork testing against a deployed contract.

[0] 0x0000000000000000000000000000000000000064::arbBlockNumber() [staticcall]
    │   │   │   │   │   └─ ← EvmError: InvalidFEOpcode
    │   │   │   │   └─ ← ()
    │   │   │   └─ ← EvmError: Revert
    │   │   └─ ← EvmError: Revert
   

I believe this was briefly mentioned in issue no #5085

The issue is still persisting and would be nice if there was any solution/ workaround for this.

Thank you.

[Abelaby]

Update:

I've used vm.mockCall() to make it work for my PoC.

[xsubject]

Try <=0.8.19 solc

[zerosnacks]

Marking as duplicate of #5085

Related: #7360