You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Broken on 1.3 as DefaultTestSet fields are now const #136
Probably either the approach to combining test sets needs to change or sets of this field need to copy the whole testset. Both of these seem unfortunate but the latter perhaps more so.
Perhaps it would suffice to amend the version check to v"1.8" <= VERSION < v"1.13.0-DEV.1037" so that 1.13 would be unbroken and other versions would be unaffected.
Its been a long time since i wrote/reviewed that code.
It is clearly not a crucial feature since it was disabled pre-1.8
I suspect without it the report might end up missing timing data for the top level testset
AFAICT the only place where this code actually is used is in displaying the test set ... which is called in finish(::ReportingTestSet). Whats more it seems like the code is not actually in any meaningful way relying on the modify-in-place behavior. IIUC it's basically creating new DefaultTestSets for display purposes, so doing an Accessors.@set shouldn't be the worst thing...
Activity
ararslan commentedon Sep 10, 2026
Looks like we only attempt to overwrite the timing information on Julia 1.8+, falling back to leaving it as-is:
TestReports.jl/src/testsets.jl
Lines 211 to 216 in 211cff8
Perhaps it would suffice to amend the version check to
v"1.8" <= VERSION < v"1.13.0-DEV.1037"so that 1.13 would be unbroken and other versions would be unaffected.oxinabox commentedon Sep 11, 2026
Its been a long time since i wrote/reviewed that code.
It is clearly not a crucial feature since it was disabled pre-1.8
I suspect without it the report might end up missing timing data for the top level testset
kleinschmidt commentedon Sep 15, 2026
AFAICT the only place where this code actually is used is in displaying the test set ... which is called in
finish(::ReportingTestSet). Whats more it seems like the code is not actually in any meaningful way relying on the modify-in-place behavior. IIUC it's basically creating new DefaultTestSets for display purposes, so doing anAccessors.@setshouldn't be the worst thing...