Allure process exited with an error 1 exit value 1

Describe the bug I'm using this plugin for Allure https://marketplace.visualstudio.com/items?itemName=Molecula.allure-test-reports When Azure try to generate the report throws next errors For U...

Describe the bug
I’m using this plugin for Allure
https://marketplace.visualstudio.com/items?itemName=Molecula.allure-test-reports
When Azure try to generate the report throws next errors

For Ubuntu agent:

[command]/usr/local/bin/node /home/vsts/work/_tasks/AllureGenerate_5c975f9d-1c3a-469f-b7c2-8907bf3eacfb/1.0.0/node_modules/allure-commandline/bin/allure generate --output /home/vsts/work/1/s/allure-report/46 /home/vsts/work/1/s/allure-results
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: spawn /home/vsts/work/_tasks/AllureGenerate_5c975f9d-1c3a-469f-b7c2-8907bf3eacfb/1.0.0/node_modules/allure-commandline/dist/bin/allure EACCES
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
    at onErrorNT (internal/child_process.js:415:16)
    [... lines matching original stack trace ...]
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
      throw er; // Unhandled 'error' event
      ^

Error: spawn /home/vsts/work/_tasks/AllureGenerate_5c975f9d-1c3a-469f-b7c2-8907bf3eacfb/1.0.0/node_modules/allure-commandline/dist/bin/allure EACCES
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
    at onErrorNT (internal/child_process.js:415:16)
    [... lines matching original stack trace ...]
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)

For Windows agent:

[command]C:Program Filesnodejsnode.exe D:a_tasksAllureGenerate_5c975f9d-1c3a-469f-b7c2-8907bf3eacfb1.0.0node_modulesallure-commandlinebinallure generate --output D:a1sallure-report49 D:a1sallure-results
Command aborted due to exception {}.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
	at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
	at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
	at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153)
	at ru.yandex.qatools.allure.command.ReportGenerate.runUnsafe(ReportGenerate.java:48)
	at ru.yandex.qatools.allure.command.AbstractCommand.run(AbstractCommand.java:52)
	at ru.yandex.qatools.allure.CommandLine.main(CommandLine.java:46)
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
	at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
	at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
	at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153)
	at ru.yandex.qatools.allure.command.ReportGenerate.runUnsafe(ReportGenerate.java:48)
	at ru.yandex.qatools.allure.command.AbstractCommand.run(AbstractCommand.java:52)
	at ru.yandex.qatools.allure.CommandLine.main(CommandLine.java:46)

	at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:58)
	at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:53)
	at ru.yandex.qatools.allure.AllureMain.main(AllureMain.java:48)

Exception in thread "main" ru.yandex.qatools.allure.data.ReportGenerationException: Could not find any allure results
	at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:58)
	at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:53)
	at ru.yandex.qatools.allure.AllureMain.main(AllureMain.java:48)

To Reproduce
Steps to reproduce the behavior:

  1. Go to Azure Devops

  2. Install Allure plugin https://marketplace.visualstudio.com/items?itemName=Molecula.allure-test-reports

  3. Go to your Azure project according to your user/workspace.

  4. Go to Pipeline section

  5. Create a new pipeline.

  6. Setup a build with Ubuntu/Windows (according what error you need to reproduce) agent
    image

  7. Setup any project to generate results (In this case Maven/Java project)

  8. Setup sheel script for Ubuntu agent to verify files in allure-results directory (use CMD for Windows)
    image

  9. Setup allure plugin to take allure-results directory to generate a report.
    image

  10. Run pipeline

Expected behavior
When pipeline finished (failed or not), it should generate Allure report files.

Screenshots
Error for Ubuntu
Verifying if allure-results directory exists and if it contains files results.
image

Stack trace when Allure plugin is trying to generate a report.
image

Error for Windows
Verifying if allure-results directory exists and if it contains files results.
image

Stack trace when Allure plugin is trying to generate a report.
image

Источник

I am trying to generate an allure report using the command mvn allure:report in Java 10.0.1 but I keep getting the error:

[INFO] Generate report to /home/ken/target/site/allure-maven-plugin
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
    at io.qameta.allure.allure1.Allure1Plugin.xmlFiles(Allure1Plugin.java:375)
    at io.qameta.allure.allure1.Allure1Plugin.getStreamOfAllure1Results(Allure1Plugin.java:370)
    at io.qameta.allure.allure1.Allure1Plugin.readResults(Allure1Plugin.java:101)
    at io.qameta.allure.ReportGenerator.lambda$readResults$0(ReportGenerator.java:32)
    at java.base/java.util.ArrayList.forEach(ArrayList.java:1378)
    at io.qameta.allure.ReportGenerator.readResults(ReportGenerator.java:32)
    at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
    at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
    at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1492)
    at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
    at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
    at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
    at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
    at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
    at io.qameta.allure.ReportGenerator.generate(ReportGenerator.java:54)
    at io.qameta.allure.ReportGenerator.generate(ReportGenerator.java:43)
    at io.qameta.allure.Commands.generate(Commands.java:88)
    at io.qameta.allure.CommandLine.run(CommandLine.java:129)
    at java.base/java.util.Optional.orElseGet(Optional.java:358)
    at io.qameta.allure.CommandLine.main(CommandLine.java:72)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
    ... 20 more
