Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop CI testing Pkg for every PR #31774

Closed
KristofferC opened this issue Apr 19, 2019 · 4 comments · Fixed by #32287
Closed

Stop CI testing Pkg for every PR #31774

KristofferC opened this issue Apr 19, 2019 · 4 comments · Fixed by #32287
Labels
ci Continuous integration packages Package management and loading

Comments

@KristofferC
Copy link
Member

Pkg has tests that semi-frequently fails due to connection issues and we are already running CI on Pkg on its own repo so double running it seems excessive. There is of course a risk that changes to Base breaks Pkg but we can either run the Pkg tests on the buildbots that create the nightlies so we do not upload a nightly with breaking Pkg or we can just fix it if Pkg happens to break (it will be quite obvious when that happens).

@KristofferC KristofferC added the triage This should be discussed on a triage call label Apr 19, 2019
@ararslan ararslan added packages Package management and loading ci Continuous integration labels Apr 20, 2019
@StefanKarpinski
Copy link
Member

Agree, should stop running Pkg tests on master.

@JeffBezanson
Copy link
Member

Triage is ok with this.

@StefanKarpinski StefanKarpinski removed the triage This should be discussed on a triage call label May 9, 2019
@ararslan
Copy link
Member

ararslan commented May 9, 2019

Triage is still okay with this, 2 weeks later.

@fredrikekre
Copy link
Member

I think I have a branch for this somewhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous integration packages Package management and loading
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants