Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

root-project / root Public

Notifications You must be signed in to change notification settings
Fork 1.3k
Star 2.8k

Code
Issues 508
Pull requests 275
Actions
Projects 7
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Back to pull request #17288

[ntuple] allow RNTuple to emulate fields of unknown types via RecordFields #14844

Sign in to view logs

Sign in to view logs

[ntuple] allow RNTuple to emulate fields of unknown types via RecordFields

[ntuple] allow RNTuple to emulate fields of unknown types via RecordFields #14844

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

8 errors and 7 warnings

Pull Request Build: tree/ntuple/v7/test/ntuple_emulated.cxx#L64

‘RException’ does not name a type

Pull Request Build: tree/ntuple/v7/test/ntuple_emulated.cxx#L65

‘ex’ was not declared in this scope; did you mean ‘exp’?

Pull Request Build: tree/ntuple/v7/test/ntuple_emulated.cxx#L156

‘RException’ does not name a type

Pull Request Build: tree/ntuple/v7/test/ntuple_emulated.cxx#L157

‘ex’ was not declared in this scope; did you mean ‘exp’?

Pull Request Build: tree/ntuple/v7/test/ntuple_evolution.cxx#L582

‘WriteOldInFork’ was not declared in this scope

Pull Request Build: tree/ntuple/v7/test/ntuple_evolution.cxx#L705

‘WriteOldInFork’ was not declared in this scope

Pull Request Build: tree/ntuple/v7/test/ntuple_evolution.cxx#L814

‘WriteOldInFork’ was not declared in this scope

Pull Request Build

Process completed with exit code 2.

Pull Request Build: interpreter/llvm-project/clang/include/clang/AST/ExternalASTSource.h#L378

‘this’ pointer is null [-Wnonnull]

Pull Request Build: interpreter/llvm-project/clang/include/clang/AST/ExternalASTSource.h#L378

‘this’ pointer is null [-Wnonnull]

Pull Request Build: interpreter/llvm-project/clang/include/clang/AST/ExternalASTSource.h#L378

‘this’ pointer is null [-Wnonnull]

Pull Request Build: interpreter/llvm-project/clang/include/clang/AST/ExternalASTSource.h#L378

‘this’ pointer is null [-Wnonnull]

Pull Request Build: interpreter/llvm-project/clang/include/clang/AST/ExternalASTSource.h#L378

‘this’ pointer is null [-Wnonnull]

Pull Request Build: interpreter/llvm-project/clang/include/clang/AST/ExternalASTSource.h#L378

‘this’ pointer is null [-Wnonnull]

Upload test results

No files were found with the provided path: /github/home/ROOT-CI/build/TestResults.xml. No artifacts will be uploaded.

fedora41 LLVM_ENABLE_ASSERTIONS=On

fedora41 LLVM_ENABLE_ASSERTIONS=On

failed Dec 18, 2024 in 3m 23s

Loading

Re-running jobs...

You can’t perform that action at this time.