search

JuliaCI / julia-buildbot

Buildbot configuration for build.julialang.org
MIT License
19 stars 14 forks source link

Separated testing #75

Closed staticfloat closed 6 years ago

staticfloat commented 6 years ago

From this change onward, package_ builders will only compile and bootstrap Julia; they will not run the tests. The compiled and boostrapped binaries are uploaded to AWS under the pretesting namespace, and are then downloaded onto separate tester_ builders. If they pass testing within the tester_builders, the binaries are then "promoted" from pretesting to the actual download URLs.

This provides a stronger guarantee of test suite correctness, as it isolates the build environment and the testing environment somewhat, and sets the stage for e.g. cross-compiling then running tests on the actual architectures.

vchuravy commented 6 years ago

I quite like this change!

On Thu, Mar 22, 2018, 21:53 Elliot Saba notifications@github.com wrote:

From this change onward, package builders will only compile and bootstrap Julia; they will not run the tests. The compiled and boostrapped binaries are uploaded to AWS under the pretesting namespace, and are then downloaded onto separate tester builders. If they pass testing within the tester_builders, the binaries are then "promoted" from pretesting to the actual download URLs.

This provides a stronger guarantee of test suite correctness, as it isolates the build environment and the testing environment somewhat, and sets the stage for e.g. cross-compiling then running tests on the actual architectures.

You can view, comment on, or merge this pull request online at:

https://github.com/JuliaCI/julia-buildbot/pull/75 Commit Summary

  • Remove old builders and code, eliminate bottling
  • Big overhaul! Separated testing!

File Changes

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JuliaCI/julia-buildbot/pull/75, or mute the thread https://github.com/notifications/unsubscribe-auth/AAI3akHv_mKa0EglhBdIDyMX3oX2VZXpks5thFWpgaJpZM4S4DZU .

staticfloat commented 6 years ago

How........ how did you reply as an email to this change? Do you get an email every time I open a PR?

ararslan commented 6 years ago

Presumably he follows the repo and receives email notifications for repos he follows.

staticfloat commented 6 years ago

I've merged this; let's keep an eye on the nightlies to make sure they are actually getting put up like we want them to be. :)

vchuravy commented 6 years ago

One thing that I was just wondering about how would one trigger a full build + test cycle? Just a forced build on the packager and the pipeline then works?

staticfloat commented 6 years ago

Yep that’s right. On Mon, Mar 26, 2018 at 23:55 Valentin Churavy notifications@github.com wrote:

One thing that I was just wondering about how would one trigger a full build + test cycle? Just a forced build on the packager and the pipeline then works?

— You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub https://github.com/JuliaCI/julia-buildbot/pull/75#issuecomment-376236066, or mute the thread https://github.com/notifications/unsubscribe-auth/AAH_aCWRkgwj6RCkNcMYtIVvdSCXu8P6ks5tiR2RgaJpZM4S4DZU .

--

-E