Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (1281421 2024-04-05T00:21:15.963758000Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Apple Silicon)
Describe the bug
On latest nightly (which we run on ci), our testing setup stopped working.
This seems to be related to #7334
On BGD we usually co-locate tests with the contracts (instead of having them in a separate directory) and then run:
forge test --match-path src/20240402_AaveV2Ethereum_UpgradeAMPLImplementation/AaveV2Ethereum_UpgradeAMPLImplementation_20240402.t.sol, where --match-path is the fully qualified path of the test.
Running the same test before and after upgrading to nightly:
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (1281421 2024-04-05T00:21:15.963758000Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Apple Silicon)
Describe the bug
On latest nightly (which we run on ci), our testing setup stopped working.
This seems to be related to #7334
On BGD we usually co-locate tests with the contracts (instead of having them in a separate directory) and then run:
forge test --match-path src/20240402_AaveV2Ethereum_UpgradeAMPLImplementation/AaveV2Ethereum_UpgradeAMPLImplementation_20240402.t.sol, where --match-path is the fully qualified path of the test.Running the same test before and after upgrading to nightly:
