Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[core] Set run timestamps before executing triggers with weight 0 #588

Merged
merged 3 commits into from
Jul 15, 2024

Conversation

knopers8
Copy link
Collaborator

@knopers8 knopers8 commented Jul 9, 2024

I still want to test it with TRG plugin enabled, but otherwise, it seems already OK.

@knopers8
Copy link
Collaborator Author

knopers8 commented Jul 9, 2024

It has to come with AliceO2Group/ControlWorkflows#655

teo
teo previously approved these changes Jul 9, 2024
@knopers8 knopers8 changed the title WIP [core] Set run timestamps before executing triggers with weight 0 [core] Set run timestamps before executing triggers with weight 0 Jul 15, 2024
@knopers8
Copy link
Collaborator Author

I tested it on staging with DCS, TRG, ODC, CCDB, BKP, DD, Kafka plugins enabled with a SYNTH 650kHz pp configuration. EMC, CPV, PHS, TRD detectors had to be excluded to allow for trigger to start.

I confirmed that the order of plugin execution remained the same.

I had to add one fix (delete run number after positive STOP_ACTIVITY hooks are called), which allowed CCDB RunStop to still work correctly. Otherwise, all the plugin logs remained the same as before the changes.

It's good to go as far as I am concerned.

@teo teo merged commit 7eeb30b into AliceO2Group:master Jul 15, 2024
2 checks passed
@knopers8 knopers8 deleted the timestamps-at-zero branch July 15, 2024 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants