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

Update the Readme to give a short description of bazel. #1

Closed
wants to merge 3 commits into from

Conversation

ulfjack
Copy link
Contributor

@ulfjack ulfjack commented Jun 16, 2014

No description provided.

@@ -1 +1 @@
Bazel.
Bazel - a scalable build tool that supports hermetic, reproducible builds.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not eloquent enough. Try harder.

@ulfjack
Copy link
Contributor Author

ulfjack commented Jun 16, 2014

How about this?

@ulfjack ulfjack closed this Jun 16, 2014
@ulfjack ulfjack reopened this Jun 16, 2014
@ulfjack ulfjack closed this Sep 30, 2014
@ulfjack ulfjack deleted the update-readme branch September 30, 2014 19:52
@ulfjack ulfjack mentioned this pull request Mar 27, 2015
bazel-io pushed a commit that referenced this pull request May 4, 2016
Add dagger to third_party in preparation for an upcoming conversion
of the junit test runner from Guice to Dagger.

Part #1: without the BUILD file (needs a separate change)

Change-Id: Idae2182c491e01d2f0b5e852a5314e65624592c6
@linrio linrio mentioned this pull request Feb 3, 2017
copybara-service bot pushed a commit that referenced this pull request Mar 14, 2023
*** Reason for rollback ***

Breaks builds internally.

*** Original change description ***

Move Apple toolchain setup to apple_support

This moves the CC toolchain for building Apple platforms besides macOS to the apple_support repo bazelbuild/apple_support#113

The default unix toolchain is now used if someone wants to build for macOS without the apple_support toolchain, but it doesn't handle as many platform specific features as the previous toolchain.

Fixes #1...

***

PiperOrigin-RevId: 516486823
Change-Id: If9b2542699cf8704e0a511e684d8519468ddd937
fweikert pushed a commit to fweikert/bazel that referenced this pull request May 25, 2023
*** Reason for rollback ***

Breaks builds internally.

*** Original change description ***

Move Apple toolchain setup to apple_support

This moves the CC toolchain for building Apple platforms besides macOS to the apple_support repo bazelbuild/apple_support#113

The default unix toolchain is now used if someone wants to build for macOS without the apple_support toolchain, but it doesn't handle as many platform specific features as the previous toolchain.

Fixes bazelbuild#1...

***

PiperOrigin-RevId: 516486823
Change-Id: If9b2542699cf8704e0a511e684d8519468ddd937
copybara-service bot pushed a commit that referenced this pull request Oct 10, 2023
… order.

1. `TestAttempt` events would wait for the `TargetCompleteEvent` to be posted before being posted.

2. There was an implicit requirement for the `TestAttempt` events to be posted in a specific order.

3. This didn't break in the noskymeld case because we fulfilled this ordering by using the order of performing the attempts themselves. The sequence would look like:
    + post `TargetCompleteEvent`
    -> perform attempt #1
    -> post `TestAttempt` #1
    -> perform attempt #2
    -> post `TestAttempt` #2

4. With skymeld, however, it could happen like this:

    + defer `TargetCompleteEvent` to wait for `CoverageActionFinishedEvent`
    + perform attempt #1 -> defer posting `TestAttempt` #1 & wait for `TargetCompleteEvent`
    + perform attempt #2 -> defer posting `TestAttempt` #2 & wait for `TargetCompleteEvent`
    + `CoverageActionFinishedEvent` -> release & post `TargetCompleteEvent`
    + `TargetCompleteEvent` -> release & post `TestAttempt` #2
    + `TargetCompleteEvent` -> release & post `TestAttempt` #1

Due to (2), the undefined ordering in (4) would cause an issue.

This CL fixes that by ensuring a FIFO ordering of the deferred events.

PiperOrigin-RevId: 572165337
Change-Id: Iac4d023d946865b8b81f15b119417192dc4b5c53
hvadehra added a commit that referenced this pull request Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants