CircleCI integration (abandoned due to memory limitations exceeded by steven_blocks) #174
Conversation
!/bin/sh -eo pipefail ERROR IN CONFIG FILE: [#/commands/steps] 0 subschemas matched instead of one 1. [#/commands/steps] expected type: Mapping, found: Sequence | SCHEMA: | type: object | INPUT: | - run: | name: Install deps | command: | | apt-get update -qq | apt-get install -y gcc libegl1-mesa-dev libgles2-mesa-dev 2. [#/commands/steps] expected type: String, found: Sequence | Command may be a string reference to another command
|
https://github.com/kkat0/circleci-demo/blob/master/.circleci/config.yml apt-get update -qq |
…b/apt/lists/lock - open (13: Permission denied)
|
Now it starts to compile, but fails on steven_block presumably due to it taking too long and getting killed: Compiling steven_blocks v0.0.1 (/home/circleci/project/blocks) |
|
Maybe not a timeout? https://circleci.com/gh/iceiix/stevenarella/11 same failure,
Resources: 2CPU/4096MB https://circleci.com/docs/2.0/configuration-reference/#resource_class
The default medium is 4GB, also available is medium+ (6GB), large (8GB), and xlarge (16GB), with a cost. Is this project too big for CircleCI's free tier? |
|
I do see high memory usage on my local system when building steven_blocks:
3.33 GB in rustc is kind of ridiculous, as is the time required to build. All the blocks are defined in a big hairy recursive macro. This is useful because it allows properties to be defined through code (expressions - for |
Previously, only the * and + operators were available, for 0 or more and 1 or more, respectively, so steven_blocks used * for optional tokens even though only one would be expected in most cases. Rust version 1.32.0 added a new operator, ?, for zero or one: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1320-2019-01-17 > You can now use the ? operator in macro definitions. The ? operator allows > you to specify zero or one repetitions similar to the * and + operators. rust-lang/rust#56245 Change to use ? instead of * for these optional repetitions.
Previously, only the * and + operators were available, for 0 or more and 1 or more, respectively, so steven_blocks used * for optional tokens even though only one would be expected in most cases. Rust version 1.32.0 added a new operator, ?, for zero or one: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1320-2019-01-17 > You can now use the ? operator in macro definitions. The ? operator allows > you to specify zero or one repetitions similar to the * and + operators. rust-lang/rust#56245 Change to use ? instead of * for these optional repetitions. Found this while investigating #174.
Previously, only the * and + operators were available, for 0 or more and 1 or more, respectively, so steven_blocks used * for optional tokens even though only one would be expected in most cases. Rust version 1.32.0 added a new operator, ?, for zero or one: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1320-2019-01-17 > You can now use the ? operator in macro definitions. The ? operator allows > you to specify zero or one repetitions similar to the * and + operators. rust-lang/rust#56245 Change to use ? instead of * for these optional repetitions. Found this while investigating #174.
|
Changing Disabled building on CircleCI for now. Buildkite is looking more attractive, building on my own systems without restrictions, but would require more work to setup the infrastructure. Also to try: https://gitlab.com/ and https://builds.sr.ht |
|
#176 builds.sr.ht - works instead of CircleCI, to use that instead. |
iceiix
changed the title
Add CircleCI for continuous integration testing (to replace Travis-CI since it is unreliable, removed #173)