Comments (4)
Hey @monitea. This is definitely something I've been thinking about, and would be fixed by #86. The reasoning behind designing it this way is that we want to run tests in isolation, so that a command test can't do something to modify the test base for another. That said, for a number of reasons I think we should at least add the option to persist the driver between test runs, not the least of which being it would mean a huge speed increase. I'll try and set aside some time for this this week.
from container-structure-test.
Thanks for the prompt answer.
I will watch keenly for this update!
from container-structure-test.
One thing is still bothering me.
Take a look at this gist: https://gist.github.com/monitea/a7f7d4b51f514ddd90c44318d4cde356
Basically, at the moment, even if #86 is done, there will still be an issue of disk overrunning if you want to have new driver for each test.
Or am I getting things wrong here?
from container-structure-test.
Ah, great catch, you're definitely right about this. We should be calling driver.Destroy()
directly instead of deferring the call. I'll fix this
from container-structure-test.
Related Issues (20)
- Release script clobbers checksum files for built binaries
- integration of compose-like container groups
- Please provide a versioned debug image like in crane HOT 1
- Add options for condensing/expanding output when using "text" format
- Junit output time appears to be using nanoseconds instead of seconds HOT 1
- Supporting non-docker v1 manifest (format oci, v2s1, v2s2)
- Update vulnerable and old dependencies
- Kubernetes driver for command tests
- version not set correctly in homebrew binary HOT 1
- ERROR - field unboundEnv not found in type v2.MetadataTest HOT 2
- latest release is missing prebuilt binaries HOT 1
- Please provide sha256 sums for 1.13.0+
- Release 1.13.0 introduced backwards incompatibility with schema version 2.0.0 for metadataTest.env field HOT 3
- Add flag to target optional docker repo HOT 1
- Testing the existence of a directory is very slow
- Release process: use github actions and release to bazel central registry HOT 1
- container-structure-test behaves differently on two identical machines HOT 2
- Add Expected Log validation HOT 3
- How to use container_structure_test with oci_image on MacOS
- No Release asset checksums (sha256) since Release v1.11.0
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from container-structure-test.