2015-11-04 00:33:03 +08:00
|
|
|
sudo: false
|
2014-11-05 01:50:47 +08:00
|
|
|
|
2017-02-08 11:20:04 +08:00
|
|
|
language: rust
|
|
|
|
|
|
|
|
|
|
rust:
|
|
|
|
|
- stable
|
|
|
|
|
- beta
|
|
|
|
|
- nightly
|
|
|
|
|
|
|
|
|
|
matrix:
|
|
|
|
|
allow_failures:
|
|
|
|
|
- rust: nightly
|
|
|
|
|
|
|
|
|
|
addons:
|
|
|
|
|
apt:
|
2017-03-04 04:15:54 +08:00
|
|
|
packages: # recommanded versions for rust-bindgen
|
2017-02-08 11:20:04 +08:00
|
|
|
- llvm-3.9-dev
|
|
|
|
|
- libclang-3.9-dev
|
2017-10-24 16:54:48 +08:00
|
|
|
- libsqlcipher-dev
|
2017-02-08 11:20:04 +08:00
|
|
|
|
2017-03-04 04:15:54 +08:00
|
|
|
env: # specify the clang path for rust-bindgen
|
2017-02-08 11:20:04 +08:00
|
|
|
- LIBCLANG_PATH=/usr/lib/llvm-3.9/lib
|
|
|
|
|
|
2014-11-05 00:37:40 +08:00
|
|
|
script:
|
2017-02-08 11:20:04 +08:00
|
|
|
- cargo build
|
|
|
|
|
- cargo build --features bundled
|
2017-10-24 16:54:48 +08:00
|
|
|
- cargo build --features sqlcipher
|
2017-02-08 11:20:04 +08:00
|
|
|
- cargo test
|
|
|
|
|
- cargo test --features backup
|
|
|
|
|
- cargo test --features blob
|
2017-02-09 10:41:34 +08:00
|
|
|
- cargo test --features functions
|
2017-04-26 02:58:22 +08:00
|
|
|
- cargo test --features hooks
|
2017-02-08 11:20:04 +08:00
|
|
|
- cargo test --features limits
|
|
|
|
|
- cargo test --features load_extension
|
|
|
|
|
- cargo test --features trace
|
|
|
|
|
- cargo test --features chrono
|
|
|
|
|
- cargo test --features serde_json
|
|
|
|
|
- cargo test --features bundled
|
2017-10-24 16:54:48 +08:00
|
|
|
- cargo test --features sqlcipher
|
Add a feature for storing i128 as blobs.
This is behind the `i128_blob` feature.
Blobs are stored as 16 byte big-endian values, with their most significant bit
flipped. This is so that sorting, comparison, etc all work properly, even with
negative numbers. This also allows the representation to be stable across
different computers.
It's possible that the `FromSql` implementation should handle the case that the
real value is stored in an integer. I didn't do this, but would be willing to
make the change. I don't think we should store them this way though, since I
don't think users would be able to sort/compare them sanely.
Support for `u128` is not implemented, as comparison with i128 values would work
strangely. This also is consistent with `u64` not being allowed, not that I
think that would be reason enough on it's own.
The `byteorder` crate is used if this feature is flipped, as it's quite small
and implements things more or less optimally. If/when `i128::{to,from}_be_bytes`
gets stabilized (https://github.com/rust-lang/rust/issues/52963), we should
probably use that instead.
2018-10-09 03:04:07 +08:00
|
|
|
- cargo test --features i128_blob
|
2018-03-24 17:15:10 +08:00
|
|
|
- cargo test --features "unlock_notify bundled"
|
2018-08-31 03:15:38 +08:00
|
|
|
- cargo test --features "array bundled csvtab vtab"
|
2018-05-01 04:02:14 +08:00
|
|
|
- cargo test --features "backup blob chrono csvtab functions hooks limits load_extension serde_json trace vtab"
|
|
|
|
|
- cargo test --features "backup blob chrono csvtab functions hooks limits load_extension serde_json trace vtab buildtime_bindgen"
|
|
|
|
|
- cargo test --features "backup blob chrono csvtab functions hooks limits load_extension serde_json trace vtab bundled"
|
|
|
|
|
- cargo test --features "backup blob chrono csvtab functions hooks limits load_extension serde_json trace vtab bundled buildtime_bindgen"
|