[ERROR] Can't generate allure report data
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:153)
    at io.qameta.allure.maven.AllureCommandline.execute (AllureCommandline.java:88)
    at io.qameta.allure.maven.AllureCommandline.generateReport (AllureCommandline.java:59)
    at io.qameta.allure.maven.AllureGenerateMojo.generateReport (AllureGenerateMojo.java:213)
    at io.qameta.allure.maven.AllureGenerateMojo.executeReport (AllureGenerateMojo.java:137)
    at org.apache.maven.reporting.AbstractMavenReport.generate (AbstractMavenReport.java:255)
    at org.apache.maven.reporting.AbstractMavenReport.execute (AbstractMavenReport.java:143)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    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:309)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:564)
    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)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.965 s
[INFO] Finished at: 2018-12-12T17:18:44-08:00
[INFO] Final Memory: 15M/54M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.qameta.allure:allure-maven:2.9:report (default-cli) on project front-end-test: An error has occurred in Allure report generation.: Could not generate the report: Can't generate allure report data: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

I know that the first error is because of the jaxb-api dependency (I have added all the dependencies to my pom.xml but still getting this error) but my main concern is the second error which prevents the report from being generated.

My pom.xml looks like below:

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <maven.compiler.source>1.10</maven.compiler.source>
    <maven.compiler.target>1.10</maven.compiler.target>
    <aspectj.version>1.9.2</aspectj.version>
    <dependency.locations.enabled>false</dependency.locations.enabled>
</properties>
<dependencies>
    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.12</version>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.8.0
        </version>
        <type>maven-plugin</type>
    </dependency>
    <dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</artifactId>
        <version>3.13.0</version>
    </dependency>
    <dependency>
        <groupId>com.jayway.restassured</groupId>
        <artifactId>rest-assured</artifactId>
        <version>2.9.0</version>
    </dependency>
    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.22.1</version>
        <type>maven-plugin</type>
    </dependency>
    <dependency>
        <groupId>com.googlecode.json-simple</groupId>
        <artifactId>json-simple</artifactId>
        <version>1.1.1</version>
    </dependency>
    <dependency>
        <groupId>javax.xml.bind</groupId>
        <artifactId>jaxb-api</artifactId>
        <version>2.3.1</version>
    </dependency>
    <dependency>
        <groupId>com.sun.xml.bind</groupId>
        <artifactId>jaxb-core</artifactId>
        <version>2.3.0.1</version>
    </dependency>
    <dependency>
        <groupId>com.sun.xml.bind</groupId>
        <artifactId>jaxb-impl</artifactId>
        <version>2.3.1</version>
    </dependency>
    <dependency>
        <groupId>javax.activation</groupId>
        <artifactId>activation</artifactId>
        <version>1.1.1</version>
    </dependency>
    <dependency>
        <groupId>backport-util-concurrent</groupId>
        <artifactId>backport-util-concurrent</artifactId>
        <version>2.1</version>
    </dependency>
    <dependency>
        <groupId>io.qameta.allure</groupId>
        <artifactId>allure-junit4</artifactId>
        <version>2.8.1</version>
        <scope>test</scope>
    </dependency>
</dependencies>
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.22.1</version>
            <configuration>
                <testFailureIgnore>false</testFailureIgnore>
                <argLine>
                    -javaagent:"${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar"
                </argLine>
                <properties>
                    <property>
                        <name>listener</name>
                        <value>io.qameta.allure.junit4.AllureJunit4</value>
                    </property>
                </properties>
            </configuration>
            <dependencies>
                <dependency>
                    <groupId>org.aspectj</groupId>
                    <artifactId>aspectjweaver</artifactId>
                    <version>${aspectj.version}</version>
                </dependency>
            </dependencies>
        </plugin>
        <plugin>
            <groupId>io.qameta.allure</groupId>
            <artifactId>allure-maven</artifactId>
            <version>2.9</version>
        </plugin>
    </plugins>
</build>
<reporting>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-report-plugin</artifactId>
            <version>2.22.1</version>
        </plugin>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-project-info-reports-plugin</artifactId>
            <version>2.9</version>
        </plugin>
    </plugins>
</reporting>

I have the same project on another PC with java 8 and I don’t have an issue generating a report. I went through other similar questions but none of the solutions worked for me.

Any help is greatly appreciated.

Источник

Step Allure Report failed #49

Comments

simonwilbert commented Mar 7, 2017 •

Have just installed latest allure report and it fails to generate the report which looks like its due to a parsing error?

