Lesson 9: staging test failed

[whypam]

Hello,

I followed these steps as Patrick explained, completed first 4 steps and failed when ran the staging tests.

// 1. Get our SubId for Chainlink VRF & Fund
// 2. Deploy our contract using the SubId
// 3. Register the contract with Chainlink VRF & it's subId
// 4. Register the contract the Chainlink Keepers
// 5. Run staging tests

Error captured here:

Anything I missed?
Thanks.

[pacelliv]

Please, push the code to GitHub and share the link.

[whypam]

Thanks for catching all these and advices, and all makes sense.
Now, I'm getting timeout error because the staging test taking longer than the timeout set in hardhat.config.js. I think it's probably the testnet is getting traffic. I'll keep trying to see if it gets through finally.

But I don't understand how the timeout set in hardhat.config.js gets triggered. Not seeing the timeout being used in the code (Raffle.staging.test.js) or other places explicitly.

Any advices / insights? Thanks.

We set 500000 (500 seconds timeout in hardhat.config.js):

mocha: {
        timeout: 500000, // 500 seconds max for running tests
},

Here is the timeout error:

hardhat-smartcontract-lottery-fcc $ hh test --network goerli


  Raffle Unit Tests
    fulfillRandomWords
      1) Works with live Chainlink Keepers and Chainlink VFR, we get a random winner


  0 passing (8m)
  1 failing

  1) Raffle Unit Tests
       fulfillRandomWords
         Works with live Chainlink Keepers and Chainlink VFR, 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. 

[pacelliv]

Check on etherscan if you're entering the raffle and add console.log() like in the repo, these will help you determine in which point of the execution you're.

[whypam]

Thanks! I finally got the staging test passed. I somehow mistakenly put the entering raffle codes outside of the Promise block.

Edited: I'm going to mark this to answered and create a new thread for the timeout question because it's probably not directly causing to staging test failed.

For the timeout in hardhat.config.js:

mocha: {
        timeout: 500000, // 500 seconds max for running tests
},

How this 500 seconds got started counting when running the staging test?

Thanks.

[pacelliv]

My best guess is that Mocha literally uses a setTimeout method to call some done function after some time to end the test.

[whypam]

Just read a reply on another thread timeout setting in hardhat.config.js. I think it's along the same line.

[chopperttt]

mine still doesnt work after checking all the related threads and fixes, can someone help?
my repo: https://github.com/AnneBBB/hardhat-smartcontract-lottery-fcc