ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Ivan Zakharyaschev <imz@altlinux.org>
To: devel@lists.altlinux.org
Cc: glebfm@altlinux.org, ldv@altlinux.org
Subject: [devel] FYI: no \n from pty; Re: python3-3.5.1-alt7: Sisyphus/x86_64 test rebuild failed
Date: Mon, 23 May 2016 17:31:01 +0300 (MSK)
Message-ID: <alpine.LFD.2.20.1605231723310.24671@ovicaa.localdomain> (raw)
In-Reply-To: <20160522100035.884E39A1CD0@gyle.altlinux.org>

[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]

FYI:

Последний раз на x86_64 сломалось из-за отсутствия новой строки в 
полученных данных в test_pty, насколько я понял.

На i586 такое не повторилось -- 
http://git.altlinux.org/beehive/logs/Sisyphus-i586/latest/success/python3-3.5.1-alt7 
.

Раньше ни разу такое не вылезало. Если вдруг у кого-то ещё в сборочной 
среде какие-то подобные проблемы, обратите внимание/дайте знать, 
пожалуйста.

On Sun, 22 May 2016, ALT beekeeper wrote:

> Package: python3-3.5.1-alt7
> Status: Sisyphus/x86_64 test rebuild failed
> Cannot build this package.
> Please investigate.
> Excerpt from build log:

[259/397] test_pty
test_basic (test.test_pty.PtyTest) ... Calling master_open()
Got master_fd '9', slave_name '/dev/pts/1'
Calling slave_open('/dev/pts/1')
Got slave_fd '22'
Writing to slave_fd
Writing chunked output
FAIL
test_fork (test.test_pty.PtyTest) ... calling pty.fork()
Waiting for child (23981) to finish.
Child (23981) exited with status 4 (1024).
ok
test__copy_eof_on_all (test.test_pty.SmallPtyTests)
Test the empty read EOF case on both master_fd and stdin. ... ok
test__copy_to_each (test.test_pty.SmallPtyTests)
Test the normal data case on both master_fd and stdin. ... test test_pty 
failed
ok

======================================================================
FAIL: test_basic (test.test_pty.PtyTest)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/usr/src/RPM/BUILD/python3-3.5.1/Lib/test/test_pty.py", line 109, 
in test_basic
     self.assertEqual(b'For my pet fish, Eric.\n', normalize_output(s2))
AssertionError: b'For my pet fish, Eric.\n' != b'For my pet fish, Eric.'

----------------------------------------------------------------------
Ran 4 tests in 0.031s

           reply	other threads:[~2016-05-23 14:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20160522100035.884E39A1CD0@gyle.altlinux.org>]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.20.1605231723310.24671@ovicaa.localdomain \
    --to=imz@altlinux.org \
    --cc=devel@lists.altlinux.org \
    --cc=glebfm@altlinux.org \
    --cc=ldv@altlinux.org \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git