plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject Re: Trouble building on OSX
Date Thu, 17 Jan 2019 11:59:20 GMT
Hi Julian,

well that would be possible, however the scraper test is failing on one of my 2 Windows VMs
and one of my two Ubuntu 18.04 VMs ... so even supporting all platforms doesn't guarantee
it works everywhere.

Chris



Am 17.01.19, 12:17 schrieb "Julian Feinauer" <j.feinauer@pragmaticminds.de>:

    Hi all,
    
    sorry for beeing late to the party.
    First, thanks justin, chris and tim for your support on finding and fixing that issue.
    Perhaps we could do Jenkins test on other OS'es as well in the future?
    
    @chris:
    Do you have an idea why this exception is raised at first? Is this a OS specific thing
that things fail differently on different OSes?
    
    Julian
    
    Am 17.01.19, 11:33 schrieb "Christofer Dutz" <christofer.dutz@c-ware.de>:
    
        Hi all,
        
        so I fixed this problem by adding a catch block to the TcpSocketFactory that wraps
every Exception during the connection in a PlcConnectionException.
        So technically the test is now passing, even if it's a different exception inside,
but I thought it was better to have PlcConnectionExceptions for everything that breaks while
connecting.
        
        So @Justin ... could you give it another try?
        
        Chris
        
        Am 17.01.19, 11:07 schrieb "Christofer Dutz" <christofer.dutz@c-ware.de>:
        
            Hi Justin,
            
            I think we found the reason for this.
            
            I asked my colleagues in different locations to run the tests and one reported
the exact same failure you did.
            A little investigation resulted in the problem probably being your DNS provider.

            In the test we are looking up a host called "nowhere" ... on my machine I am getting
an "unknown host" error.
            On his machine he tries to connect to a port on a machine that seems to belong
to a Amazon AWS node.
            
            When pinging on my machine I get an "unknown host", on his it starts pinging that
Amazon node ...
            
            That's why your test is failing with a timeout and ours are succeeding with unknown
host errors ... I'll think of a way to work around this problem.
            
            Chris
            
            
            
            Am 16.01.19, 21:39 schrieb "Justin Mclean" <justin@classsoftware.com>:
            
                Hi Chris,
                
                here’s the failing test:
                [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test
(default-test) on project plc4j-driver-modbus: There are test failures.
                [ERROR] 
                [ERROR] Please refer to /Users/justinmclean/incubator-plc4x/plc4j/drivers/modbus/target/surefire-reports
for the individual test results.
                [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream
and [date]-jvmRun[N].dumpstream.
                [ERROR] -> [Help 1]
                org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project
plc4j-driver-modbus: There are test failures.
                
                Please refer to /Users/justinmclean/incubator-plc4x/plc4j/drivers/modbus/target/surefire-reports
for the individual test results.
                Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream
and [date]-jvmRun[N].dumpstream.
                	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
                	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
                	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
                	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
                	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
                	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
                	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
                	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
                	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
                	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
                	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
                	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
                	at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
                	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
                	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                	at java.lang.reflect.Method.invoke(Method.java:498)
                	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
                	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
                	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
                	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
                Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.
                
                Please refer to /Users/justinmclean/incubator-plc4x/plc4j/drivers/modbus/target/surefire-reports
for the individual test results.
                Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream
and [date]-jvmRun[N].dumpstream.
                	at org.apache.maven.plugin.surefire.SurefireHelper.throwException(SurefireHelper.java:240)
                	at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:112)
                	at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:364)
                	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1052)
                	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:868)
                	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
                	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
                	... 20 more
                
                Dump file has this:
                System.exit() or native command error interrupted process checker.
                java.lang.IllegalStateException: error [STOPPED] to read process 5579
                        at org.apache.maven.surefire.booter.PpidChecker.checkProcessInfo(PpidChecker.java:145)
                        at org.apache.maven.surefire.booter.PpidChecker.isProcessAlive(PpidChecker.java:124)
                        at org.apache.maven.surefire.booter.ForkedBooter$2.run(ForkedBooter.java:213)
                        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
                        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
                        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
                        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
                        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                        at java.lang.Thread.run(Thread.java:748)
                
                Not sure that helps.
                
                Thanks,
                Justin
                
                
            
            
        
        
    
    

Mime
View raw message