c/ooni-probe-cli
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
638acb0830
ooni-probe-cli/.github/workflows/debianrepo.yml

39 lines
947 B
YAML
Raw Normal View History

feat: make sure our debian repo is WAI (#351) We want to be sure it's working for all the supported archs. See https://github.com/ooni/probe/issues/1484
2021-05-19 14:12:33 +02:00
# debianrepo ensures we can install on debian with the official build instructions
fix(ci): use correct rule name for debianrepo workflow (#550) See https://github.com/ooni/probe/issues/1840
2021-10-21 11:04:27 +02:00
name: debianrepo
feat: make sure our debian repo is WAI (#351) We want to be sure it's working for all the supported archs. See https://github.com/ooni/probe/issues/1484
2021-05-19 14:12:33 +02:00
on:
push:
branches:
fix(ci/debianrepo): avoid running docker arm64 (#551) The issue at https://github.com/ooni/probe/issues/1741 is that running `docker --platform linux/arm64` segfaults when running `sudo apt-get update -q` inside the `arm64` docker environment. As far as the `debianrepo` rule is concerned, we can fix the issue by taking advantage of Debian multi-arch. We now configure Debian multi-arch and install the package inside a `debian:stable` environment. We keep using docker. In principle we could not. But the Ubuntu environment provided by GitHub actions does not support multi-arch for arm. Also, I'd like testing this rule to be possible also locally (where I don't have Debian).
2021-10-21 16:55:00 +02:00
- "stable"
ci: master only runs coverage and only with go1.17 (+ fix flaky test) (#452) * fix: disable debianrepo build on master branch This just mitigates https://github.com/ooni/probe/issues/1741 and does not fully address it, but I'd rather avoid delving into this problem until I open a release/v3.11.0 branch and have to really fix this issue. * fix: only run coverage using go1.17 This is the version of Go with which we are going to bless v3.11.0 therefore it's the only version of Go that matters. Reference issue: https://github.com/ooni/probe/issues/1738. * fix(ptx/obfs4_test.go): avoid context-vs-normal-code race We want to test whether we get the context failure if the error generated inside normal code happens _after_ the context cancellation. The best way to do that is to write code that is not racy. To this end, we just need to pause normal code until we know that the context has returned to the caller. We also need to ensure we do not leak a goroutine, hence we use a WaitGroup to check that. Fixes https://github.com/ooni/probe/issues/1750
2021-09-05 12:44:44 +02:00
- "release/**"
fix(ci/debianrepo): avoid running docker arm64 (#551) The issue at https://github.com/ooni/probe/issues/1741 is that running `docker --platform linux/arm64` segfaults when running `sudo apt-get update -q` inside the `arm64` docker environment. As far as the `debianrepo` rule is concerned, we can fix the issue by taking advantage of Debian multi-arch. We now configure Debian multi-arch and install the package inside a `debian:stable` environment. We keep using docker. In principle we could not. But the Ubuntu environment provided by GitHub actions does not support multi-arch for arm. Also, I'd like testing this rule to be possible also locally (where I don't have Debian).
2021-10-21 16:55:00 +02:00
- "master"
- "debianrepo"
feat: make sure our debian repo is WAI (#351) We want to be sure it's working for all the supported archs. See https://github.com/ooni/probe/issues/1484
2021-05-19 14:12:33 +02:00
jobs:
test_386:
runs-on: "ubuntu-20.04"
steps:
- uses: actions/checkout@v2
fix(ci/debianrepo): avoid running docker arm64 (#551) The issue at https://github.com/ooni/probe/issues/1741 is that running `docker --platform linux/arm64` segfaults when running `sudo apt-get update -q` inside the `arm64` docker environment. As far as the `debianrepo` rule is concerned, we can fix the issue by taking advantage of Debian multi-arch. We now configure Debian multi-arch and install the package inside a `debian:stable` environment. We keep using docker. In principle we could not. But the Ubuntu environment provided by GitHub actions does not support multi-arch for arm. Also, I'd like testing this rule to be possible also locally (where I don't have Debian).
2021-10-21 16:55:00 +02:00
- run: sudo ./E2E/debian.sh docker i386
- run: sudo cat DEBIAN_INSTALLED_PACKAGE.txt
feat: make sure our debian repo is WAI (#351) We want to be sure it's working for all the supported archs. See https://github.com/ooni/probe/issues/1484
2021-05-19 14:12:33 +02:00
test_amd64:
runs-on: "ubuntu-20.04"
steps:
- uses: actions/checkout@v2
fix(ci/debianrepo): avoid running docker arm64 (#551) The issue at https://github.com/ooni/probe/issues/1741 is that running `docker --platform linux/arm64` segfaults when running `sudo apt-get update -q` inside the `arm64` docker environment. As far as the `debianrepo` rule is concerned, we can fix the issue by taking advantage of Debian multi-arch. We now configure Debian multi-arch and install the package inside a `debian:stable` environment. We keep using docker. In principle we could not. But the Ubuntu environment provided by GitHub actions does not support multi-arch for arm. Also, I'd like testing this rule to be possible also locally (where I don't have Debian).
2021-10-21 16:55:00 +02:00
- run: sudo ./E2E/debian.sh docker amd64
- run: sudo cat DEBIAN_INSTALLED_PACKAGE.txt
feat: make sure our debian repo is WAI (#351) We want to be sure it's working for all the supported archs. See https://github.com/ooni/probe/issues/1484
2021-05-19 14:12:33 +02:00
test_arm:
runs-on: "ubuntu-20.04"
steps:
- uses: actions/checkout@v2
fix(ci/debianrepo): avoid running docker arm64 (#551) The issue at https://github.com/ooni/probe/issues/1741 is that running `docker --platform linux/arm64` segfaults when running `sudo apt-get update -q` inside the `arm64` docker environment. As far as the `debianrepo` rule is concerned, we can fix the issue by taking advantage of Debian multi-arch. We now configure Debian multi-arch and install the package inside a `debian:stable` environment. We keep using docker. In principle we could not. But the Ubuntu environment provided by GitHub actions does not support multi-arch for arm. Also, I'd like testing this rule to be possible also locally (where I don't have Debian).
2021-10-21 16:55:00 +02:00
- run: sudo ./E2E/debian.sh docker armhf
- run: sudo cat DEBIAN_INSTALLED_PACKAGE.txt
feat: make sure our debian repo is WAI (#351) We want to be sure it's working for all the supported archs. See https://github.com/ooni/probe/issues/1484
2021-05-19 14:12:33 +02:00
fix(ci/debianrepo): avoid running docker arm64 (#551) The issue at https://github.com/ooni/probe/issues/1741 is that running `docker --platform linux/arm64` segfaults when running `sudo apt-get update -q` inside the `arm64` docker environment. As far as the `debianrepo` rule is concerned, we can fix the issue by taking advantage of Debian multi-arch. We now configure Debian multi-arch and install the package inside a `debian:stable` environment. We keep using docker. In principle we could not. But the Ubuntu environment provided by GitHub actions does not support multi-arch for arm. Also, I'd like testing this rule to be possible also locally (where I don't have Debian).
2021-10-21 16:55:00 +02:00
test_arm64:
feat: make sure our debian repo is WAI (#351) We want to be sure it's working for all the supported archs. See https://github.com/ooni/probe/issues/1484
2021-05-19 14:12:33 +02:00
runs-on: "ubuntu-20.04"
steps:
- uses: actions/checkout@v2
fix(ci/debianrepo): avoid running docker arm64 (#551) The issue at https://github.com/ooni/probe/issues/1741 is that running `docker --platform linux/arm64` segfaults when running `sudo apt-get update -q` inside the `arm64` docker environment. As far as the `debianrepo` rule is concerned, we can fix the issue by taking advantage of Debian multi-arch. We now configure Debian multi-arch and install the package inside a `debian:stable` environment. We keep using docker. In principle we could not. But the Ubuntu environment provided by GitHub actions does not support multi-arch for arm. Also, I'd like testing this rule to be possible also locally (where I don't have Debian).
2021-10-21 16:55:00 +02:00
- run: sudo ./E2E/debian.sh docker arm64
- run: sudo cat DEBIAN_INSTALLED_PACKAGE.txt
Reference in New Issue Copy Permalink