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

allureServe/allureReport task failing after the second run if category.json is saved under test/resources #105

Open
vinogradoff opened this issue Feb 20, 2023 · 0 comments

Comments

@vinogradoff
Copy link

I'm submitting a ...

  • [ x ] bug report

What is the current behavior?

Essential tasks are failing when running multiple times.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • include any categories.json file in the test/resource folder.
  • run tests
  • run gradle allureReportagain (fine)
  • run gradle allureReport again
> Task :copyCategories FAILED

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':copyCategories' (type 'CopyCategories').
  - In plugin 'io.qameta.allure.gradle.adapter.AllureAdapterBasePlugin' type 'io.qameta.allure.gradle.adapter.tasks.CopyCategories' property 'markerFile' is not writable because '/Users/vinogradov/git/bb-selenide/build/copy-categories/copyCategories' is not a file.
    
    Reason: Cannot write a file to a location pointing at a directory.
    
    Possible solutions:
      1. Configure 'markerFile' to point to a file, not a directory.
      2. Annotate 'markerFile' with @OutputDirectory instead of @OutputFiles.
    
    Please refer to https://docs.gradle.org/8.0/userguide/validation_problems.html#cannot_write_output for more details about this problem.


What is the expected behavior?

Tasks run multiple time without any problems.

Please tell us about your environment:

| Allure version | 2.21.1 |
| Gradle | 7.4 and 8.0 |
| Gradle Allure Plugin | 2.11.2 |

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

No branches or pull requests

1 participant