Lesson 9 : Staging Test- Error: Timeout of 500000ms exceeded

[zulfi984]

when i run my test through rinkeby network, i got this error after some waiting

fulfillRandomWords
works with live Chainlink Keepers and Chainlink VRF, we get a random winner:
Error: Timeout of 500000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

I checked my SubscriptionId too..

[krakxn]

@alymurtazamemon I believe you resolved a similar problem?

[zulfi984]

@zulfi984 Your code is correct, just need to make sure some things that I cannot test from my side. First of all, you should check this Chronological Updates of Lesson 9 and make sure that the things are correct that are mentioned there.

And I am going to mention step by step process that you should verify, maybe this works for you and you can find issues:

1. You already have subscriptionId so make sure you have funded that (Just put 5 LINK Tokens for safety)
2. After adding subscriptionId to your helper file now make sure you have deployed it on the actual testnet (Rinkeby)
3. After deploying take that contract address from a terminal, go to the VRF website and add that address to your consumer.
4. Now make sure you have registered upkeep on the keeper's website and the same contract address is added for the upkeep address. Also, make sure you have added a gas limit 50000 and starting link balance of at least 13 LINK Tokens
5. Now run npx hardhat test --network rinkeby
6. Now until it is not passing, check some things (these may take some time), on testnet.etherscan check transactions for your contract address and see whether the enterRaffle transaction is executed or not. After that, you go keepers website and see performUpkeep is performed and the balance is deducted. After that, go to the VRF website and see if your transaction is executed successfully (should not be in a pending state).

These things will take some time so you can also increase the mocha timeout and one by one see executions on their website so you could find where actually it is stucking.

I followed all your steps and I change my timeout to 1000000(16mins).
Enter Raffle is fine, but i can't find any history in chainlink Upkeep.. so maybe it's getting stuck on upkeep..

[Mark-Four]

Hi @zulfi984,
I'm by no means an expert, just trying to help, so this is a long shot. Just adding to @alymurtazamemon's step by step troubleshooting.

1. Check if your subscription ID is correctly mentioned in the helper-hardhat-config. Also add extra test LINK just to be safe (more than 10)
2. After deploying your contract on rinkeby, make sure you copy the correct 'Deployed at ...." address from your terminal. The first time I did this I copy and pasted the wrong address in the VRF consumer registration.
3. In your hardhat config, you have copy pasted the RPC URL example from alchemy that still has the "your-api-key" at the end of the path. Even though it may never be called because you'll get the RPC URL from process.env, but I think it's still not correct.

const MAINNET_RPC_URL =
    process.env.MAINNET_RPC_URL ||
    process.env.ALCHEMY_MAINNET_RPC_URL ||
    "https://eth-mainnet.alchemyapi.io/v2/your-api-key"      -> this part here
const RINKEBY_RPC_URL =
    process.env.RINKEBY_RPC_URL || "https://eth-rinkeby.alchemyapi.io/v2/your-api-key"
const KOVAN_RPC_URL = process.env.KOVAN_RPC_URL || "https://eth-kovan.alchemyapi.io/v2/your-api-key"
const POLYGON_MAINNET_RPC_URL =
    process.env.POLYGON_MAINNET_RPC_URL || "https://polygon-mainnet.alchemyapi.io/v2/your-api-key"

4. I compared your stage test to the repo stage test and they're identical. So it's not a problem with the stage test code. Checking your helper-hardhat-config and hardhat-config now.
5. You have saveDeployments set to true for rinkeby (I don't). Could that be interfering with the test?

[zulfi984]

@alymurtazamemon @Mark-Four
I had been trying this for few days.
Enter raffle is called, and 0.1 ETH balance also deducted, but there is no history in Keepers and VRF subscription.. running until the timeout 1000000ms..

[DEFIdaniel1]

@alymurtazamemon @Mark-Four
Anyone been able to resolve? I am also experiencing this issue.

Contract deploys fine, enterRaffle works, but then the VRF/Keepers aren't triggered. No function is called, no test LINK are consumed from the contract either. Followed all the steps as well.. Seems there's an issue with calling the Keepers contract?

[paulcoffee85]

@alymurtazamemon @Mark-Four Anyone been able to resolve? I am also experiencing this issue.

Contract deploys fine, enterRaffle works, but then the VRF/Keepers aren't triggered. No function is called, no test LINK are consumed from the contract either. Followed all the steps as well.. Seems there's an issue with calling the Keepers contract?

I tried everything under the sun. Turns out I just needed to add more (12 Link to my subscription ) to my subscription.
` Raffle Staging Tests
fulfillRandomWords
Setting up test...
Entering Raffle...
WinnerPicked event fired!
✔ works with live Chainlink Keeprs and Chainlink VRF, we get a random winner (745ms)

1 passing (2s)
`

[DorianDaSilva]

@alymurtazamemon Thank you Ali! I have followed all the steps you describe above but still not working.

===============================================================================
VRF

KEEPERS

[alymurtazamemon]

@DorianDaSilva After etherscan did you check on the Keepers website and then VRF?

[DorianDaSilva]

@alymurtazamemon as per the screenshots shared above, there is no fulfillment in VRF or Keepers. The code breaks after entering Raffle once it hits the Promise bit.

@abossofmyself The repo is available in my github: https://github.com/DorianDaSilva/Raffle-SmartContract-Lottery but from previous reviews from members of the group the code seems to be fine. Problem seems to come from VRF & Keepers. (Used the contract address from deploy rinkeby to create consumer then used consumer address - same as Raffle contract - to create keepers

@Mark-Four Where do you have saveDeployments ?

[Mark-Four]

@DorianDaSilva ,
I saw saveDeployments in @zulfi984 hardhat-config, within each network's object. I haven't used that till now. Not sure what it's functionality is either.

[alymurtazamemon]

@DorianDaSilva Recently I answered someone, he has some other issues but his VRF and Keepers were working fine. So now I am sure that the issue is on your side and the thing is I can not solve this because these are a settings-related issues that only you can do.

[DorianDaSilva]

@alymurtazamemon I understand and still need to fix it so the raffle site can actually run a raffle.

I am sure there must be something wrong on my end with keepers.

1- I deploy contract on rinkeby
2- I take deployed contract from rinkeby (not mock) and create consumer using that address
3- I use the same contract address from deployed raffle on rinkeby to create keepers (custom logic option)

Maybe you could help me with a step by step or I can post a step by step here using screenshots for you to look into if you are up for it. Is that something that would work for you?

[asserules]

Didn't look through this thread carefully, but try just increasing mocha timeout in hardhat.config.js.
mocha: {
timeout: 100000000,
},
Think I had a similar problem, and this fixed it.