Closed SaboniAmine closed 3 years ago
Could successfully test the scheduling with act. Here is the setup to reproduce :
FROM ubuntu:20.04
RUN apt-get update \
&& apt update -y \
&& apt-get upgrade -y \
&& DEBIAN_FRONTEND=noninteractive apt-get install -y \
build-essential \
curl \
nodejs \
npm \
sudo \
libsndfile1 \
&& rm -rf /var/lib/apt/lists/*
docker build . -t local/ubuntu-builder:latest
act -v schedule -P ubuntu-latest=local/ubuntu-builder:latest
Test should run 3 parallel builds at scheduled time, and 3 parallel tensorflow downloads, which could be bandwith / CPU intensive.
Merging #338 (5aa9fa1) into master (bbea923) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #338 +/- ##
=======================================
Coverage 82.89% 82.89%
=======================================
Files 13 13
Lines 2689 2689
=======================================
Hits 2229 2229
Misses 460 460
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update bbea923...5aa9fa1. Read the comment docs.
As far as I understood, scheduled build can only be activated on the workflow on the default branch, master. That means that it cannot be executed from a non-default branch, thus quite hard to reproduce (even locally, I tried with act). I propose to merge this lone update, after changing the schedule to a convenient hour, to test it live.
Another PR could be open to segregate heavy tests only for the nightly builds.