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

Report tab not loading on Azure devops server #176

Closed
danielmertens opened this issue Oct 21, 2020 · 14 comments · Fixed by #363
Closed

Report tab not loading on Azure devops server #176

danielmertens opened this issue Oct 21, 2020 · 14 comments · Fixed by #363

Comments

@danielmertens
Copy link

I'm attempting to use this plugin on our Azure devops server but the report tab seems to be infinitely loading when I open it.
I have included my Yaml pipeline (Stryker is running with correct output and the file is generated) and some logs from the Chrome Developers Console. This last one seems to contain an error.

Versions

  • dotnet-stryker: 0.20.0
  • azure-devops-mutationreport-publisher: 0.1.3

Yaml

- task: DotNetCoreCLI@2
    displayName: 'Install dotnet-stryker'
    inputs:
      command: custom
      custom: tool
      arguments: update dotnet-stryker --tool-path $(Agent.ToolsDirectory)

  - task: Powershell@2
    displayName: 'Run mutation test on ${{ parameters.testName}}'
    inputs:
      workingDirectory: ${{ parameters.workingDirectory }}
      targetType: 'inline'
      script: $(Agent.ToolsDirectory)/dotnet-stryker ${{ parameters.strykerCommands}}

  - task: PublishMutationReport@0
    displayName: 'Publish Mutation Test Report'
    inputs:
      reportPattern: '**/mutation-report.html'

Developer console

image

I can confirm, by using the diagnostic logs, that the html file is found and uploaded by the task.

@psfinaki
Copy link

Hello, I can confirm this - any progress here?

It took me so much effort to get this extension approved for our organization and now it doesn't seem to work :)

@rouke-broersma
Copy link
Member

Hello, I can confirm this - any progress here?

It took me so much effort to get this extension approved for our organization and now it doesn't seem to work :)

Hi! Sorry you took the effort to get this approved and for the extension to then not work 😢
Unfortunately between my work on stryker and my day job I can't currently prioritize this extension even though I would like to. I hope you understand.

@psfinaki
Copy link

Thanks for the response. I understand. If I only I knew TypeScript, I would help myself :)

@rouke-broersma
Copy link
Member

Don't worry, I don't know typescript either! 😁

@xakep139
Copy link
Contributor

I believe the root cause of this issue is related with that workaround: microsoft/azure-devops-extension-api#18 (comment)
And apparently that undocumented workaround doesn't work anymore. According to the docs SDK.getConfiguration() returns a simple dictionary of values.

@xakep139
Copy link
Contributor

@rouke-broersma, please kindly review PR #363

@rouke-broersma
Copy link
Member

@xakep139 awesome I'll take a look soon :)

rouke-broersma added a commit that referenced this issue Apr 28, 2021
* Fix #176 "Report tab not loading on ADO"

* See what happens if we await the call

Co-authored-by: Nikita Balabaev <[email protected]>
Co-authored-by: Rouke Broersma <[email protected]>
Co-authored-by: Rouke Broersma <[email protected]>
@psfinaki
Copy link

Okay, so that error has gone, now we have this:
image

@xakep139, any ideas?

@psfinaki
Copy link

@rouke-broersma, I guess I don't have rights to reopen :(

@rouke-broersma
Copy link
Member

rouke-broersma commented Apr 28, 2021

Okay, so that error has gone, now we have this:
image

@xakep139, any ideas?

We don't use the unpkg package at runtime, there's no reason for that error to be here 🤔

Though this looks like an error in the report and not in the task. @nicojs I'm wondering could this be because of dark mode? Do we save that in local storage and is that perhaps not allowed in iframes?

@nicojs
Copy link
Member

nicojs commented Apr 29, 2021

@psfinaki
Copy link

Okay so update here - my latest issue was because of disabled cookies in the browser 🤦
After I enabled them, the mutation report is shown!

So given that the other issue is open, this can be probably closed again :)

@xakep139
Copy link
Contributor

@psfinaki, glad to hear that 😅
@rouke-broersma, thank you for your time and assistance on solving this issue!
Seems like I can't close the issue, so please do it by yourself

@rouke-broersma
Copy link
Member

Thank you guys for putting in the effort, makes it a lot easier for me to do the same!

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.

5 participants