From: raid5atemyhomework via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: "51498@debbugs.gnu.org" <51498@debbugs.gnu.org>
Subject: bug#51498: onionshare build is broken
Date: Fri, 05 Nov 2021 01:31:24 +0000 [thread overview]
Message-ID: <71NrR9CIatwqC45LYY-6AWdyugCrijO3vc409GY_eDSCIg9wnzFAE3CerYB3r0zkY16fwraexVge-RKIQPquf0cDHrFRfnXHMGrEdfKAqh0=@protonmail.com> (raw)
In-Reply-To: <92qiop_y9j0qwdLooBRmFS2c4LIcTWyH12TZ7li1isQfez4ntpPdkLmBdH5p0dtF0T4xgUB6D0FIdbGDOXVWz5HHdFlxHgxXMZ2TxUPxU7I=@protonmail.com>
> > Can you test it again? I was able to build it just now with commit
> > c0c974ad96767a1e207fe2823cd5479605485415. I was also able to build it
> > with your provided commit above.
>
> Having diverging results suggests a nondeterministic build, which is bad, right? I'm running on a Guix System machine running directly on the metal.
On a Guix on top of a foreign distro, I got:
* good: `guix time-machine --commit=ebc274063716a3a9471f51abb526d693c06b9f63 -- build onionshare`
* result: `/gnu/store/ynkjlqh9sjr72blfvvxrj86cgjpa270l-onionshare-2.3.2`
Looks like nondeterminism?
On the machine where the build is failing, this is the stanza where the tests start going wrong:
```
tests/test_gui_share.py::TestShare::test_401_public_skips_ratelimit PASSED [ 5%]
tests/test_gui_share.py::TestShare::test_401_triggers_ratelimit PASSED [ 10%]
tests/test_gui_share.py::TestShare::test_405_page_returned_for_invalid_methods PASSED [ 15%]
tests/test_gui_share.py::TestShare::test_autostart_and_autostop_timer_mismatch SKIPPED [ 21%]
tests/test_gui_share.py::TestShare::test_autostart_timer SKIPPED [ 26%]
tests/test_gui_share.py::TestShare::test_autostart_timer_cancel PASSED [ 31%]
tests/test_gui_share.py::TestShare::test_autostart_timer_too_short SKIPPED [ 36%]
tests/test_gui_share.py::TestShare::test_autostop_timer SKIPPED [ 42%]
tests/test_gui_share.py::TestShare::test_autostop_timer_too_short SKIPPED [ 47%]
tests/test_gui_share.py::TestShare::test_clear_all_history_button PASSED [ 52%]
tests/test_gui_share.py::TestShare::test_download PASSED [ 57%]
tests/test_gui_share.py::TestShare::test_individual_files PASSED [ 63%]
tests/test_gui_share.py::TestShare::test_individual_files_without_autostop_sharing PASSED [ 68%]
tests/test_gui_share.py::TestShare::test_large_download FAILED [ 73%]
tests/test_gui_share.py::TestShare::test_persistent_password FAILED [ 78%]
tests/test_gui_share.py::TestShare::test_public_mode FAILED [ 84%]
tests/test_gui_share.py::TestShare::test_remove_all_file_selection_button FAILED [ 89%]
tests/test_gui_share.py::TestShare::test_unreadable_file FAILED [ 94%]
tests/test_gui_share.py::TestShare::test_without_autostop_sharing FAILED [100%]
```
Build log github gist: https://gist.github.com/raid5atemyhomework/113e4860b359ab70637eedc032648d3b
Thanks
raid5atemyhomework
next prev parent reply other threads:[~2021-11-05 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 2:53 bug#51498: onionshare build is broken raid5atemyhomework via Bug reports for GNU Guix
2021-10-30 3:05 ` raid5atemyhomework via Bug reports for GNU Guix
2021-11-01 10:37 ` Efraim Flashner
2021-11-05 1:21 ` raid5atemyhomework via Bug reports for GNU Guix
2021-11-05 1:31 ` raid5atemyhomework via Bug reports for GNU Guix [this message]
2022-07-12 3:58 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='71NrR9CIatwqC45LYY-6AWdyugCrijO3vc409GY_eDSCIg9wnzFAE3CerYB3r0zkY16fwraexVge-RKIQPquf0cDHrFRfnXHMGrEdfKAqh0=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=51498@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=raid5atemyhomework@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).