Skip to content

Conversation

@ktf
Copy link
Member

@ktf ktf commented Apr 2, 2025

No description provided.

@ktf ktf requested a review from a team as a code owner April 2, 2025 11:18
@github-actions
Copy link
Contributor

github-actions bot commented Apr 2, 2025

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

@alibuild
Copy link
Collaborator

alibuild commented Apr 2, 2025

Error while checking build/O2/fullCI_slc9 for e313097 at 2025-04-02 18:00:

## sw/BUILD/O2Physics-latest/log
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:


## sw/BUILD/O2-sim-challenge-test-latest/log
./sim-challenge.logDetected critical problem in logfile mftmchMatch.log
./sim-challenge.logmftmchMatch.log:[18218:internal-dpl-ccdb-backend]: [18:00:20][ERROR] Exception while running: Fatal error. Rethrowing.
./sim-challenge.logmftmchMatch.log-[18218:internal-dpl-ccdb-backend]: [18:00:20][FATAL] Unhandled o2::framework::runtime_error reached the top of main of o2-globalfwd-matcher-workflow, device shutting down. Reason: Fatal error
./sim-challenge.log[18218:internal-dpl-ccdb-backend]: [18:00:19][ERROR] CCDBDownloader CURL transfer error - Timeout was reached
./sim-challenge.log[18218:internal-dpl-ccdb-backend]: [18:00:19][ERROR] CcdbDownloader finished transfer http://alice-ccdb.cern.ch/MFT/Config/AlpideParam for 1546300800000 (agent_id: alimetal04.cern.ch-1743609613-h151Pl) with http code: 0
./sim-challenge.log[18218:internal-dpl-ccdb-backend]: [18:00:19][ERROR] File MFT/Config/AlpideParam could not be retrieved. No more hosts to try.
./sim-challenge.log[18218:internal-dpl-ccdb-backend]: [18:00:19][FATAL] Unable to find CCDB object MFT/Config/AlpideParam/1546300800000
./sim-challenge.log[18218:internal-dpl-ccdb-backend]: [18:00:20][ERROR] Exception while running: Fatal error. Rethrowing.
./sim-challenge.log[18218:internal-dpl-ccdb-backend]: [18:00:20][FATAL] Unhandled o2::framework::runtime_error reached the top of main of o2-globalfwd-matcher-workflow, device shutting down. Reason: Fatal error
./sim-challenge.log[ERROR] Workflow crashed - PID 18218 (internal-dpl-ccdb-backend) did not exit correctly however it's not clear why. Exit code forced to 128.
./sim-challenge.log[ERROR]  - Device internal-dpl-ccdb-backend: pid 18218 (exit 128)
./sim-challenge.log[INFO]    - First error: [18:00:19][FATAL] Unable to find CCDB object MFT/Config/AlpideParam/1546300800000
./sim-challenge.log[ERROR] SEVERE: Device internal-dpl-ccdb-backend (18218) had at least one message above severity 7: Unable to find CCDB object MFT/Config/AlpideParam/1546300800000
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/43}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/45}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/46}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/47}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/48}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/49}
./digi.log[5898:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./digi.log[5898:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./digi.log[5898:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./digi.log[5898:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
[0 more errors; see full log]

Full log here.

@ktf ktf merged commit a3163d2 into AliceO2Group:dev Apr 3, 2025
11 of 12 checks passed
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