tahoe-lafs
/
trac-2024-07-25
2
0
Issues 1.1k Wiki

Appveyor builds intermittently fail while uploading artifacts #2993

New Issue
Closed
opened 2019-03-11 13:39:42 +00:00 by exarkun · 2 comments
exarkun commented 2019-03-11 13:39:42 +00:00
Copy Link

For example, https://ci.appveyor.com/project/tahoe-lafs/tahoe-lafs/builds/22978547/job/6uw22y64rcam277g has a failed job with a log that ends:

Uploading artifacts...
[1/47] dist\appdirs-1.4.3-py2.py3-none-any.whl (12,154 bytes)...100%
[2/47] dist\argparse-1.4.0-py2.py3-none-any.whl (23,000 bytes)...100%
[3/47] dist\asn1crypto-0.24.0-py2.py3-none-any.whl (101,571 bytes)...100%
[4/47] dist\attrs-19.1.0-py2.py3-none-any.whl (35,784 bytes)...100%
[5/47] dist\autobahn-19.2.1-py2.py3-none-any.whl (302,987 bytes)...100%
[6/47] dist\Automat-0.7.0-py2.py3-none-any.whl (37,638 bytes)...100%
[7/47] dist\boltons-19.1.0-py2.py3-none-any.whl (163,903 bytes)...100%
[8/47] dist\cffi-1.12.2-cp27-cp27m-win32.whl (157,191 bytes)...100%
[9/47] dist\characteristic-14.3.0-py2.py3-none-any.whl (15,045 bytes)...100%
[10/47] dist\Click-7.0-py2.py3-none-any.whl (81,299 bytes)...100%
[11/47] dist\constantly-15.1.0-py2.py3-none-any.whl (7,922 bytes)...100%
[12/47] dist\cryptography-2.6.1-cp27-cp27m-win32.whl (1,253,393 bytes)...100%
[13/47] dist\eliot-1.6.0-py2.py3-none-any.whl (104,922 bytes)...100%
[14/47] dist\enum34-1.1.6-py2-none-any.whl (12,427 bytes)...100%
[15/47] dist\foolscap-0.13.1-py2-none-any.whl (315,007 bytes)...100%
[16/47] dist\hkdf-0.0.3-cp27-none-any.whl (3,773 bytes)...100%
[17/47] dist\humanize-0.5.1-cp27-none-any.whl (17,929 bytes)...100%
[18/47] dist\hyperlink-18.0.0-py2.py3-none-any.whl (37,905 bytes)...100%
[19/47] dist\idna-2.8-py2.py3-none-any.whl (58,594 bytes)...100%
[20/47] dist\incremental-17.5.0-py2.py3-none-any.whl (16,667 bytes)...100%
[21/47] dist\ipaddress-1.0.22-py2.py3-none-any.whl (18,155 bytes)...100%
[22/47] dist\magic_wormhole-0.11.2-py2.py3-none-any.whl (130,626 bytes)...100%
[23/47] dist\Nevow-0.14.4-py2-none-any.whl (449,148 bytes)...100%
[24/47] dist\pyasn1-0.4.5-py2.py3-none-any.whl (73,683 bytes)...100%
[25/47] dist\pyasn1_modules-0.2.4-py2.py3-none-any.whl (66,953 bytes)...100%
[26/47] dist\pycparser-2.19-py2.py3-none-any.whl (111,078 bytes)...100%
[27/47] dist\pycryptopp-0.7.1.869544967005693312591928092448767568728501330214-cp27-cp27m-win32.whl (1,473,748 bytes)...100%
[28/47] dist\PyHamcrest-1.9.0-py2.py3-none-any.whl (52,311 bytes)...100%
[29/47] dist\PyNaCl-1.3.0-cp27-cp27m-win32.whl (181,405 bytes)...100%
[30/47] dist\pyOpenSSL-19.0.0-py2.py3-none-any.whl (53,333 bytes)...100%
[31/47] dist\pypiwin32-223-cp27-none-any.whl (1,028 bytes)...100%
[32/47] dist\pyrsistent-0.14.11-cp27-cp27m-win32.whl (54,835 bytes)...100%
[33/47] dist\pyutil-3.1.0-cp27-none-any.whl (393,647 bytes)...100%
[34/47] dist\pywin32-224-cp27-cp27m-win32.whl (6,836,723 bytes)...
Error uploading artifact the storage: Unable to read data from the transport connection: The connection was closed.

It's not clear we can fix the actual problem ourselves as this seems to be part of Appveyor-implemented functionality. Perhaps we could avoid that functionality entirely in favor of something we control and can make work reliably. Or perhaps we can report this issue to Appveyor and get them to make it reliable.

A mitigating step might be to upload fewer artifacts from Appveyor. I'm not sure why we upload all of those third-party wheels. Are we hoping they will be helpful to someone? Seems unlikely. It seems like just uploading the Tahoe-LAFS wheel would be sufficient. But, for that matter, do we need to make a Tahoe-LAFS Windows wheel? Shouldn't a cross-platform wheel be possible?

