Tests fail when defaultNetwork is set to localhost

[bitcoinbrisbane]

Im getting the following error when trying to run coverage against a base fork, with the command.

npx hardhat coverage

Error in plugin solidity-coverage: ❌ 24 test(s) failed under coverage.

hardhat config

const PK = process.env.PK;

const config: HardhatUserConfig = {
	solidity: {
		version: "0.8.19",
		settings: {
			optimizer: {
				enabled: true,
				runs: 100,
			},
			viaIR: true,
		},
	},
	defaultNetwork: "localhost",
	etherscan: {
		apiKey: {
			base: process.env.BASESCAN_API_KEY || "",
		},
		customChains: [
			{
				network: "base",
				chainId: 8453,
				urls: {
					apiURL: "https://api.basescan.org/api",
					browserURL: "https://basescan.org",
				},
			},
		],
	},
	networks: {
		base: {
			accounts: PK ? [PK] : [],
			chainId: 8453,
			url: "https://mainnet.base.org",
		},
		hardhat: {
			forking: {
				url: process.env.FORKING_URL as string,
				// blockNumber: 19197423,
				enabled: true,
			},
			chains: {
				8453: {
					hardforkHistory: {
						london: 0,
					},
				},
			},
			blockGasLimit: 60000000 // Network block gasLimit
		},
	},
};

export default config;

[cgewecke]

@bitcoinbrisbane Could you try commenting out the part of the config where you define the defaultNetwork as localhost and see if that works? (The plugin needs to run on the hardhat network).

Is the problem reproducible when running this repo and branch?

https://github.com/weweswap/contracts/tree/fix/coverage-report

[bitcoinbrisbane]

@bitcoinbrisbane Could you try commenting out the part of the config where you define the defaultNetwork as localhost and see if that works? (The plugin needs to run on the hardhat network).

Is the problem reproducible when running this repo and branch?

https://github.com/weweswap/contracts/tree/fix/coverage-report

Sure, trying now.

[bitcoinbrisbane]

Success!

[cgewecke]

I think the plugin should probably detect when there's a user-defined defaultNetwork that won't work and warn about it.

Am going to re-open just to keep track of this problem...thanks for reporting.