[12:01:28]Step 3/3: Allure Report (6s)
[12:01:30][Step 3/3] Starting: C:BuildAgentjrebinjava.exe -Dallure.config=D:BuildAgenttempbuildTmpallure-config1538927833471753088allure.properties -Dallure.home=C:BuildAgenttoolsallure-commandline -classpath C:BuildAgenttoolsallure-commandlinelib/*;C:BuildAgenttoolsallure-commandlineconf ru.yandex.qatools.allure.CommandLine -v generate D:BuildAgentwork40ce24ae9259cf8allure-results —output D:BuildAgenttempbuildTmpallure-report2133115941729705135allure-report
[12:01:30][Step 3/3] in directory: D:BuildAgentwork40ce24ae9259cf8
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.MigrationPlugin@e24091]
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.XUnitPlugin@86b9e3]
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.TimelinePlugin@1dac5ef]
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.BehaviorsPlugin@509ffa]
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.DefectsPlugin@567e20]
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.GraphPlugin@1d07cbb]
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.EnvironmentPlugin@3570b7]
[12:01:33][Step 3/3] [main] DEBUG ru.yandex.qatools.allure.data.utils.ServiceLoaderUtils — Found Plugin [ru.yandex.qatools.allure.data.plugins.TotalPlugin@947bc5]
[12:01:34][Step 3/3] Exception in thread «main» java.lang.NumberFormatException: For input string: «»
[12:01:34][Step 3/3] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
[12:01:34][Step 3/3] at java.lang.Long.parseLong(Long.java:601)
[12:01:34][Step 3/3] at java.lang.Long.valueOf(Long.java:803)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.DatatypeConverterImpl._parseLong(DatatypeConverterImpl.java:118)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.model.TestCaseResult_JaxbXducedAccessor_stop.parse(TransducedAccessor_field_Long.java:50)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.v2.runtime.unmarshaller.StructureLoader.startElement(StructureLoader.java:195)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:559)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:538)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:153)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:380)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2787)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:118)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
[12:01:34][Step 3/3] at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:243)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:221)
[12:01:34][Step 3/3] at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:276)
[12:01:34][Step 3/3] at javax.xml.bind.JAXB.unmarshal(JAXB.java:242)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.commons.AllureFileUtils.unmarshal(AllureFileUtils.java:59)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.commons.AllureFileUtils.unmarshal(AllureFileUtils.java:50)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.commons.AllureFileUtils.unmarshal(AllureFileUtils.java:40)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.data.io.TestSuiteReader$TestSuiteResultIterator.next(TestSuiteReader.java:48)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.data.io.TestSuiteReader$TestSuiteResultIterator.next(TestSuiteReader.java:1)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.data.io.TestCaseReader$TestCaseResultIterator.nextSuite(TestCaseReader.java:46)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.data.io.TestCaseReader$TestCaseResultIterator.hasNext(TestCaseReader.java:56)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:57)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:53)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.AllureMain.main(AllureMain.java:48)
[12:01:34][Step 3/3] Command aborted due to exception <>.
[12:01:34][Step 3/3] org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
[12:01:34][Step 3/3] at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
[12:01:34][Step 3/3] at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
[12:01:34][Step 3/3] at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.command.ReportGenerate.runUnsafe(ReportGenerate.java:48)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.command.AbstractCommand.run(AbstractCommand.java:52)
[12:01:34][Step 3/3] at ru.yandex.qatools.allure.CommandLine.main(CommandLine.java:46)
[12:01:34][Step 3/3] Delete
[12:01:34][Step 3/3] Delete
[12:01:34][Step 3/3] Delete
[12:01:34][Step 3/3] Process exited with code 1
[12:01:35][Step 3/3] Step Allure Report failed

The text was updated successfully, but these errors were encountered:

Источник

Error when generates a report — Allure Test Reports(Molecula) plugin — Azure Devops(VSTS) #919

Comments

fescobar commented Mar 21, 2019

Describe the bug
I’m using this plugin for Allure
https://marketplace.visualstudio.com/items?itemName=Molecula.allure-test-reports
When Azure try to generate the report throws next errors

For Ubuntu agent:

For Windows agent:

To Reproduce
Steps to reproduce the behavior:

Go to Azure Devops

Go to your Azure project according to your user/workspace.

Go to Pipeline section

Create a new pipeline.

Setup a build with Ubuntu/Windows (according what error you need to reproduce) agent

Setup any project to generate results (In this case Maven/Java project)

Setup sheel script for Ubuntu agent to verify files in allure-results directory (use CMD for Windows)

Setup allure plugin to take allure-results directory to generate a report.

Expected behavior
When pipeline finished (failed or not), it should generate Allure report files.

Screenshots
Error for Ubuntu
Verifying if allure-results directory exists and if it contains files results.

Stack trace when Allure plugin is trying to generate a report.

Error for Windows
Verifying if allure-results directory exists and if it contains files results.

Stack trace when Allure plugin is trying to generate a report.

The text was updated successfully, but these errors were encountered:

MegalaRajendran commented Aug 9, 2019

Facing the same issue. Do we have any updates?

fescobar commented Aug 15, 2019

@MegalaRajendran seems to be nobody is maintaining this plugin.

I have another solution for you. You could start up an Allure docker container in your server (Allure Docker Service: https://github.com/fescobar/allure-docker-service ) and you could send your results from AzureDevops to that container through API.

MegalaRajendran commented Aug 16, 2019 •

@fescobar Thanks for the workaround. Will Try . Hope this solves

stambecg commented Feb 12, 2020

Allure Test Reports plugin is not working on Azure, i am getting below error.
Could you please look into it?

I have checked C:agent_work2stargetallure-results contains multiple files

Источник

Can’t generate allure report data #602

Comments

slipwalker commented Sep 21, 2017 •

I’ve gotten this error during Allure report generation stage. This error happens only when I run the tests through the Grid (grid hub located on the same machine where build server is, its url mentioned in the stack trace error below). Any thoughts/suggestions on this one? Why this happens? Report is generated via Allure Maven plugin.

The text was updated successfully, but these errors were encountered:

slipwalker commented Sep 22, 2017

Also, sometimes for my ordinary working build I get the following error during Allure report generation:

baev commented Oct 8, 2017

@slipwalker could you please specify your allure-maven plugin version, maven version (result of mvn -version command)

slipwalker commented Oct 10, 2017

@baev allure-maven plugin version is 2.8, maven version is 3.5.0

rimmiw commented Jan 26, 2018

Hi,
I have the same problem, I can get my report using command line allure open .
but nothing with maven built I got the error

[INFO] Building CLP-REST 1.0-SNAPSHOT
[INFO] ————————————————————————
[INFO]
[INFO] — allure-maven:2.8:report (default-cli) @ clprest —
[INFO] Allure installation directory D:UserfilesrlamraniDesktopCLP_REGRESSION/.allure
[INFO] Try to finding out allure 2.5.0
[INFO] Downloading allure commandline.
[INFO] Proxy is not specified.
[INFO] Downloading allure commandline complete
[INFO] Generate Allure report (report) with version 2.5.0
[INFO] Generate Allure report to D:UserfilesrlamraniDesktopCLP_REGRESSIONtargetsite/allure-maven-plugin
[INFO] Found results directory D:UserfilesrlamraniDesktopCLP_REGRESSIONtargetsoapui-results
[INFO] Can’t find information about categories.
Can’t find information about categories.
[INFO] Generate report to D:UserfilesrlamraniDesktopCLP_REGRESSIONtargetsiteallure-maven-plugin
Report successfully generated to D:UserfilesrlamraniDesktopCLP_REGRESSIONtargetsiteallure-maven-plugin
[INFO] Report generated successfully.
[INFO] ————————————————————————
[INFO] BUILD SUCCESS
[INFO] ————————————————————————
[INFO] Total time: 20.895 s
[INFO] Finished at: 2018-01-26T15:54:57+01:00
[INFO] Final Memory: 22M/300M
[INFO] ————————————————————————

Источник

Allure не распознает файл для него созданный #676

Comments

git22ura commented Jan 26, 2017

В результате выполнения команды (прописанной по инструкции из вики):

C:smoke_test>»C:Program Files1cv88.3.9.1850bin1cv8.exe» ENTERPRISE /F»C:smoke_testtest_base» /Nadmin /P1 /RunModeManagedApplication /Execute «C:smoke_testxUnitFor1CxddTestRunner.epf» /C «xddRun ЗагрузчикКаталога «»C:smoke_testTests»»; xddReport ГенераторОтчетаAllureXML «»C:smoke_testReportsreport-allure.xml»»; xddShutdown;»

тесты_ОткрытиеФормКонфигурации_ограничениеКоличества ТестДолжен_ПроверитьБагПлатформыПриОткрытииУправляемойФормыПриОткрытииКоторойЕстьИсключение Новые : Справочник.ПервыйСправочник.Форма.ФормаЭлемента Существующие : Справочник.ПервыйСправочник.Форма.ФормаЭлемента

Скармливаю Аллюру, а он ругается

c:testReports>allure generate .
Exception in thread «main» ru.yandex.qatools.allure.data.ReportGenerationExcepti
on: Could not find any allure results
at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureRe
portGenerator.java:58)
at ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureRe
portGenerator.java:53)
at ru.yandex.qatools.allure.AllureMain.main(AllureMain.java:48)
Command aborted due to exception <>.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit
value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecut
or.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:
166)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:
153)
at ru.yandex.qatools.allure.command.ReportGenerate.runUnsafe(ReportGener
ate.java:48)
at ru.yandex.qatools.allure.command.AbstractCommand.run(AbstractCommand.
java:52)
at ru.yandex.qatools.allure.CommandLine.main(CommandLine.java:46)

c:testReports>`
Что я делаю не так?

The text was updated successfully, but these errors were encountered:

Источник

Источник

Я пытаюсь создать отчет о привлекательности с помощью команды mvn allure:report в Java 10.0.1, но все равно получаю сообщение об ошибке:

[INFO] Generate report to /home/ken/target/site/allure-maven-plugin
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
    at io.qameta.allure.allure1.Allure1Plugin.xmlFiles(Allure1Plugin.java:375)
    at io.qameta.allure.allure1.Allure1Plugin.getStreamOfAllure1Results(Allure1Plugin.java:370)
    at io.qameta.allure.allure1.Allure1Plugin.readResults(Allure1Plugin.java:101)
    at io.qameta.allure.ReportGenerator.lambda$readResults$0(ReportGenerator.java:32)
    at java.base/java.util.ArrayList.forEach(ArrayList.java:1378)
    at io.qameta.allure.ReportGenerator.readResults(ReportGenerator.java:32)
    at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
    at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
    at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1492)
    at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
    at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
    at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
    at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
    at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
    at io.qameta.allure.ReportGenerator.generate(ReportGenerator.java:54)
    at io.qameta.allure.ReportGenerator.generate(ReportGenerator.java:43)
    at io.qameta.allure.Commands.generate(Commands.java:88)
    at io.qameta.allure.CommandLine.run(CommandLine.java:129)
    at java.base/java.util.Optional.orElseGet(Optional.java:358)
    at io.qameta.allure.CommandLine.main(CommandLine.java:72)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
    ... 20 more
[ERROR] Can't generate allure report data
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:153)
    at io.qameta.allure.maven.AllureCommandline.execute (AllureCommandline.java:88)
    at io.qameta.allure.maven.AllureCommandline.generateReport (AllureCommandline.java:59)
    at io.qameta.allure.maven.AllureGenerateMojo.generateReport (AllureGenerateMojo.java:213)
    at io.qameta.allure.maven.AllureGenerateMojo.executeReport (AllureGenerateMojo.java:137)
    at org.apache.maven.reporting.AbstractMavenReport.generate (AbstractMavenReport.java:255)
    at org.apache.maven.reporting.AbstractMavenReport.execute (AbstractMavenReport.java:143)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    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:309)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:564)
    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)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.965 s
[INFO] Finished at: 2018-12-12T17:18:44-08:00
[INFO] Final Memory: 15M/54M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.qameta.allure:allure-maven:2.9:report (default-cli) on project front-end-test: An error has occurred in Allure report generation.: Could not generate the report: Can't generate allure report data: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Я знаю, что первая ошибка связана с зависимостью jaxb-api (я добавил все зависимости в свой pom.xml, но все еще получаю эту ошибку), но меня больше всего беспокоит вторая ошибка, которая препятствует созданию отчета.

Мой pom.xml выглядит так:

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <maven.compiler.source>1.10</maven.compiler.source>
    <maven.compiler.target>1.10</maven.compiler.target>
    <aspectj.version>1.9.2</aspectj.version>
    <dependency.locations.enabled>false</dependency.locations.enabled>
</properties>
<dependencies>
    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.12</version>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.8.0
        </version>
        <type>maven-plugin</type>
    </dependency>
    <dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</artifactId>
        <version>3.13.0</version>
    </dependency>
    <dependency>
        <groupId>com.jayway.restassured</groupId>
        <artifactId>rest-assured</artifactId>
        <version>2.9.0</version>
    </dependency>
    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.22.1</version>
        <type>maven-plugin</type>
    </dependency>
    <dependency>
        <groupId>com.googlecode.json-simple</groupId>
        <artifactId>json-simple</artifactId>
        <version>1.1.1</version>
    </dependency>
    <dependency>
        <groupId>javax.xml.bind</groupId>
        <artifactId>jaxb-api</artifactId>
        <version>2.3.1</version>
    </dependency>
    <dependency>
        <groupId>com.sun.xml.bind</groupId>
        <artifactId>jaxb-core</artifactId>
        <version>2.3.0.1</version>
    </dependency>
    <dependency>
        <groupId>com.sun.xml.bind</groupId>
        <artifactId>jaxb-impl</artifactId>
        <version>2.3.1</version>
    </dependency>
    <dependency>
        <groupId>javax.activation</groupId>
        <artifactId>activation</artifactId>
        <version>1.1.1</version>
    </dependency>
    <dependency>
        <groupId>backport-util-concurrent</groupId>
        <artifactId>backport-util-concurrent</artifactId>
        <version>2.1</version>
    </dependency>
    <dependency>
        <groupId>io.qameta.allure</groupId>
        <artifactId>allure-junit4</artifactId>
        <version>2.8.1</version>
        <scope>test</scope>
    </dependency>
</dependencies>
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.22.1</version>
            <configuration>
                <testFailureIgnore>false</testFailureIgnore>
                <argLine>
                    -javaagent:"${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar"
                </argLine>
                <properties>
                    <property>
                        <name>listener</name>
                        <value>io.qameta.allure.junit4.AllureJunit4</value>
                    </property>
                </properties>
            </configuration>
            <dependencies>
                <dependency>
                    <groupId>org.aspectj</groupId>
                    <artifactId>aspectjweaver</artifactId>
                    <version>${aspectj.version}</version>
                </dependency>
            </dependencies>
        </plugin>
        <plugin>
            <groupId>io.qameta.allure</groupId>
            <artifactId>allure-maven</artifactId>
            <version>2.9</version>
        </plugin>
    </plugins>
</build>
<reporting>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-report-plugin</artifactId>
            <version>2.22.1</version>
        </plugin>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-project-info-reports-plugin</artifactId>
            <version>2.9</version>
        </plugin>
    </plugins>
</reporting>

У меня есть тот же проект на другом ПК с java 8, и у меня нет проблем с созданием отчета. Я задавал другие похожие вопросы, но ни одно из решений не помогло мне.

Любая помощь приветствуется.

Источник

Содержание

  1. Почему не работает код?
  2. Unable to run JavaFX via Maven #50
  3. Comments
  4. Failed to execute goal #28
  5. Comments
  6. Support Questions
  7. Support Questions

Почему не работает код?

Error: Main method not found in class Lesson4.BankAccount, please define the main method as:
public static void main(String[] args)
or a JavaFX application class must extend javafx.application.Application
Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:764)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)
at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:564)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
————————————————————————
BUILD FAILURE
————————————————————————
Total time: 2.691 s
Finished at: 2020-08-04T16:59:56+03:00
————————————————————————
Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec (default-cli) on project mavenproject1: Command execution failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

Источник

Unable to run JavaFX via Maven #50

I did set the JAVA_HOME environment variable to point to Java 13.0.1.

However I get the following exception:

C:_devNetBeansProjectshellofx>echo %JAVA_HOME%
C:_devjdk-13.0.1
C:_devNetBeansProjectshellofx>mvn -version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:_toolsapache-maven-3.6.3bin..
Java version: 13.0.1, vendor: Oracle Corporation, runtime: C:_devjdk-13.0.1
Default locale: en_ZA, platform encoding: Cp1252
OS name: «windows 10», version: «10.0», arch: «amd64», family: «windows»

C:_devNetBeansProjectshellofx>mvn clean javafx:run
[INFO] Scanning for projects.
[INFO]
[INFO] ———————— ————————-
[INFO] Building demo 1.0-SNAPSHOT
[INFO] ———————————[ jar ]———————————
[INFO]
[INFO] — maven-clean-plugin:2.5:clean (default-clean) @ hellofx —
[INFO] Deleting C:_devNetBeansProjectshellofxtarget
[INFO]
[INFO] — javafx-maven-plugin:0.0.3:run (default-cli) @ hellofx —
[INFO] Using ‘UTF-8’ encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:_devNetBeansProjectshellofxsrcmainresources
[INFO] Changes detected — recompiling the module!
[INFO] Compiling 1 source file to C:_devNetBeansProjectshellofxtargetclasses
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Unrecognized option: —module-path
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
at org.openjfx.JavaFXBaseMojo.executeCommandLine (JavaFXBaseMojo.java:491)
at org.openjfx.JavaFXBaseMojo.executeCommandLine (JavaFXBaseMojo.java:453)
at org.openjfx.JavaFXRunMojo.execute (JavaFXRunMojo.java:97)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:567)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at org.openjfx.JavaFXBaseMojo.executeCommandLine(JavaFXBaseMojo.java:491)
at org.openjfx.JavaFXBaseMojo.executeCommandLine(JavaFXBaseMojo.java:453)
at org.openjfx.JavaFXRunMojo.execute(JavaFXRunMojo.java:97)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
[INFO] ————————————————————————
[INFO] BUILD FAILURE
[INFO] ————————————————————————
[INFO] Total time: 7.226 s
[INFO] Finished at: 2019-11-27T12:39:26+02:00
[INFO] ————————————————————————
[ERROR] Failed to execute goal org.openjfx:javafx-maven-plugin:0.0.3:run (default-cli) on project hellofx: Error: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

I also tried a variety of things using the sample project provided by NetBeans, but couldn’t get it running.

The text was updated successfully, but these errors were encountered:

Источник

Failed to execute goal #28

I’ll move a project from SWT to JavaFX and start exploring JavaFX and OpenJDK version 12.

I end up with the Getting started with JavaFX and IntelliJ and the Modular with Maven section. I downloaded the project from here and followed the instructions.

and everything works fine.

The text was updated successfully, but these errors were encountered:

The project is modular, and the plugin allows setting the main class as recommended by the modular system module-name/fully-qualified-main-class.

It should work for you as is. Else, please post more details, like a stack trace.

  1. Downloaded the similar project from github and unzip
  2. Open the project in IntelliJIDEA
  3. Compile -> works
  4. Plugins -> javafx -> javafx:run -> fails

This is the output.

It looks like you are running the goal compiler:compile from the compiler plugin ( Plugins -> Compiler ), which does not call the resources plugin, so the classes are compiled (see target/classes ), but the resources are not copied, hence the error you get about not finding the FXML file.

Optionally, you can run Resources -> resources:resources , to manage the resource copying.

Also, if you run directly Lifecycle -> Compile , the compiler plugin in this case does call the resources plugin, the FXML file and other resources are copied (see target/classes ), and then running javafx:run will work.

Alternatively, you can run Lifecycle -> Clean , and directly javafx:run , as the plugin will do compile, resources and run.

Feel free to check that it works for you and close this issue if this is the case.

Thank you for your excellent answer after the view into the glass ball. You’re absolutely wright. Everything works fine.

Источник

Support Questions

  • Subscribe to RSS Feed
  • Mark Question as New
  • Mark Question as Read
  • Float this Question for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page

Created ‎04-20-2016 10:35 AM

  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

As per tutorial http://hortonworks.com/hadoop-tutorial/hands-on-tour-of-apache-spark-in-5-minutes/ I am able to run %sh interpreter and download Hortonworks data from wikipedia, however while trying to copy data to /tmp folder using following command as suggested in tutorial,

%sh hadoop fs -put

zeppelin gives error as Process exited with an error: 1 (Exit value: 1).

Can anyone please suggest the workaround?

Thanks in advance.

Created ‎05-02-2016 09:01 PM

  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

I tried the tutorial you referenced. I found that if I ran «%sh hadoop fs -put

/Hortonworks /tmp» twice:

first time = successfully populated /tmp/Hortonworks

second time = failed with «Process exited with an error: 1 (Exit value: 1)» because /tmp/Hortonworks was already populated.

If I delete the /tmp/Hortonworks folder «%sh hadoop fs -rm -r -f /tmp/Hortonworks» , I am able to re-run «%sh hadoop fs -put

Источник

Support Questions

  • Subscribe to RSS Feed
  • Mark Question as New
  • Mark Question as Read
  • Float this Question for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page

Created ‎04-20-2016 10:35 AM

  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

As per tutorial http://hortonworks.com/hadoop-tutorial/hands-on-tour-of-apache-spark-in-5-minutes/ I am able to run %sh interpreter and download Hortonworks data from wikipedia, however while trying to copy data to /tmp folder using following command as suggested in tutorial,

%sh hadoop fs -put

zeppelin gives error as Process exited with an error: 1 (Exit value: 1).

Can anyone please suggest the workaround?

Thanks in advance.

Created ‎05-02-2016 09:01 PM

  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

I tried the tutorial you referenced. I found that if I ran «%sh hadoop fs -put

/Hortonworks /tmp» twice:

first time = successfully populated /tmp/Hortonworks

second time = failed with «Process exited with an error: 1 (Exit value: 1)» because /tmp/Hortonworks was already populated.

If I delete the /tmp/Hortonworks folder «%sh hadoop fs -rm -r -f /tmp/Hortonworks» , I am able to re-run «%sh hadoop fs -put

Источник

Источник

Я просто настраиваю Allure 2 для работы в моем довольно новом проекте intelliJ Maven.

Копия моего POM прилагается.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>

<groupId>com.intellihub.msats.automation</groupId>
<artifactId>b2bresponder</artifactId>
<version>1.0-SNAPSHOT</version>

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <aspectj.version>1.8.10</aspectj.version>
    <allure.version>1.5.0</allure.version>
</properties>


<dependencies>
    <dependency>
        <groupId>org.testng</groupId>
        <artifactId>testng</artifactId>
        <version>6.11</version>
        <scope>test</scope>
    </dependency>

    <!-- https://mvnrepository.com/artifact/org.seleniumhq.selenium/selenium-java -->
    <dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</artifactId>
        <version>3.6.0</version>
    </dependency>

    <!-- https://mvnrepository.com/artifact/com.opencsv/opencsv -->
    <dependency>
        <groupId>com.opencsv</groupId>
        <artifactId>opencsv</artifactId>
        <version>3.3</version>
    </dependency>

    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-api</artifactId>
        <version>2.9.1</version>
    </dependency>
    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-core</artifactId>
        <version>2.9.1</version>
    </dependency>

    <!-- https://mvnrepository.com/artifact/io.qameta.allure/allure-testng -->
    <dependency>
        <groupId>io.qameta.allure</groupId>
        <artifactId>allure-testng</artifactId>
        <version>2.0-BETA16</version>
    </dependency>

    <!-- https://mvnrepository.com/artifact/javax.xml.bind/jaxb-api -->
    <dependency>
        <groupId>javax.xml.bind</groupId>
        <artifactId>jaxb-api</artifactId>
        <version>2.3.0</version>
    </dependency>
    <dependency>
        <groupId>ru.yandex.qatools.allure</groupId>
        <artifactId>allure-testng-adaptor</artifactId>
        <version>${allure.version}</version>
    </dependency>
</dependencies>

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <configuration>
                <source>1.8</source>
                <target>1.8</target>
            </configuration>
        </plugin>
        <plugin>
            <groupId>io.qameta.allure</groupId>
            <artifactId>allure-maven</artifactId>
            <version>2.9</version>
        </plugin>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-report-plugin</artifactId>
            <version>2.20.1</version>
        </plugin>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.20</version>
            <configuration>
                <useSystemClassLoader>false</useSystemClassLoader>
                <argLine>
                    -javaagent:"${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar"
                </argLine>
                <properties>
                    <property>
                        <name>listener</name>
                        <value>ru.yandex.qatools.allure.testng.AllureTestListener</value>
                    </property>
                    <systemProperties>
                        <property>
                            <name>allure.results.directory</name>
                            <value>${project.build.directory}/allure-results</value>
                        </property>
                    </systemProperties>
                </properties>
            </configuration>
            <dependencies>
                <dependency>
                    <groupId>org.aspectj</groupId>
                    <artifactId>aspectjweaver</artifactId>
                    <version>${aspectj.version}</version>
                </dependency>
                <dependency>
                    <groupId>javax.xml.bind</groupId>
                    <artifactId>jaxb-api</artifactId>
                    <version>2.3.0</version>
                </dependency>
            </dependencies>
        </plugin>
    </plugins>
</build>

<reporting>
    <excludeDefaults>true</excludeDefaults>
    <plugins>
        <plugin>
            <groupId>io.qameta.allure</groupId>
            <artifactId>allure-maven</artifactId>
            <version>2.9</version>
        </plugin>
    </plugins>
</reporting>

Дела идут отлично, пока не дойдет до подготовки отчета об очаровании. Я получаю ошибку NoClassDefFoundError.

[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 154.871 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] --- maven-site-plugin:3.3:site (default-site) @ b2bresponder ---
[INFO] configuring report plugin io.qameta.allure:allure-maven:2.9
[WARNING] No project URL defined - decoration links will not be relativized!
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0 skin.
[INFO] Skipped "Allure" report, file "allure-maven.html" already exists for the English version.
[INFO] Skipped "Allure" report, file "allure-maven.html" already exists for the English version.
[INFO] Skipped "Allure" report, file "allure-maven.html" already exists for the English version.
[INFO] Generating "Allure" report    --- allure-maven:2.9
[INFO] Allure installation directory C:UsersDocumentsSELENIUMprojectsb2bresponder/.allure
[INFO] Try to finding out allure 2.0.1
[INFO] Generate Allure report (aggregate) with version 2.0.1
[INFO] Generate Allure report to C:UsersDocumentsSELENIUMprojectsb2brespondertargetsite/allure-maven-plugin
[INFO] Found results directory C:UsersDocumentsSELENIUMprojectsb2brespondertargetallure-results
[INFO] Can't find information about categories.
[INFO] Generate report to C:UsersDocumentsSELENIUMprojectsb2brespondertargetsiteallure-maven-plugin
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
    at com.fasterxml.jackson.module.jaxb.JaxbAnnotationIntrospector.<init>(JaxbAnnotationIntrospector.java:139)
    at com.fasterxml.jackson.module.jaxb.JaxbAnnotationIntrospector.<init>(JaxbAnnotationIntrospector.java:126)
    at io.qameta.allure.context.JacksonContext.<init>(JacksonContext.java:24)
    at io.qameta.allure.ConfigurationBuilder.useDefault(ConfigurationBuilder.java:50)
    at io.qameta.allure.Commands.createReportConfiguration(Commands.java:158)
    at io.qameta.allure.Commands.generate(Commands.java:63)
    at io.qameta.allure.CommandLine.run(CommandLine.java:129)
    at java.base/java.util.Optional.orElseGet(Optional.java:361)
    at io.qameta.allure.CommandLine.main(CommandLine.java:72)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlElement
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
    ... 9 more
[ERROR] Can't generate allure report data
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
    at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153)
    at io.qameta.allure.maven.AllureCommandline.execute(AllureCommandline.java:88)
    at io.qameta.allure.maven.AllureCommandline.generateReport(AllureCommandline.java:59)
    at io.qameta.allure.maven.AllureGenerateMojo.generateReport(AllureGenerateMojo.java:213)
    at io.qameta.allure.maven.AllureGenerateMojo.executeReport(AllureGenerateMojo.java:137)
    at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
    at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
    at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
    at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
    at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
    at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
    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:309)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:564)
    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)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:47 min
[INFO] Finished at: 2017-11-07T14:55:02+10:00
[INFO] Final Memory: 32M/107M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project b2bresponder: Error during page generation: Error rendering Maven report: Could not generate the report: Can't generate allure report data: Process exited with an error: 1 (Exit value: 1) ->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

У меня была эта проблема, когда я впервые интегрировал Allure 2, но я решил ее, добавив зависимость jaxb-api.

Теперь, когда я перехожу к созданию отчета Allure, я получаю ту же ошибку.

Любые идеи?

1 ответ

Лучший ответ

Проблемы с JAXB должны быть исправлены в версии 2.4.1. Но это не единственная проблема в вашем случае, поскольку я вижу несколько проблем в предоставленном pom.xml:

  • Есть беспорядок из 2-х разных версий адаптера Allure TestNG.
  • В разделе плагина не указана версия отчета.
  • Используется неправильная команда создания отчета. Подробности см. На официальной странице allure-maven.


0

Sergey Korol
10 Ноя 2017 в 12:06

Источник

Like this post? Please share to your friends:
  • All workers are in error state
  • All wheel drive ошибка опель мокка
  • All wheel drive опель инсигния ошибка
  • All weak password танки ошибка сервера
  • All threads completed succeed 0 failed 1 как исправить