add tests on CI to exercise bbfreeze/"frozen" #2471

Closed
opened 2015-07-21 16:46:12 +00:00 by warner · 1 comment

#585 added support for "bbfreeze"-generated single-file executables. I don't know if this still works: there is code (in *init*.py, at least) to detect the presence of sys.frozen, which occurs if you're inside a bbfreeze binary, but I don't think we have anything which tests this.

Maybe a CI job which creates the frozen executable and then runs the test suite, or at least does a basic smoketest and --version-and-path check.

#585 added support for "bbfreeze"-generated single-file executables. I don't know if this still works: there is code (in `*init*.py`, at least) to detect the presence of `sys.frozen`, which occurs if you're inside a bbfreeze binary, but I don't think we have anything which tests this. Maybe a CI job which creates the frozen executable and then runs the test suite, or at least does a basic smoketest and `--version-and-path` check.
warner added the
packaging
normal
task
1.10.1
labels 2015-07-21 16:46:12 +00:00
warner added this to the undecided milestone 2015-07-21 16:46:12 +00:00
tahoe-lafs changed title from add tests/buildslave to exercise bfreeze/"frozen" to add tests/buildslave to exercise bbfreeze/"frozen" 2015-07-21 19:32:57 +00:00
exarkun changed title from add tests/buildslave to exercise bbfreeze/"frozen" to add tests on CI to exercise bbfreeze/"frozen" 2019-07-25 13:00:43 +00:00

pyinstaller is now tested on CI.

pyinstaller is now tested on CI.
exarkun added the
was already fixed
label 2020-01-21 20:58:12 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2471
No description provided.