Your message dated Sat, 13 Oct 2018 07:51:06 +0000 with message-id <[email protected]> and subject line Bug#910311: fixed in elpy 1.25.0-1 has caused the Debian Bug report #910311, regarding elpy FTBFS randomly: test elpy-promise-wait-should-return-early-for-resolved-promise fails to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 910311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910311 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: elpy Version: 1.24.0-1 Severity: serious Tags: ftbfs elpy fails to build from source randomly. A build log contains: | Test elpy-promise-wait-should-return-early-for-resolved-promise backtrace: | (if (unwind-protect (setq value-774 (apply fn-772 args-773)) (setq f | (let (form-description-776) (if (unwind-protect (setq value-774 (app | (let ((value-774 (quote ert-form-evaluation-aborted-775))) (let (for | (let ((fn-772 (function elpy-promise-resolved-p)) (args-773 (list pr | (let ((start-time (current-time)) (promise (elpy-promise nil))) (run | (progn (let ((start-time (current-time)) (promise (elpy-promise nil) | (progn (setq elpy-rpc-timeout 100) (progn (let ((start-time (current | (unwind-protect (progn (setq elpy-rpc-timeout 100) (progn (let ((sta | (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn | (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-b | (progn (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-cu | (unwind-protect (progn (let ((temp-buffer (generate-new-buffer " *te | (let ((old-process-list (process-list)) (old-buffer-list (buffer-lis | (lambda nil (let ((old-process-list (process-list)) (old-buffer-list | ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc | ert-run-test([cl-struct-ert-test elpy-promise-wait-should-return-ear | ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test e | ert-run-tests(t #[385 "\306^B\307\"\203G^@\211\211G\310U\203^T^@\211@\20 | ert-run-tests-batch(nil) | ert-run-tests-batch-and-exit() | eval((ert-run-tests-batch-and-exit)) | command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc | command-line() | normal-top-level() | Test elpy-promise-wait-should-return-early-for-resolved-promise condition: | (ert-test-failed | ((should | (elpy-promise-resolved-p promise)) | :form | (elpy-promise-resolved-p | [*elpy-promise* nil nil #<killed buffer> nil]) | :value nil)) | FAILED 222/362 elpy-promise-wait-should-return-early-for-resolved-promise This happened in sbuild on unstable/amd64. The reproducible builds folks encountered the same failure in one out of two builds using pbuilder: https://tests.reproducible-builds.org/debian/logs/unstable/amd64/elpy_1.24.0-1.build2.log.gz https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/elpy_1.24.0-1.rbuild.log.gz https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/elpy_1.24.0-1.rbuild.log.gz For amd64, only the second build failed. When I tried it locally in sbuild, three builds succeeded. I have no clue how the failure is caused, but it is evident that it is not broken infrastructure. Helmut
--- End Message ---
--- Begin Message ---Source: elpy Source-Version: 1.25.0-1 We believe that the bug you reported is fixed in the latest version of elpy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas D Steeves <[email protected]> (supplier of updated elpy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 12 Oct 2018 18:16:00 -0400 Source: elpy Binary: elpa-elpy Architecture: source all Version: 1.25.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team <[email protected]> Changed-By: Nicholas D Steeves <[email protected]> Description: elpa-elpy - Emacs Python Development Environment Closes: 910311 Changes: elpy (1.25.0-1) unstable; urgency=medium . * New upstream version. * Upstream no longer distributes NEWS.rst - debian/rules: Drop build/NEWS generation. - Drop debian/local-var-snippet which was only used in NEWS. - debian/docs: do not install build/NEWS. - debian/elpa-test: Do not run test for elpy-news-should-insert-file, because it depends on NEWS.rst, which was dropped upstream. * Support 'nodoc' build profile - debian/control: Add <!nodoc> to python3-sphinx and texinfo build deps. - debian/rules: Only attempt to generate documentation when nodoc is not present in DEB_BUILD_PROFILES. - debian/rules: Workaround Bug #908078, because dh_sphinxdoc does not yet detect when "nodoc" is active and --with sphinxdoc will fail when python3-sphinx is not installed. * Add lintian-override for wrong-section-according-to-package-name, because section "devel" is most appropriate for an IDE for Python development when that IDE is implemented in Emacs Lisp. * debian/rules: Fix typo. * Enable support for Black, the uncompromising Python code formatter, now that it has been added to the Debian archive. - debian/control: Add black to Build-Depends and Suggests. - Drop debian/patches/0002-Disable-tests-for-black-code-formatter.patch. * Import upstream 0002-Handle-sphinx-warnings-linked-to-indexnode.patch This patch fixes numerous warnings of "4 column based index found" when building. * Fix sentence fragment in long description. * debian/elpa-test: Temporarily disable elpy-promise-wait-should-return-early-for-resolved and related tests in elpy-promise-wait-test.el. This test passes 100% of the time with python3.6=3.6.6-1 and python3.7=3.7.1~rc1-1 and fails ~40% of the time with python3.6=3.6.7~rc1-1. Issue has been forwarded upstream. Tests involving Elpy "promises" will be reenabled after the Python 3.7 transition. (Closes: #910311) Checksums-Sha1: 5b1d2ea438622e886e311e8dee80e63a5a12dc7f 2422 elpy_1.25.0-1.dsc e2a1fe6ec94267f839b49fdbd50453eef969f27f 118068 elpy_1.25.0.orig.tar.xz 5ccc39b2b9721b570935b4b181312fb0897eb02c 7628 elpy_1.25.0-1.debian.tar.xz 343ac42435339deffa2f17988046fbb53892988d 111436 elpa-elpy_1.25.0-1_all.deb 3640d92202125f0586209fc1b681a9a7daa41076 10609 elpy_1.25.0-1_amd64.buildinfo Checksums-Sha256: 08a635d6b48056df05109bb0ff7b306e001d4022799717a9c84389a2be1461a2 2422 elpy_1.25.0-1.dsc 03b90d0dc334c3c4dc2b3c35a8c65abbc57f17d6243c5f7029f751a0e5019de8 118068 elpy_1.25.0.orig.tar.xz 1bfad64bf2db89fd8255f7310316a86aa5922a80a970c14f7817e5a0b903929c 7628 elpy_1.25.0-1.debian.tar.xz f48d0f5741bd02986079b80c3ef500868494cbbce6fb1d0b28a4a43b1f4681a0 111436 elpa-elpy_1.25.0-1_all.deb b6ba92868e8bc8c4ad309c81565d6f219c7a343d218d20daae7d4ca4ef9c4b84 10609 elpy_1.25.0-1_amd64.buildinfo Files: 7cd4c221ebeaf520cf6c12bfa4ea321a 2422 devel optional elpy_1.25.0-1.dsc 4c378bbc3acb7052955b6e21f9831c90 118068 devel optional elpy_1.25.0.orig.tar.xz 63f43f5e5fa38d0d814f6ffb03cc7195 7628 devel optional elpy_1.25.0-1.debian.tar.xz 658226c6c26f753d6ded2b3fa992f0f0 111436 devel optional elpa-elpy_1.25.0-1_all.deb 604715acbdcd362810d925554c6f30c4 10609 devel optional elpy_1.25.0-1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlvBoOUACgkQHpU+J9Qx Hlibxg/6AwBx4H+Do/UwHurDrCJM6wYPmRL42KrpY6zZJeFHkgCjDLgKwP5J022V yld69LXeNdDqycgD6XhO+adhbuNGhL3OevbJRejYL8VovgjCZqURmBB3P37x4k5q 3DOfLHBxfrzu+iAaCVx6mayZawfEsvKrTOYTOMfgvBNa9gD+CFQ8aFWbbG7NmGHB 7TjL6vKOUXEkMBpCBapq+sjfXUghwb++ykx7ZvXi/rPdr6re9K/wVtyg5y6JAlRr B2DsfXuyGLB6QC6disRLkCy4XRrKV3JothszvaEIK8MhMfVyaBEXMCc986wLH9KN gFgnmpKU7sIVJVy+qO/8Qps4Q0P7S40U97kzeFxUUIipDeJC9SauM6Wms6dCC9e3 EEo4rUHWbzkAPf3irWm5vje3lPo07kVM8xL/tbL1ri0bEhYNLBlVtVrxNTvrNcyy j3SzVPaBmg6/ap9aiRuJICKpxFV4wc/z2KDpihYNYo3UFRow8W1oZKWTRs9K5gG2 iF+BPXSDNPvC1EWE7Xt+Rka08S5dC4NfaSqyz2G2+u8LCEIGG8I+x+pPt94FOfSI WjIRdKwcMgWvwaqqKFpmPXRtLS0nDkvSpKVjTucRwy1TOU/AdMHonNZvZ8XCbKR9 jEk4TftnBgoePmbbWbFAS4j234ItCLI3erJOABAu+rVTZ+XeNwg= =mVO4 -----END PGP SIGNATURE-----
--- End Message ---
