Comments (2)
Yeah the reported time is the time it took to run the specs. Without upfront build time. I think this is fine and expected.
A spec program is just a regular Crystal program. And it can build and execute in different ways.
crystal spec
is just a convenience feature of the compiler that combines the build and run steps into a single command.
If you want the entire time it takes to run crystal spec
, using time
as a separte command seems quite reasonable.
from crystal.
If we showed both the build and run time for this command, I think it would be less confusing. I know at work the test suite for our Ruby monolith shows both file load time and spec runtime separately. That's sort of what I have in mind here.
Other than that maybe the message can be improved somewhat. Finished in X...
doesn't indicate what is being measured. Maybe Finished running specs in X...
would make more sense here.
from crystal.
Related Issues (20)
- Implement new UUID versions (V6, V7, V8) HOT 2
- Installing system dependencies in the Windows GUI installer HOT 1
- Static linking mode fails on Arch Linux HOT 8
- Compiler crash when using a TypeDeclaration in the wrong spot HOT 1
- Command prompt escaping in `Process.quote_windows` HOT 2
- Comparisons between integers and floats are inexact
- `YAML::Any#dig` does not accept a string key HOT 6
- `Math.pow` returns different results between `Int` and `Float` exponents
- Some `IO::FileDescriptor` methods are implemented in `Crystal::System::File`
- Linking against the debug MSVC runtime libraries
- Permission denied opening `libiconv.dll` HOT 1
- Another codegen error involving instance variables with `Iterator` type
- SIGBUS on AArch64 when `Proc` returns large extern struct by value
- Can't initialize a struct inside `#pre_initialize` HOT 4
- Unable to run interpreter after building HOT 2
- Using `lld-link` as a linker HOT 1
- Interpreter bug when `require "http/server"` HOT 1
- Can't instantiate a UNIXSocket instance in the interpreter HOT 2
- Some `#[]?(Range)` methods can still raise `IndexError`
- Interpreter hits Invalid memory access (after Error: BUG: no target defs) HOT 1
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 crystal.