Skip to content

Conversation

@ethanglaser
Copy link
Contributor

@ethanglaser ethanglaser commented Nov 12, 2025

Description

Avoid ChunkedEncodingError / IncompleteRead issues in CI by disabling usage of epsilon dataset


Checklist:

Completeness and readability

  • I have commented my code, particularly in hard-to-understand areas.
  • I have updated the documentation to reflect the changes or created a separate PR with updates and provided its number in the description, if necessary.
  • Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
  • I have resolved any merge conflicts that might occur with the base branch.

Testing

  • I have run it locally and tested the changes extensively.
  • All CI jobs are green or I have provided justification why they aren't.
  • I have extended testing suite if new functionality was introduced in this PR.

@ethanglaser
Copy link
Contributor Author

@david-cortes-intel
Copy link
Contributor

@razdoburdin Would it be a problem to remove this dataset?

@razdoburdin
Copy link
Collaborator

@razdoburdin Would it be a problem to remove this dataset?

it represents the xgboost cases with large histogram size not fitting in cache, but we can replace it by synthetic data or use preloaded data.

@david-cortes-intel
Copy link
Contributor

@ethanglaser Any blockers for merging this PR?

@ethanglaser
Copy link
Contributor Author

ethanglaser commented Nov 26, 2025

@ethanglaser Any blockers for merging this PR?

Last I checked there were still some issues with the job. Let's see how http://intel-ci.intel.com/f0caf58d-06da-f13b-8936-a4bf010d0e2d goes. Also I think we may need some help from Aleksei, the filters parameter does not work as intended (it always resorts to default from what I can tell)

@david-cortes-intel
Copy link
Contributor

@ethanglaser Any blockers for merging this PR?

Last I checked there were still some issues with the job. Let's see how http://intel-ci.intel.com/f0caf58d-06da-f13b-8936-a4bf010d0e2d goes. Also I think we may need some help from Aleksei, the filters parameter does not work as intended (it always resorts to default from what I can tell)

Why would the filters matter if this is removing it from the configs?

@ethanglaser
Copy link
Contributor Author

Why would the filters matter if this is removing it from the configs?

Because this is another error frequently occurring in CI benchmark jobs. In the event that there are no dataset downloading issues, the logs are littered with "cannot place on GPU device" or something like this, for the CPU jobs, and what I am seeing is that it is because that part of the filters is not actually read by infra because the field is misconfigured or mishandled.

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.

3 participants