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

roachtest: when building, don't run nogo #138702

Merged
merged 2 commits into from
Jan 9, 2025

Conversation

rickystewart
Copy link
Collaborator

Part of: #136626
Epic: None
Release note: None

The `ci` configuration is overloaded and is used for a few different
things. It is used in builds to enable `lintonbuild`, and it's used in
tests to set some configurations that are useful in TeamCity (increased
verbosity, etc.)

While running lints every time we build in a paranoid, repetitive
fashion does mean that lint issues cannot go unnoticed, it does have a
performance impact (see cockroachdb#136626). Going forward, we will not have this
configuration imply `lintonbuild` and provide the option to disable
`nogo` for certain builds in automation. For example, `roachtest`s will
benefit from having lints disabled as well to speed up the build.

Here, we do the following:

1. Have `--config=ci` not imply enabling lints
2. Now, `--config=ci` has no specific meaning for builds (it's only
   meaningful for tests). So, I go through all the scripts and
   automation and remove it for builds specifically.
3. Disable `nogo` for release builds to reduce the likelihood of an OOM.

Part of: cockroachdb#136626
Epic: CRDB-41952
Release note: None
Part of: cockroachdb#136626
Epic: None
Release note: None
@rickystewart rickystewart requested a review from a team as a code owner January 8, 2025 23:54
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rickystewart
Copy link
Collaborator Author

First commit is from #138698, can be ignored

Not to be merged before #138698

@rickystewart rickystewart requested review from rail and jlinder January 8, 2025 23:57
@rickystewart rickystewart added the backport-24.3.x Flags PRs that need to be backported to 24.3 label Jan 9, 2025
@rickystewart
Copy link
Collaborator Author

bors r=rail

@craig craig bot merged commit 34c96a1 into cockroachdb:master Jan 9, 2025
21 of 22 checks passed
Copy link

blathers-crl bot commented Jan 9, 2025

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 2f9e00f to blathers/backport-release-24.3-138702: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 24.3.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-24.3.x Flags PRs that need to be backported to 24.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants