acts icon indicating copy to clipboard operation
acts copied to clipboard

ci: Reenable some ExaTrkX tests

Open benjaminhuth opened this issue 1 year ago • 4 comments

These tests should work even though cugraph is not available anymore...

benjaminhuth avatar Jul 16 '24 19:07 benjaminhuth

don't let your dreams be dreams!

andiwand avatar Jul 16 '24 19:07 andiwand

📊: Physics performance monitoring for f65d721c2233ebf14c647c0d50c7654cd0df2018

Full contents

physmon summary

github-actions[bot] avatar Jul 16 '24 20:07 github-actions[bot]

Walkthrough

Reintroduced in the .gitlab-ci.yml, two test jobs are: test_exatrkx_unittests and test_exatrkx_python. Execute they do, unit tests and Python tests, upon the successful completion of the build_exatrkx job. Updated are the build_linux_ubuntu, build_exatrkx_cpu, and build_exatrkx jobs, with a refined cache key format. Modified is the addExaTrkX function in Examples/Python/python/acts/examples/reconstruction.py to include a new algorithm, PrototracksToTracks, enhancing the conversion of prototracks to tracks.

Changes

File Change Summary
.gitlab-ci.yml - Added jobs: test_exatrkx_unittests, test_exatrkx_python
- Updated jobs: build_linux_ubuntu, build_exatrkx_cpu, build_exatrkx (cache key modified)
Examples/Python/python/acts/examples/reconstruction.py - Updated addExaTrkX method signature (new parameter added)
- Introduced method: PrototracksToTracks (new algorithm)
Examples/Algorithms/TrackFindingExaTrkX/CMakeLists.txt - Added source file: src/createFeatures.cpp to library ActsExamplesTrackFindingExaTrkX
Examples/Python/tests/root_file_hashes.txt - Hash updated for: test_exatrkx[gpu-torch]__performance_track_finding.root

Possibly related PRs

  • #3886: The changes in the main PR involve the addition of test jobs related to ExaTrkX, which may be relevant to the modifications in the RootTrackSummaryWriter that enhance its functionality for handling track states and measurements, particularly in scenarios without truth information.

Suggested labels

automerge

Suggested reviewers

  • andiwand

Poem

In the CI pipeline, new tests arise,
Unittests and Python, a welcome surprise.
Prototracks to tracks, a seamless flow,
Enhancements abound, watch the progress grow!
With cache keys refined, efficiency's near,
In code we trust, our path is clear! ✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot] avatar Nov 29 '24 14:11 coderabbitai[bot]

This PR currently has a merge conflict. Please resolve this and then re-add the automerge label.

kodiakhq[bot] avatar Dec 06 '24 08:12 kodiakhq[bot]

:white_check_mark: Athena integration test results [12ea68c11818c0a95ab0687719cbda781037870c]

:white_check_mark: All tests successful

status job report
:green_circle: report_pull_request
:yellow_circle: run_workflow_tests_run4_mc
:green_circle: run_workflow_tests_run2_mc
:green_circle: run_workflow_tests_run2_data
:green_circle: run_workflow_tests_run3_mc
:green_circle: run_workflow_tests_run3_data
:green_circle: test_ActsDumpGeometryIdentifiers
:green_circle: test_ActsCheckObjectCountsWorkflowHgtd
:green_circle: test_ActsCheckObjectCountsCachedWorkflow
:green_circle: test_ActsCheckObjectCountsWorkflow
:green_circle: test_ActsEFTrackFit
:green_circle: test_ActsPersistifySeeds
:green_circle: test_ActsBenchmarkWithSpot
:green_circle: test_ActsAnalogueClustering
:green_circle: test_ActsWorkflowHeavyIons
:green_circle: test_ActsWorkflowFastTracking
:green_circle: test_ActsWorkflowCached
:green_circle: test_ActsWorkflow
:green_circle: test_ActsValidateAmbiguityResolution
:green_circle: test_ActsValidateResolvedTracks
:green_circle: test_ActsValidateTracks
:green_circle: test_ActsValidateActsCoreSpacePoints
:green_circle: test_ActsValidateActsSpacePoints
:green_circle: test_ActsValidateSeeds
:green_circle: test_ActsValidateOrthogonalSeeds
:green_circle: test_ActsValidateClusters
:green_circle: test_ActsPersistifyEDM
:green_circle: test_ActsGx2fRefitting
:green_circle: test_ActsGSFRefitting
:green_circle: test_ActsKfRefitting
:green_circle: test_ActsExtrapolationAlgTest
:green_circle: test_ActsITkTest

acts-project-service avatar Dec 06 '24 21:12 acts-project-service