trufflesuite / truffle-teams

Continuous Integration for your Truffle Project
https://truffleframework.com/teams
13 stars 5 forks source link

Error: shutting down the container failed #6

Closed 4math2379 closed 4 years ago

4math2379 commented 5 years ago

Hello ,

Since 2 days i got this timeout issue , on my Test Smartcontract.

Even locally with Ganache i got the same error.

This is my repo : git@github.com:4math2379/Wallet101.git

Thanks for any path for resolve this :)

the log from the TruffleTeam cli :

truffle-teams-ci: Build Number: 2064e6a7-6035-4cf6-b114-c11217aaa938 added to queue...

truffle-teams-ci: Build request starting...

truffle-teams-ci: Executing build command `mkdir -p /home/builduser/workingdir`

truffle-teams-ci: Executing build command `git clone https://github.com/4math2379/Wallet101.git repo`

Cloning into 'repo'...
Checking out files: 100% (6754/6754), done.

truffle-teams-ci: Executing build command `git fetch origin 8057fef8b9a7c630072db54dcbc592cfe8d9c315`

From https://github.com/4math2379/Wallet101
* branch 8057fef8b9a7c630072db54dcbc592cfe8d9c315 -> FETCH_HEAD

truffle-teams-ci: Executing build command `git -c advice.detachedHead=false checkout FETCH_HEAD`

HEAD is now at 8057fef test

truffle-teams-ci: Executing build command `npm install`

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

audited 33667 packages in 5.686s
found 1 low severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details

truffle-teams-ci: Executing build command `[ -f ./truffle.js ] && mv ./truffle.js ./truffle-config.js ; mv ./truffle-config.js ./__t2_truffle-configuration_.js ; echo "module.exports = Object.assign({}, require("'"./__t2_truffle-configuration_.js"'"), {networks: {}});" > ./truffle-config.js `

truffle-teams-ci: Executing build command `npx truffle compile`

Compiling your contracts...
===========================
> Compiling ./contracts/Migrations.sol
> Compiling ./contracts/wallet101.sol
> Compiling ./../../../../openzeppelin-solidity/contracts/math/SafeMath.sol
> Compiling ./../../../../openzeppelin-solidity/contracts/token/ERC20/ERC20.sol
> Compiling ./../../../../openzeppelin-solidity/contracts/token/ERC20/IERC20.sol
> Artifacts written to /home/builduser/workingdir/repo/build/contracts
> Compiled successfully using:
- solc: 0.5.0+commit.1d4f565a.Emscripten.clang

truffle-teams-ci: Executing build command `npx truffle test`

Using network 'test'.

Compiling your contracts...
===========================

ERROR: A caught error when processing your build request occured. The error was:
Error: shutting down the container failed
mikeseese commented 5 years ago

Hey @4math2379! Thanks for using Truffle Teams, and thanks for reporting this issue!

We are aware of the error you're getting:

ERROR: A caught error when processing your build request occured. The error was:
Error: shutting down the container failed

We've been monitoring this happening and have an internal issue to hopefully fix this soon!

As far as how you're getting the same error with Ganache:

Even locally with Ganache i got the same error.

I'm not sure how you could be getting this error locally on Ganache, as the error is specific to Truffle Teams

Lastly, I noticed you're hardcoding a mnemonic in your truffle-config.js. Make sure that you don't use this mnemonic for Mainnet or use it in the future for anything with real Ether. To use a mnemonic without hardcoding it (it's fine for testnets I guess), you need to add it as an environment variable and reference it as process.env.MNEMONIC (or whatever the name of the variable is when you set it).

4math2379 commented 5 years ago

ok thanks .

For the Mnemonic, i use it only for testnet and Ropsten. It is a faucet Metamask. i will test this env for it .

Thanks you

mikeseese commented 5 years ago

Going to keep this issue open as it is still an issue

mikeseese commented 4 years ago

We swapped out our containerization technology, so this issue no longer appears. Thanks again for reporting this!