Re: [jboss-as7-dev] Characters not echoing back to terminal after running AS7 testsuite
On 5/2/12 10:47 AM, Alexey Loubyansky wrote:
AFAICS, the issue should be fixed now. If anybody is still seeing
it,
please, let me know.
In fact, it used to be a couple of the OSGI tests that used the
CLIWrapper. OSGiManagementTest used to take care of the initialization
and cleaning up. It's removed now and the other utility class is using
the DMR API directly.
Great.
I'll continue looking into minimizing and removing the CLIWrapper
in
favour of the CLI public API.
Good. We need to rationalize things in the testsuite a bit. E.g. once we
adequately test that the CLI public API provides the same input to and
output from the core CLI as reading/writing from a separate process'
stdio does, there no need for other tests to use a separate CLI process.
Similarly, if we establish that the CLI parses strings representing
low-level ops into a proper ModelNode structure for use in the native
management API, then there's no need to test a bunch of low level ops
using both the native management API and the CLI. Prove in some tests
that both mechanisms work in general, and then if the real goal of a
test is to test server side behavior of a particular op (e.g. a
datasource add), pick either the CLI public API or a native management
op to test that, not both.
Alexey
On 04/28/2012 12:10 PM, Darran Lofthouse wrote:
> For me this has been happening after a failed OSGI test that looks as if
> it may use the CLI as well so not sure if that is related.
>
> Regards,
> Darran Lofthouse.
>
>
> On 04/28/2012 10:14 AM, Alexey Loubyansky wrote:
>> It doesn't seem to be a CLI testsuite related issue.
>> I simply removed all the CLI tests (cli local and the main testsuite),
>> './build.sh clean' and './build.sh' and I still see it. Not after
every
>> run though.
>>
>> Alexey
>>
>> On 04/27/2012 08:01 PM, Brian Stansberry wrote:
>>> A number of people are reporting that after building the current
>>> upstream master and running the testsuite, the terminal used to do that
>>> no longer echos characters you type back to the screen.
>>>
>>> Just wanted to let you know we're aware of the issue and are working it,
>>> with a pretty good idea as to the root cause.
>>>
>>> Some solutions people have used to get a normally functioning terminal
>>> after this happens:
>>>
>>> 1) The Reset command from the Terminal menu.
>>> 2) Running 'stty sane' from the command line
>>> 3) Open a new terminal. ;)
>>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat