Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If --legacy-junit-result set, flank crashing on report uploading #947

Closed
adamfilipow92 opened this issue Aug 6, 2020 · 0 comments · Fixed by #950
Closed

If --legacy-junit-result set, flank crashing on report uploading #947

adamfilipow92 opened this issue Aug 6, 2020 · 0 comments · Fixed by #950
Assignees

Comments

@adamfilipow92
Copy link
Contributor

Describe the bug

A clear and concise description of what the bug is.

If --legacy-junit-result set, flank crashing on report uploading

To Reproduce

Steps to reproduce the behavior:

  1. Run flank with flag --legacy-junit-result
  2. When flank tries to upload report throws an exception.
FetchArtifacts
  .
  Updating matrix file

java.lang.NullPointerException
	at java.base/sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:272)
	at java.base/java.nio.file.Path.of(Path.java:147)
	at java.base/java.nio.file.Paths.get(Paths.java:69)
	at ftl.reports.util.ReportManager.getWebLink(ReportManager.kt:51)
	at ftl.reports.util.ReportManager.processXmlFromFile$flank(ReportManager.kt:81)
	at ftl.reports.util.ReportManager.parseTestSuite(ReportManager.kt:100)
	at ftl.reports.util.ReportManager.generate(ReportManager.kt:111)
	at ftl.run.NewTestRunKt$newTestRun$2.invokeSuspend(NewTestRun.kt:27)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:32)
	at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:113)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:274)
	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:84)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59)
	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38)
	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)
	at ftl.cli.firebase.test.android.AndroidRunCommand.run(AndroidRunCommand.kt:47)
	at picocli.CommandLine.executeUserObject(CommandLine.java:1919)
	at picocli.CommandLine.access$1100(CommandLine.java:145)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2332)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2326)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2291)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2159)
	at picocli.CommandLine.execute(CommandLine.java:2058)
	at DebugKt$main$1.invoke(Debug.kt:19)
	at DebugKt$main$1.invoke(Debug.kt)
	at ftl.util.Utils.withGlobalExceptionHandling(Utils.kt:130)
	at DebugKt.main(Debug.kt:18)
	at DebugKt.main(Debug.kt)

Process finished with exit code 1

Expected behavior

A clear and concise description of what you expected to happen.

Flank, shouldn't throw an exception on uploading legacy JUnit result

Details (please complete the following information):

Have you tested on the latest Flank snapshot?

Tested on latest master

This issue is related to Issue 157 because without it we cannot use --legacy-junit-result

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant