Comments (9)
Not really IMO, remember that we don't rebuild pending PRs when master changes, because it's O(NĀ² / 2)
. To still catch bugs that are caused by semantic differences (not textural ones which would cause merge conflicts), the integration branch needs to be retested.
This could indeed be done less often, e.g. daily, because the chances are low and a bit of bisecting add much complexity.
from ci.
Same goes for AppVeyor and SemaphoreCI, let's please find a common policy for all of those.
from ci.
It doesn't help anyone if no one looks at the errors which is the case at the moment.
from ci.
Yes, those would need a badge or sth. to be more visible, but someone will notice it eventually already.
from ci.
Also E-Mail notifications would be appropriate for a broken master.
from ci.
I was the only one subscribed to these mails, but I can't fix everything. For CircleCi, everyone can click on subscribe on their platform to receive such mails, but still I was the only one caring and fixing this when there was a failure a couple of days ago at Phobos.
With AppVeyor there were also a couple of random failures in the beginning.
Yes, those would need a badge or sth. to be more visible, but someone will notice it eventually already.
Already there. Also these two CIs aren't mission critical and the free resources they offer are simply not enough to rebuild master on every PR. Daily builds are enabled though.
from ci.
Also with so much frequency on GitHub and every PR merging with master a failure would immediately be discovered, but I haven't seen one case where merging to master made a difference or lead to a failure. The failures are caused by other things.
from ci.
Yes, daily build would still help to catch the rare issues that mostly happen with major refactorings. Since Kenji no longer works on the compiler, those have indeed become extremely rare.
from ci.
On Buildkite we could in theory ignore building master ("Branch limiting") - https://buildkite.com/dlang/dmd/settings/repository
from ci.
Related Issues (20)
- Automate release steps with the Buildkite release triggers HOT 1
- Prevent spurious breakage when tagging happens HOT 5
- style test relies on adjacent dmd repo being present HOT 5
- wrong version of dub is tested HOT 3
- Druntime tests depend on GDB8
- Phobos tests sometimes run out of memory
- Occasional slow network connection to Buildkite and Github from Hetzner Cloud servers HOT 4
- The automatically spawned buildkite agents should have a lower queue priority than the constant ones HOT 3
- Build druntime currently fails HOT 1
- Use custom checkouts HOT 1
- Buildkite: dub pipeline fails due to dls HOT 9
- druntime tests can fail due to not having rebuilt phobos
- Vibe.d sometimes still timeouts
- Why the hell does the style check still use dparse 0.8.8 ? HOT 4
- Update build environment to Debian 10
- Implement support for Github actions HOT 1
- `travis_get_script` should use `set -e` HOT 1
- Buildkite should ideally define TRAVIS_OS_NAME and TRAVIS_CPU_ARCH correctly HOT 1
- Add a job to check `-preview=in`
- deleteme HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
š Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ššš
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ā¤ļø Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ci.