tarpaulin: fails on travis with ASLR disable failed: EPERM

0.42s$ bash <(curl https://raw.githubusercontent.com/xd009642/tarpaulin/master/travis-install.sh)
cargo-tarpaulin
after_success.2
178.59s$ cargo tarpaulin --out Xml &&
    bash <(curl -s https://codecov.io/bash)
    
Building project
Launching test
ASLR disable failed: EPERM: Operation not permitted
thread 'main' panicked at 'Failed to trace: Sys(EPERM)', /checkout/src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.
Unexpected grab
Error while collecting coverage. EPERM: Operation not permitted
Coverage Results
#
# Omitted 
#
0.00% coverage, 0/302 lines covered
Tarpaulin finished

Travis log: https://travis-ci.org/swc-project/swc/builds/328637807#L2967

I use nightly

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 1
  • Comments: 20 (9 by maintainers)

Commits related to this issue

Most upvoted comments

I ended up using the following CircleCI configuration for textwrap:

version: 2
jobs:
  build:
    machine: true
    steps:
      - checkout
      - run:
          name: Pull xd009642/tarpaulin
          command: docker pull xd009642/tarpaulin
      - run:
          name: Generate coverage report
          command: >-
            docker run --security-opt seccomp=unconfined
            -v $PWD:/volume xd009642/tarpaulin
            cargo tarpaulin --out Xml --all-features
      - run:
          name: Upload to codecov.io
          command: bash <(curl -s https://codecov.io/bash) -Z -f cobertura.xml

This way only the cargo tarpaulin step is run in the Docker container and the whole pipeline takes about 2-3 minutes on my textwrap project.

@Marwes My understanding is that there is no solution for Travis that does not require sudo.