Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Problem] Running freecad integrated tests leaves leftover files #9680

Open
2 tasks done
Pesc0 opened this issue May 27, 2023 · 5 comments
Open
2 tasks done

[Problem] Running freecad integrated tests leaves leftover files #9680

Pesc0 opened this issue May 27, 2023 · 5 comments
Labels
Packaging/building Related to building, compiling or packaging FreeCAD Status: Stale Stale and might be closed automatically.

Comments

@Pesc0
Copy link
Contributor

Pesc0 commented May 27, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Version

0.21 (Development)

Full version info

latest build

Subproject(s) affected?

None

Problem description

Running FreeCAD -t 0 leaves behind

  • gcode.tmp:
G90
G21
M60

  • AM_INSTALLATION_DIGEST.txt:

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@xtemp09
Copy link
Contributor

xtemp09 commented May 28, 2023

Yes, I also would add:

SUMMARY: LeakSanitizer: 50339002 byte(s) leaked in 219478 allocation(s).

@Pesc0
Copy link
Contributor Author

Pesc0 commented May 28, 2023

It seems to me python tests could get a bit of attention and refinement. I wouldn't mind working on this. As part of this would it be a good idea to move said tests outside of freecad, to the tests directory, alongside cpp tests? I did ask this question here: #9663 (comment), the idea being:

  • All tests would be in the same place, well organized and easy to find.
  • Detaching from freecad allows more flexibility, in particular for the goal of better integration with IDEs (Improve VSCode integration #9663)
  • It's one less workbench in freecad. Correct me if I'm wrong, but this is used only by developers, end users don't really need to run tests, right?

Would there be any downsides to this move? Is it quite straight forward or am I committing to a massive endeavor?

@adrianinsaval
Copy link
Member

I don't know, we've gotten several reports that lead to fixing things from users running tests on different platforms (that we don't normally test on).

@luzpaz luzpaz added the Packaging/building Related to building, compiling or packaging FreeCAD label Jun 7, 2023
@luzpaz
Copy link
Contributor

luzpaz commented Sep 29, 2023

Other leftover files related ticket: #10221

Copy link

github-actions bot commented Jan 1, 2025

Hi! This issue hasn’t seen activity in a while. We automatically check each issue after 190 days without activity to keep the backlog tidy.
If it’s still relevant, please update to the latest FreeCAD weekly build download here to see if the issue is already resolved.

If the issue is still relevant, let us know by adding a comment.
Otherwise, we’ll close this issue automatically in 60 days.

Feel free to comment anytime to keep it open. Closed issues can always be reopened.
Thanks for helping improve FreeCAD!

Access additional FreeCAD resources:

@github-actions github-actions bot added the Status: Stale Stale and might be closed automatically. label Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Packaging/building Related to building, compiling or packaging FreeCAD Status: Stale Stale and might be closed automatically.
Projects
None yet
Development

No branches or pull requests

4 participants