public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] test/py main_signon
Date: Tue, 16 Feb 2016 13:12:14 +0100	[thread overview]
Message-ID: <56C3121E.7060406@xilinx.com> (raw)

Hi Stephen,

trying to run the latest testing on zynq board and getting this
main_signon error.

This is what I am running
./test/py/test.py --bd zynq_zc702  --build --board-identity zc702
and getting below.

Thanks,
Michal

U-Boot 2016.03-rc2 (Feb 16 2016 - 13:10:03 +0100)

Model: Zynq ZC702 Development Board
Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 1 GiB

Bad pattern found on console: main_signon

FAILED:
request = <SubRequest 'u_boot_console' for <Function 'test_version'>>

    @pytest.fixture(scope='function')
    def u_boot_console(request):
        """Generate the value of a test's u_boot_console fixture.

        Args:
            request: The pytest request.

        Returns:
            The fixture value.
        """

>       console.ensure_spawned()

test/py/conftest.py:311:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

self = <u_boot_console_exec_attach.ConsoleExecAttach object at
0x7f2b33dee8d0>

    def ensure_spawned(self):
        """Ensure a connection to a correctly running U-Boot instance.

            This may require spawning a new Sandbox process or resetting
target
            hardware, as defined by the implementation sub-class.

            This is an internal function and should not be called directly.

            Args:
                None.

            Returns:
                Nothing.
            """

        if self.p:
            return
        try:
            self.log.start_section('Starting U-Boot')
            self.at_prompt = False
            self.p = self.get_spawn()
            # Real targets can take a long time to scroll large amounts of
            # text if LCD is enabled. This value may need tweaking in the
            # future, possibly per-test to be optimal. This works for 'help'
            # on board 'seaboard'.
            if not self.config.gdbserver:
                self.p.timeout = 30000
            self.p.logfile_read = self.logstream
            if self.config.buildconfig.get('config_spl', False) == 'y':
                m = self.p.expect([pattern_u_boot_spl_signon] +
self.bad_patterns)
                if m != 0:
                    raise Exception('Bad pattern found on console: ' +
>                                   self.bad_pattern_ids[m - 1])
E                                   Exception: Bad pattern found on
console: main_signon

test/py/u_boot_console_base.py:310: Exception

             reply	other threads:[~2016-02-16 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 12:12 Michal Simek [this message]
2016-02-16 13:32 ` [U-Boot] test/py main_signon Heiko Schocher
2016-02-16 16:04   ` Michal Simek
2016-02-16 16:39     ` Stephen Warren
2016-02-16 19:08       ` Michal Simek
2016-02-16 21:38         ` Stephen Warren
2016-02-17  8:42           ` Michal Simek
2016-02-17  9:05             ` Heiko Schocher
2016-02-17 18:38             ` Stephen Warren
2016-02-17  6:34     ` Heiko Schocher
2016-02-17  7:24       ` Michal Simek

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=56C3121E.7060406@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=u-boot@lists.denx.de \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox