Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#11539 closed defect (fixed)

TBB nightly failing with can't open file 'setup_tbb.py': [Errno 2] No such file or directory"

Reported by: ln5 Owned by: kpdyer
Priority: Medium Milestone:
Component: Applications/Tor bundles/installation Version:
Severity: Keywords: MikePerry201404R
Cc: gk Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

tor-browser-bundle is at commit eef7f8761aba04722f67a098b8a7aba72a5917cb

a - obj/re2/regexp.o
a - obj/re2/set.o
a - obj/re2/simplify.o
a - obj/re2/tostring.o
a - obj/re2/unicode_casefold.o
a - obj/re2/unicode_groups.o
make[1]: Leaving directory `/home/ubuntu/build/fteproxy/thirdparty/re2'
+ LD_PRELOAD=
+ wine /home/ubuntu/install/python/python.exe setup_tbb.py build_ext -c mingw32
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
Z:\home\ubuntu\install\python\python.exefixme:msvcrt:__clean_type_info_names_internal (0x1e24c178) stub
: can't open file 'setup_tbb.py': [Errno 2] No such file or directory

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by gk

Owner: changed from erinn to kpdyer
Status: newassigned

This fteproxy bug breaks our current nightly builds.

comment:2 in reply to:  1 ; Changed 5 years ago by kpdyer

Replying to gk:

This fteproxy bug breaks our current nightly builds.

Can you ensure that something isn't wrong with the nightly build setup? That is, the latest master of fteproxy [1] does have a setup_tbb.py file. So, something might have gone wrong?

However, there is a larger problem here. It might be best for us to move away from "master" for fteproxy and nightly builds. The fteproxy master will be unstable in future. If that's not ok, then we should pin a specific version.

I've now pinned the latest stable version of fteproxy across all versions* files. This should prevent this from happening again.

Mike - can you merge [2]?

[1] https://github.com/kpdyer/fteproxy
[2] https://github.com/kpdyer/tor-browser-bundle

Last edited 5 years ago by kpdyer (previous) (diff)

comment:3 Changed 5 years ago by kpdyer

Keywords: MikePerry201404R added
Resolution: fixed
Status: assignedclosed

comment:4 in reply to:  2 Changed 5 years ago by gk

Replying to kpdyer:

Replying to gk:

This fteproxy bug breaks our current nightly builds.

Can you ensure that something isn't wrong with the nightly build setup? That is, the latest master of fteproxy [1] does have a setup_tbb.py file. So, something might have gone wrong?

Sorry, this was indeed a bug in the tor-browser-bundle code and should be fixed with commit e47484df829eefead58ed10c8541a493c0ba6e3a.

However, there is a larger problem here. It might be best for us to move away from "master" for fteproxy and nightly builds. The fteproxy master will be unstable in future. If that's not ok, then we should pin a specific version.

Fair enough. I think if "unstable" boils down to breaking the nightly builds then pinning might indeed be the best thing here.

I've now pinned the latest stable version of fteproxy across all versions* files. This should prevent this from happening again.

Mike - can you merge [2]?

Thanks. I've tested and merged your code (the latter in commit 7df52e4294bcb0fff50c34bffe7aca38a9b88b61)

Note: See TracTickets for help on using tickets.