Not sure if it's the fault of the update, but I did get this that I haven't seen before. I also don't know that the crash actually breaks/broke anythnig... I ran a container interactively, then sometime later I got the ABRT error.
"The application encountered a problem and could not continue"
"conmon killed by SIGABRT"
--- Skipping collect_GConf ---
No matching actions found for this event.
--- Skipping collect_vimrc_user ---
No matching actions found for this event.
--- Skipping collect_vimrc_system ---
No matching actions found for this event.
--- Skipping collect_xsession_errors ---
No matching actions found for this event.
--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Preparing an archive to upload
Uploading 71.1 KiB
Upload successful
Retrace job started
Analyzing crash data
.........
Generating backtrace
.................
Retrace job finished successfully
--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update has been submitted for testing by rhcontainerbot.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted conmon-2.0.23-1.fc33, and has inherited its bugs and notes.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
generally functional
works for me
This update has been submitted for stable by bodhi.
FEDORA-2021-10cc84dedc ejected from the push because 'Required tests did not pass on this update'
Not sure if it's the fault of the update, but I did get this that I haven't seen before. I also don't know that the crash actually breaks/broke anythnig... I ran a container interactively, then sometime later I got the ABRT error.
"The application encountered a problem and could not continue" "conmon killed by SIGABRT"
--- Running report_uReport --- ('report_uReport' completed successfully)
--- Skipping collect_GConf --- No matching actions found for this event.
--- Skipping collect_vimrc_user --- No matching actions found for this event.
--- Skipping collect_vimrc_system --- No matching actions found for this event.
--- Skipping collect_xsession_errors --- No matching actions found for this event.
--- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' Querying server settings Preparing an archive to upload Uploading 71.1 KiB Upload successful Retrace job started Analyzing crash data ......... Generating backtrace ................. Retrace job finished successfully
--- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has been obsoleted by conmon-2.0.25-1.fc33.