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

aup stuck in infite loop when updating archive packages #107

Open
moooeeeep opened this issue Oct 18, 2021 · 2 comments
Open

aup stuck in infite loop when updating archive packages #107

moooeeeep opened this issue Oct 18, 2021 · 2 comments

Comments

@moooeeeep
Copy link

moooeeeep commented Oct 18, 2021

When I install a package from an archive and update the archive link (e.g., to update the version), without specifying AUTOBUILD_ARCHIVE_AUTOUPDATE=1 and without clearing the cache, aup gets stuck in an infinite loop:

[...]
  update failed external/lemon
  update failed external/lemon
  update failed external/lemon
  update failed external/lemon
  update failed external/lemon
^C  interrupted external/lemon

Interrupted by user

I can reproduce it with this buildconf manifest:

package_sets:
 - github: rock-core/rock-package_set
layout:
 - external/lemon

It gets stuck, when I then (after installation) change the link to select another version of the package, e.g., like this

--- source.yml
+++ source.yml
@@ -302,7 +302,7 @@ version_control:
 
     - external/lemon:
       type: archive
-      url: http://lemon.cs.elte.hu/pub/sources/lemon-1.3.1.tar.gz
+      url: http://lemon.cs.elte.hu/pub/sources/lemon-1.2.4.tar.gz
       update_cached_file: false
       patches:
             - $AUTOPROJ_SOURCE_DIR/patches/lemon_cmake.patch

The exception is raised here. Not sure where exactly the infinite loop is going on.

This seems to also happen with update_cached_file: true

@moooeeeep
Copy link
Author

It seems the exception is caught and ignored here.

Therefore the package is never removed from the queue and the loop doesn't stop.

@doudou
Copy link
Member

doudou commented Oct 19, 2021

Hi @moooeeeep. Thanks for the report.

It seems the exception is caught and ignored here.

Not that simple ;-) The error e is added to completion_queue and is then managed afterwards.

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

No branches or pull requests

2 participants