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

Test or_later formula changes. #20

Merged
merged 1 commit into from
Nov 6, 2016
Merged

Test or_later formula changes. #20

merged 1 commit into from
Nov 6, 2016

Conversation

MikeMcQuaid
Copy link
Member

When the diff contains an or_later bottle change then don’t try to
build the bottle but just install it and test it that way.

CC @ilovezfs for thoughts.

When the diff contains an `or_later` bottle change then don’t try to
build the bottle but just install it and test it that way.
@ilovezfs
Copy link
Contributor

ilovezfs commented Nov 6, 2016

It seems like it should be using json merges rather than manually editing bottle blocks, which we've emphasized as verboten.

@MikeMcQuaid
Copy link
Member Author

Can you elaborate more on "json merges"? In the short-term: do you object to this approach to verify if this is going to work for us? Happy to iterate on the workflow if it proves annoying but would be good to be able to use this for some more Sierra bottles temporarily.

@MikeMcQuaid
Copy link
Member Author

Yeh, I see. In this case I think although it's different it's a feature because it doesn't require us to rebuild/reupload the bottle.

@ilovezfs
Copy link
Contributor

ilovezfs commented Nov 6, 2016

I don't think we'd need to rebuild/reupload to go through brew pull for this.

In the short-term: do you object to this approach to verify if this is going to work for us?

As long as (A) we know the build fails on 10.12 and (B) the bottle goes through CI in some form before getting an or_later stamp, I think whatever works is fine in the short-run.

But I'd prefer to see these go through brew pull / git push, no upload/download of bottles involved, and the commit be attributed to test-bot not a maintainer.

@MikeMcQuaid
Copy link
Member Author

As long as (A) we know the build fails on 10.12 and (B) the bottle goes through CI in some form before getting an or_later stamp, I think whatever works is fine in the short-run.

Yep, this will allow us to do this.

But I'd prefer to see these go through brew pull / git push, no upload/download of bottles involved, and the commit be attributed to test-bot not a maintainer.

I'd rather avoid modifying e.g. brew pull for this weird case if not necessary.

@MikeMcQuaid MikeMcQuaid merged commit 1cbad4f into Homebrew:master Nov 6, 2016
@MikeMcQuaid MikeMcQuaid deleted the test-or-later branch November 6, 2016 15:49
@ilovezfs
Copy link
Contributor

ilovezfs commented Nov 6, 2016

I'd rather avoid modifying e.g. brew pull for this weird case if not necessary.

I think it depends how many we're talking about. Given there are 65 left on Homebrew/homebrew-core#6408 and maybe at most 1/4th of them actually need this right now, it's probably moot for the time being.

maxim-belkin pushed a commit to maxim-belkin/homebrew-test-bot that referenced this pull request May 12, 2017
…w#20)

This reverts commit e9ba0af.

Do not install gcc on TravisCI.
GCC 5 is not ABI compatible with GCC 4.8, and
GCC 4.8 is used to build bottles for Linuxbrew.
@lock lock bot added the outdated label Jan 18, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants