Failing tests about ansible-node-exporter HOT 7 CLOSED

Should be fixed by recent migration to molecule v3 and ditching tox. If this is still an issue please reopen.

from ansible-node-exporter.

What is the environment for test execution?

from ansible-node-exporter.

CentOS8

from ansible-node-exporter.

I remember that essentially the Docker in Docker failed because of the filesystem

Tests are not aimed to be run with DinD, that's one of the reasons behind using tox. How to run tests is described already in readme at https://github.com/cloudalchemy/ansible-node-exporter#local-testing

Or it's buggy Docker?

Maybe. However, if you start any container and you are able to write to /tmp in it, then it is fine.

Or it's Travis-CI.

Travis CI works. We schedule VM-per-ansible version, inside VM we launch molecule tests where each target is separate docker container.

Should we try to fix this?

If running tox inside a clean repository doesn't work, then yes. If it works, then I don't see any bug.

from ansible-node-exporter.

https://travis-ci.com/github/cloudalchemy/ansible-node-exporter/jobs/363897218

from ansible-node-exporter.

Not sure what happened there. Any idea how to fix?

from ansible-node-exporter.

This is some sort of flakiness in molecule itself. I have no solution apart from hitting "restart job"

from ansible-node-exporter.