Resolve "#297 has not been merged to master (CPU 100%)" (!326) · Merge requests · nodes / rust / Duniter v2S

Status	Pipeline	Stages
Passed 00:35:14 3 months ago	fix: crash during tests #40742 326 ed05ac18	Stage: labels Stage: quality Stage: build Stage: tests Stage: deploy	Download artifacts No artifacts found
Passed 00:34:53 3 months ago	fix: crash during tests #40739 326 42013f9b	Stage: labels Stage: quality Stage: build Stage: tests Stage: deploy	Download artifacts No artifacts found
Failed 00:33:24 3 months ago	Resolve "Duniter is using 100% of one CPU core" (nodes/rust/duniter-v2s!322) #40735 326 9c259d20	Stage: labels Stage: quality Stage: build Stage: tests Stage: deploy	Download artifacts No artifacts found
1
Blocked	fix: crash during tests #40741 301-297-has-not-been-merged-to-master-cpu-100 ed05ac18	Stage: quality Stage: build Stage: tests Stage: deploy	Download artifacts No artifacts found
Blocked	fix: crash during tests #40738 301-297-has-not-been-merged-to-master-cpu-100 42013f9b	Stage: quality Stage: build Stage: tests Stage: deploy	Download artifacts No artifacts found
Blocked	Resolve "Duniter is using 100% of one CPU core" (nodes/rust/duniter-v2s!322) #40734 301-297-has-not-been-merged-to-master-cpu-100 9c259d20	Stage: quality Stage: build Stage: tests Stage: deploy	Download artifacts No artifacts found
Blocked	switch to subxt official #40733 301-297-has-not-been-merged-to-master-cpu-100 041f43e8	Stage: quality Stage: build Stage: tests Stage: deploy	Download artifacts No artifacts found

Resolve "#297 has not been merged to master (CPU 100%)"