Skip to content

Added nf-test - #74

Merged
sillitoe merged 26 commits into
devfrom
nf_test
Aug 5, 2026
Merged

Added nf-test#74
sillitoe merged 26 commits into
devfrom
nf_test

Conversation

@FernandoDuarteF

Copy link
Copy Markdown
Collaborator

This PR has the same changes as #70, but it's not comparing to a forked repo this time.

I want to check whether CI works this time, as it was not working in the previous PR.

@chriswyatt1

Copy link
Copy Markdown
Collaborator

Just thought I would try removing dev from PR tests, but think this won't work. lets see (I will put back if not)

@chriswyatt1

Copy link
Copy Markdown
Collaborator

@sillitoe @NSEdmunds . I think the PRs can be merged now if you are happy with them.

@sillitoe

sillitoe commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

TODO:

  • add to CI
  • merge

@sillitoe

sillitoe commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@FernandoDuarteF is there any way of getting nf-test to be more specific about the differences in a failing test? I can't actually see where any differences are in this output.

@sillitoe

sillitoe commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Also, we merged the config PR #69 hence the conflict

@FernandoDuarteF

Copy link
Copy Markdown
Collaborator Author

It's mainly a problem of github, the output is truncated I believe.

The CI is failing here becuase of foldseek_parsed_results.tsv, it has slightly different results depending on the architecture. I got different results in some decimal places on my Mac, which is the one that I used for the snapshot.

I'll try to run the test on an amd machine and generate the snapshot again, that should work for the CI.

@FernandoDuarteF

Copy link
Copy Markdown
Collaborator Author

Hey everyone. It seems I always get a different snapshot on different platforms (ci vs codespaces vs my mac). It's starting to be a real headache.

Perhaps we shouldn't wait for this PR before running the pipeline on the next batch.

The final float in the following line is not stable when computed on different arch.

```                "A0A004_02\tf9ca035470c019ce20a74306af810176\tmed\t234-372_496-557\t201\t2\t29\t13\t5\t18\t11\t11.708\t0.319\t92.159\tproteome-tax_id-67581-0_v4\t\tStreptomyces viridosporus\tcellular organisms (no rank), Bacteria (domain), Bacillati (kingdom), Actinomycetota (phylum), Actinomycetes (class), Kitasatosporales (order), Streptomycetaceae (family), Streptomyces (genus)\t0.905\tTrue\t6gq3A02\t2.459e-12\t0.862\t3.40.50.620\tH\t0.995\t0.776\t81.270",
```

We have manaully changed `81.520` -> `81.270`, but this needs a better solution moving forwards.
@sillitoe

sillitoe commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Hey everyone. It seems I always get a different snapshot on different platforms (ci vs codespaces vs my mac). It's starting to be a real headache.

Perhaps we shouldn't wait for this PR before running the pipeline on the next batch.

Hmm.. interesting. The difference does seem more than expected just from calculations on different arch (81.520 -> 81.270).

I'm thinking it would be good to include this PR, so how about we:

  • manually change the single failing result in the snapshot (done)
  • add an issue to investigate this further

?

Also, just a note that I've added some changes to hopefully improve the reporting of failed nf-test results (unified diff + upload artifacts)

@FernandoDuarteF

Copy link
Copy Markdown
Collaborator Author

Yeah, maybe changing the snapshot manually is the only way. Or maybe we can add the changing files to the nf-test ignore?

I also noticed that the *chopped_pdbs.tar.gz files are have different md5s when I run the test in codespaces, which I found very strange as it doesn't happen in the ci or my mac. But I'll have a closer look.

@sillitoe

sillitoe commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Cool. Looks like tests are passing now. Are you happy to merge @FernandoDuarteF ?

@FernandoDuarteF

Copy link
Copy Markdown
Collaborator Author

Looks good! I'll merge then

@sillitoe

sillitoe commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Yeah, maybe changing the snapshot manually is the only way. Or maybe we can add the changing files to the nf-test ignore?

I also noticed that the *chopped_pdbs.tar.gz files are have different md5s when I run the test in codespaces, which I found very strange as it doesn't happen in the ci or my mac. But I'll have a closer look.

I think we'll definitely want to include the rest of the results file that has differences.

Very interesting to have an example chopped PDB file with changes - I would expect any changes would be a reflection on changes in the domain boundaries (in the results file). Strange to have differences in a single chopped PDB file without differences in the results file.

Happy to create new issues to look into both of these.

@sillitoe
sillitoe merged commit 2773ca2 into dev Aug 5, 2026
2 checks passed
@FernandoDuarteF

Copy link
Copy Markdown
Collaborator Author

Yeah, maybe changing the snapshot manually is the only way. Or maybe we can add the changing files to the nf-test ignore?
I also noticed that the *chopped_pdbs.tar.gz files are have different md5s when I run the test in codespaces, which I found very strange as it doesn't happen in the ci or my mac. But I'll have a closer look.

I think we'll definitely want to include the rest of the results file that has differences.

Very interesting to have an example chopped PDB file with changes - I would expect any changes would be a reflection on changes in the domain boundaries (in the results file). Strange to have differences in a single chopped PDB file without differences in the results file.

Happy to create new issues to look into both of these.

I'll open the issues and explore a little bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants