Skip to content

Conversation

jblomer
Copy link
Contributor

@jblomer jblomer commented Sep 16, 2025

No description provided.

@jblomer jblomer self-assigned this Sep 16, 2025
@jblomer jblomer force-pushed the ntuple-evolution-integral branch from 815fc64 to f3ab34a Compare September 16, 2025 21:44
Copy link

github-actions bot commented Sep 17, 2025

Test Results

    21 files      21 suites   3d 15h 56m 51s ⏱️
 3 674 tests  3 673 ✅  0 💤 1 ❌
75 342 runs  75 330 ✅ 10 💤 2 ❌

For more details on these failures, see this check.

Results for commit 643fa1e.

♻️ This comment has been updated with latest results.

@jblomer jblomer force-pushed the ntuple-evolution-integral branch 2 times, most recently from e407222 to 7bcb04d Compare September 19, 2025 08:37
@jblomer jblomer requested a review from silverweed September 19, 2025 11:04
@jblomer jblomer force-pushed the ntuple-evolution-integral branch from 7bcb04d to 49440e6 Compare September 19, 2025 12:23
@jblomer jblomer requested a review from silverweed September 19, 2025 12:32
Copy link
Member

@hahnjo hahnjo left a comment

Choose a reason for hiding this comment

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

LGTM

That would not be strictly necessary because the column representations
implictly enforce the automatic schema evolution rules for simple types.
Making this explicit though allows for better error messages and it is a
precondition to read enums into ints.
@jblomer jblomer force-pushed the ntuple-evolution-integral branch from 49440e6 to 643fa1e Compare September 24, 2025 19:30
@jblomer jblomer merged commit 12c37e4 into root-project:master Sep 25, 2025
23 of 26 checks passed
@jblomer jblomer deleted the ntuple-evolution-integral branch September 25, 2025 02:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants