Please not that `workflow.trace.succeeded().size()...
# pipeline-maintainers
m
Please not that
workflow.trace.succeeded().size()
in nf-test is no longer working with the latest Nextflow version, so we removed it from the TEMPLATE but it might still be in your tests, please take care, and don't hesitate to come in #C049MBCEW06 if you have any questions. cf https://nfcore.slack.com/archives/C049MBCEW06/p1762944186970469
p
Is there an issue for it on the nf-test repo?
m
yes
I'm sure I made one when I first encountered that problem
f
is there a replacement to achieve the same behavior?
p
@Maxime Garcia and is it still a problem after https://github.com/nextflow-io/nextflow/pull/6403 was merged?
If that fixes it, then sounds like it should only be an issue for NF
25.07.0-edge
->
25.09.0-edge
?
If not, then the issue needs an update for both Ben + Lukas I guess.
f
I just ran a local test with version
25.10.0
and
workflow.trace.succeeded().size()
and it succeeded.
d
This is working for me too, it reports the number
p
Should we add it back to the template? 'cc @Maxime Garcia <!subteam^S08LAB76NBU>
m
oh
let's wait until we bump the minimal version in TEMPLATE
m
what is the required minimum version for this?
p
None, it only affected a range of edge releases between stable releases
m
> let's wait until we bump the minimal version in TEMPLATE so no need for this?
👍🏻 1
p
I don't think so? If I understand it properly
m
Are we sure it's not breaking on any stable release?
p
Not according to the title of the issue that you created 😅
Nextflow 25.07.0-edge fails with workflow.trace
But also based on the PR with the fix I guess not. Ben said that it was a regression from the config refactor, and that's new in 25.10
m
Yeah I discovered it with edge
Haven't tried all versions
25.10 wasn't released at the time
p
I suspect that if you test 25.04 and 25.10 they should both be fine.
m
OK, I'll do a proper investigation then
🙏🏻 1