Skip to content

Event order update#1549

Merged
feldergast merged 4 commits intosstsimulator:develfrom
feldergast:event-order-update
Jan 26, 2026
Merged

Event order update#1549
feldergast merged 4 commits intosstsimulator:develfrom
feldergast:event-order-update

Conversation

@feldergast
Copy link
Contributor

Changing how the event ordering based on the links they were sent on. Currently it is based on the alphabetized link name, this PR moves control of ordering to the model developer by basing it on the order in which configureLink() is called. This PR leaves ordering for self links the same (they are all given the same order tag, so events with the same deliver time and priority will deliver in the order they were sent).

This is the implementation for issue #1540

NOTE: Since this PR changes some of the outputs of test reference files, we will need to force push the reference file update on Elements and then send this PR for testing.

@feldergast feldergast requested a review from gvoskuilen January 26, 2026 16:44
@feldergast feldergast self-assigned this Jan 26, 2026
@feldergast feldergast added the Major Feature A new feature that has broad impact on codebase and requires a minimum two week discussion period label Jan 26, 2026
@github-actions github-actions bot added AT: WIP Mark PR as a Work in Progress (No Autotesting Performed) AT: CLANG-FORMAT PASS and removed AT: WIP Mark PR as a Work in Progress (No Autotesting Performed) labels Jan 26, 2026
@github-actions
Copy link

CLANG-FORMAT TEST - PASSED

@feldergast feldergast added the AT: WIP Mark PR as a Work in Progress (No Autotesting Performed) label Jan 26, 2026
Copy link
Contributor

@gvoskuilen gvoskuilen left a comment

Choose a reason for hiding this comment

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

Looks good. Couple typos in comments that can be fixed in a subsequent PR if needed.

if ( clink->component[0] == ULONG_MAX ) {
output.output("WARNING: Found unused link: %s\n", clink->name.c_str());
2 - Dangling link. This happens when order == 0 and we are a nonlocal link, or when order == 0 and we are NOT
a nonlocal link
Copy link
Contributor

Choose a reason for hiding this comment

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

Comment needs fixing. Dangling link when (order == 0, nonlocal) or (order == 1, ~nonlocal)



/**
Gets the next value or the order field of the link. The ordering of events based on links will be based on
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be "Gets the next value 'for' the order field"?

@feldergast feldergast removed the AT: WIP Mark PR as a Work in Progress (No Autotesting Performed) label Jan 26, 2026
@sst-autotester
Copy link
Contributor

Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection is Not Necessary for this Pull Request.

@sst-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects:

Pull Request Auto Testing STARTING (click to expand)

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-elements

  • Build Num: 2502
  • Status: STARTED

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-elements_MR-2

  • Build Num: 2447
  • Status: STARTED

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-elements_MT-2

  • Build Num: 2445
  • Status: STARTED

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-core_Make-Dist

  • Build Num: 1047
  • Status: STARTED

Build Information

Test Name: SST__AutotestGen2_NewFW_OSX-15-XC15-ARM2_OMPI-4.1.6_PY3.10_sst-elements

  • Build Num: 995
  • Status: STARTED

Using Repos:

Repo: CORE (feldergast/sst-core)
  • Branch: event-order-update
  • SHA: 2a5ac0c
  • Mode: TEST_REPO
Repo: SQE (sstsimulator/sst-sqe)
  • Branch: devel
  • SHA: 788652510af0795d1b08ea6504761359dca32fae
  • Mode: SUPPORT_REPO
Repo: ELEMENTS (sstsimulator/sst-elements)
  • Branch: devel
  • SHA: a0733f799251e7a403f862fa58b24e17e1710c6c
  • Mode: SUPPORT_REPO
Repo: MACRO (sstsimulator/sst-macro)
  • Branch: devel
  • SHA: 489f035111339bbd94e9db661a68c1b2cd7faf77
  • Mode: SUPPORT_REPO

Pull Request Author: feldergast

@kpgriesser
Copy link
Contributor

FYI - checked that this branch is passing on TCL CI pipeline as well

@sst-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED

Pull Request Auto Testing has PASSED (click to expand)

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-elements

  • Build Num: 2502
  • Status: PASSED

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-elements_MR-2

  • Build Num: 2447
  • Status: PASSED

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-elements_MT-2

  • Build Num: 2445
  • Status: PASSED

Build Information

Test Name: SST__AutotestGen2_NewFW_sst-test_OMPI-4.1.4_PY3.9_sst-core_Make-Dist

  • Build Num: 1047
  • Status: PASSED

Build Information

Test Name: SST__AutotestGen2_NewFW_OSX-15-XC15-ARM2_OMPI-4.1.6_PY3.10_sst-elements

  • Build Num: 995
  • Status: PASSED

@sst-autotester
Copy link
Contributor

Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ gvoskuilen ]!

@sst-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Pull Request MUST BE MERGED MANUALLY BY Project Team - This Repo does not support Automerge

@feldergast feldergast merged commit 3fe2541 into sstsimulator:devel Jan 26, 2026
23 of 28 checks passed
@feldergast feldergast deleted the event-order-update branch January 26, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AT: CLANG-FORMAT PASS Major Feature A new feature that has broad impact on codebase and requires a minimum two week discussion period

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants