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
Example-ORMs pulls files from 3rd party vendors on every CI run, and fails if upstream is unavailable #52342
Labels
A-testing
Testing tools and infrastructure
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
S-3-productivity
Severe issues that impede the productivity of CockroachDB developers.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
Comments
knz
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
C-test-failure
Broken test (automatically or manually discovered).
S-3-productivity
Severe issues that impede the productivity of CockroachDB developers.
A-testing
Testing tools and infrastructure
labels
Aug 4, 2020
knz
changed the title
Example-ORMs pulls files from 3rd party vendors on every CI run
Example-ORMs pulls files from 3rd party vendors on every CI run, and fails if upstream is unavailable
Aug 4, 2020
Example failure:
|
Here's another:
|
This could be resolved by the idea here: #59437 |
Funnily that's what we already do for all the crdb tests in pkg/acceptance, there's an acceptance test image with a bunch of languages/drivers. Maybe we can add to that? |
rafiss
added
the
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
label
May 12, 2021
6 tasks
rafiss
removed
the
C-test-failure
Broken test (automatically or manually discovered).
label
Jun 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-testing
Testing tools and infrastructure
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
S-3-productivity
Severe issues that impede the productivity of CockroachDB developers.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
The Java tests in the Examples-ORMs pull their dependencies from repo.maven.apache.org upon every run.
The Python tests pull their dependencies from pipy servers.
And so on.
This is happening on every run. The files are not cached
This is causing unnecessary ingress costs on our side, and expensive egress cost on the side of 3rd party.
Lately we've had an uptick of failures due to the upstream server refusing our requests. (I wouldn't blame them personally, from their perspective we're an impolite leecher with a missing/incorrect proxy config.)
This is really a variation of #51543, with the problem focused on Examples-ORMs instead of the cdc roachtests.
Jira issue: CRDB-3960
The text was updated successfully, but these errors were encountered: