Skip to content

cpu-o3: consider rename in worst-case scenario (#305) #445

cpu-o3: consider rename in worst-case scenario (#305)

cpu-o3: consider rename in worst-case scenario (#305) #445

Triggered via push March 3, 2025 02:49
Status Failure
Total duration 1h 48m 54s
Artifacts

gem5.yml

on: push
XS-GEM5 - Running test checkpoints
1h 48m
XS-GEM5 - Running test checkpoints
XS-GEM5 - Check memory corruption
25m 7s
XS-GEM5 - Check memory corruption
XS-GEM5 - Test new simulation script on RV64GCB
18m 48s
XS-GEM5 - Test new simulation script on RV64GCB
XS-GEM5 - Test new simulation script on RV64GCBV
15m 55s
XS-GEM5 - Test new simulation script on RV64GCBV
XS-GEM5 - Test Multi-core + RV64GCB
3m 29s
XS-GEM5 - Test Multi-core + RV64GCB
XS-GEM5 - Check difftest
3m 20s
XS-GEM5 - Check difftest
XS-GEM5 - Test fix L2TLB bugs
20m 56s
XS-GEM5 - Test fix L2TLB bugs
XS-GEM5 - Test new simulation script on RV64GCBH
21m 56s
XS-GEM5 - Test new simulation script on RV64GCBH
Fit to window
Zoom out
Zoom in

Annotations

1 error
XS-GEM5 - Test Multi-core + RV64GCB
Process completed with exit code 139.