# Issue with the test that is using latest Nextflow version

**URL:** <https://community.seqera.io/t/issue-with-the-test-that-is-using-latest-nextflow-version/463>\
**Category:** Ask for help\
**Tags:** nf-core\
**Created:** [February 8, 2024, 11:13am UTC](https://community.seqera.io/t/issue-with-the-test-that-is-using-latest-nextflow-version/463 "2024-02-08T11:13:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![subwaystation](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/subwaystation/32/474_2.png) [@subwaystation](https://community.seqera.io/u/subwaystation)\
**Post date:** [February 8, 2024, 11:13am UTC](https://community.seqera.io/t/issue-with-the-test-that-is-using-latest-nextflow-version/463/1 "2024-02-08T11:13:44Z")

</div>

Hi,  
I am currently updating some modules of the [GitHub - nf-core/pangenome: Renders a collection of sequences into a pangenome graph.](https://github.com/nf-core/pangenome) pipeline. The test with all software latest does not run through anymore due to some parsing problem of the latest Nextflow version?  
Somebody got any ideas? Thanks! [update wfmash, multiqc by subwaystation · Pull Request #165 · nf-core/pangenome · GitHub](https://github.com/nf-core/pangenome/pull/165). The code that is apparently malfunctioning was not touched within this PR.

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [February 8, 2024, 4:13pm UTC](https://community.seqera.io/t/issue-with-the-test-that-is-using-latest-nextflow-version/463/3 "2024-02-08T16:13:34Z")

</div>

Hello, @subwaystation. If I’m not mistaken, this was due to Nextflow recent change to Groovy 4, and the error you were running into was solved by [this commit](https://github.com/nf-core/pangenome/commit/28e73b153282c5f9467bc158af517a9b98c20a85) from @Adam_Talbot, right?

---

<div class="post-metadata">

**Author:** ![Adam\_Talbot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/adam_talbot/32/62_2.png) [@Adam\_Talbot](https://community.seqera.io/u/Adam_Talbot)\
**Post date:** [February 8, 2024, 6:07pm UTC](https://community.seqera.io/t/issue-with-the-test-that-is-using-latest-nextflow-version/463/4 "2024-02-08T18:07:46Z")

</div>

Yep, although there seems to be some nuance which you can find detailed here: [Config parsing error in 24.01.0-edge when using `includeConfig` of assignment of function value · Issue #4722 · nextflow-io/nextflow · GitHub](https://github.com/nextflow-io/nextflow/issues/4722)