For example, <https://ci.appveyor.com/project/tahoe-lafs/tahoe-lafs/builds/22978547/job/6uw22y64rcam277g> has a failed job with a log that ends: ``` Uploading artifacts... [1/47] dist\appdirs-1.4.3-py2.py3-none-any.whl (12,154 bytes)...100% [2/47] dist\argparse-1.4.0-py2.py3-none-any.whl (23,000 bytes)...100% [3/47] dist\asn1crypto-0.24.0-py2.py3-none-any.whl (101,571 bytes)...100% [4/47] dist\attrs-19.1.0-py2.py3-none-any.whl (35,784 bytes)...100% [5/47] dist\autobahn-19.2.1-py2.py3-none-any.whl (302,987 bytes)...100% [6/47] dist\Automat-0.7.0-py2.py3-none-any.whl (37,638 bytes)...100% [7/47] dist\boltons-19.1.0-py2.py3-none-any.whl (163,903 bytes)...100% [8/47] dist\cffi-1.12.2-cp27-cp27m-win32.whl (157,191 bytes)...100% [9/47] dist\characteristic-14.3.0-py2.py3-none-any.whl (15,045 bytes)...100% [10/47] dist\Click-7.0-py2.py3-none-any.whl (81,299 bytes)...100% [11/47] dist\constantly-15.1.0-py2.py3-none-any.whl (7,922 bytes)...100% [12/47] dist\cryptography-2.6.1-cp27-cp27m-win32.whl (1,253,393 bytes)...100% [13/47] dist\eliot-1.6.0-py2.py3-none-any.whl (104,922 bytes)...100% [14/47] dist\enum34-1.1.6-py2-none-any.whl (12,427 bytes)...100% [15/47] dist\foolscap-0.13.1-py2-none-any.whl (315,007 bytes)...100% [16/47] dist\hkdf-0.0.3-cp27-none-any.whl (3,773 bytes)...100% [17/47] dist\humanize-0.5.1-cp27-none-any.whl (17,929 bytes)...100% [18/47] dist\hyperlink-18.0.0-py2.py3-none-any.whl (37,905 bytes)...100% [19/47] dist\idna-2.8-py2.py3-none-any.whl (58,594 bytes)...100% [20/47] dist\incremental-17.5.0-py2.py3-none-any.whl (16,667 bytes)...100% [21/47] dist\ipaddress-1.0.22-py2.py3-none-any.whl (18,155 bytes)...100% [22/47] dist\magic_wormhole-0.11.2-py2.py3-none-any.whl (130,626 bytes)...100% [23/47] dist\Nevow-0.14.4-py2-none-any.whl (449,148 bytes)...100% [24/47] dist\pyasn1-0.4.5-py2.py3-none-any.whl (73,683 bytes)...100% [25/47] dist\pyasn1_modules-0.2.4-py2.py3-none-any.whl (66,953 bytes)...100% [26/47] dist\pycparser-2.19-py2.py3-none-any.whl (111,078 bytes)...100% [27/47] dist\pycryptopp-0.7.1.869544967005693312591928092448767568728501330214-cp27-cp27m-win32.whl (1,473,748 bytes)...100% [28/47] dist\PyHamcrest-1.9.0-py2.py3-none-any.whl (52,311 bytes)...100% [29/47] dist\PyNaCl-1.3.0-cp27-cp27m-win32.whl (181,405 bytes)...100% [30/47] dist\pyOpenSSL-19.0.0-py2.py3-none-any.whl (53,333 bytes)...100% [31/47] dist\pypiwin32-223-cp27-none-any.whl (1,028 bytes)...100% [32/47] dist\pyrsistent-0.14.11-cp27-cp27m-win32.whl (54,835 bytes)...100% [33/47] dist\pyutil-3.1.0-cp27-none-any.whl (393,647 bytes)...100% [34/47] dist\pywin32-224-cp27-cp27m-win32.whl (6,836,723 bytes)... Error uploading artifact the storage: Unable to read data from the transport connection: The connection was closed. ``` It's not clear we can fix the actual problem ourselves as this seems to be part of Appveyor-implemented functionality. Perhaps we could avoid that functionality entirely in favor of something we control and can make work reliably. Or perhaps we can report this issue to Appveyor and get them to make it reliable. A mitigating step might be to upload fewer artifacts from Appveyor. I'm not sure why we upload all of those third-party wheels. Are we hoping they will be helpful to someone? Seems unlikely. It seems like just uploading the Tahoe-LAFS wheel would be sufficient. But, for that matter, do we need to make a Tahoe-LAFS Windows wheel? Shouldn't a cross-platform wheel be possible?
exarkun added the
unknown
normal
defect
1.12.1
 labels 2019-03-11 13:39:42 +00:00
exarkun added this to the undecided milestone 2019-03-11 13:39:42 +00:00
exarkun commented 2020-01-17 17:12:05 +00:00
Author
Copy Link

Maybe we should use GitHub actions instead of Appveyor. I hear it's the new hotness that everybody loves.

Maybe we should use [GitHub](wiki/GitHub) actions instead of Appveyor. I hear it's the new hotness that everybody loves.
exarkun commented 2020-08-27 14:36:32 +00:00
Author
Copy Link

We did indeed move to GitHub Actions and stopped using Appveyor.

We did indeed move to [GitHub](wiki/GitHub) Actions and stopped using Appveyor.
exarkun added the
wontfix
 label 2020-08-27 14:36:32 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No Milestone
undecided
Assignees
Clear assignees
No Assignees
1 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#2993
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?