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.

Sign up for GitHub

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

Jump to bottom

Integration test is failing on Windows #10

Open
1 task
aSemy opened this issue Feb 18, 2023 · 1 comment
Open
1 task

Integration test is failing on Windows #10

aSemy opened this issue Feb 18, 2023 · 1 comment
Labels
blocked-by:Gradle Blocked by a bug/missing feature in Gradle bug Something isn't working help wanted Extra attention is needed

Comments

@aSemy
Copy link
Contributor

aSemy commented Feb 18, 2023 •
edited
Loading

The BasicProjectIntegrationTest is failing on Windows, but passing on macOS and Unix. It's very weird.

2023-02-18T14:13:06.9914069Z  FAILURE: Build failed with an exception.
2023-02-18T14:13:06.9914629Z  
2023-02-18T14:13:06.9914944Z  * Where:
2023-02-18T14:13:06.9916109Z  Build file 'D:\a\bug-gradle-testkit\bug-gradle-testkit\modules\integration-tests\build\test-temp-dir\it\it-basic\dokka\build.gradle.kts' line: 8
2023-02-18T14:13:06.9916676Z  
2023-02-18T14:13:06.9917234Z  * What went wrong:
2023-02-18T14:13:06.9919137Z  Plugin [id: 'org.jetbrains.kotlin.jvm', version: '1.7.22'] was not found in any of the following sources:
2023-02-18T14:13:06.9919710Z  
2023-02-18T14:13:06.9920335Z  - Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
2023-02-18T14:13:06.9921467Z  - Plugin Repositories (could not resolve plugin artifact 'org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.7.22')
2023-02-18T14:13:06.9923394Z    Searched in the following repositories:     MavenLocal(file:/C:/Users/runneradmin/.m2/repository)     maven(https://cache-redirector.jetbrains.com/jcenter.bintray.com)     MavenRepo     Gradle Central Plugin Repository     Google     maven2(https://cache-redirector.jetbrains.com/dl.bintray.com/kotlin/kotlin-eap)     maven3(https://cache-redirector.jetbrains.com/dl.bintray.com/kotlin/kotlin-dev)
2023-02-18T14:13:06.9924693Z

I've created an issue for Gradle gradle/gradle#23959

  • Re-enable the Windows tests requirement for GitHub merging
@aSemy aSemy added bug Something isn't working help wanted Extra attention is needed labels Feb 18, 2023
aSemy added a commit that referenced this issue Feb 20, 2023
@aSemy
disable BasicProjectIntegrationTest on Windows #10
cdbcbde
@aSemy aSemy mentioned this issue Feb 20, 2023
Merged
aSemy added a commit that referenced this issue Feb 20, 2023
@aSemy
Fix JDK package list URL (#15)
f6e7758 
* rm unused Jackson JSON code

* Update DokkatooPluginTest to use Kotest

* update test dependencies

* move SamWithReceiver workarounds to test-fixtures

* fix jdk11+ packageListUrl

* add Kotest Datatest dependency, and remove unused test suite

* disable BasicProjectIntegrationTest on Windows #10
@aSemy aSemy mentioned this issue Mar 10, 2023
Merged
@aSemy aSemy added the blocked-by:Gradle Blocked by a bug/missing feature in Gradle label May 18, 2023
@aSemy aSemy mentioned this issue Aug 14, 2023
Merged
aSemy added a commit that referenced this issue Aug 15, 2023
@aSemy
update comment with link to #10
c3eb98c
@aSemy
Copy link
Contributor Author

aSemy commented Aug 15, 2023

After #112 the integration tests work on a local Windows machine, but fail on GitHub Workflows due to OOM issues.

@aSemy aSemy mentioned this issue Aug 20, 2023
Merged
aSemy added a commit that referenced this issue Aug 20, 2023
@aSemy
Improve Windows tests on GitHub Workflow (#33)
0850e6e 
Improvements focused on improving Windows Test performance in GitHub Workflows, because currently they always fail due to OOM or weird Gradle errors (see #10)

* Update to Gradle 8.3
* Add `-XX:+AlwaysPreTouch` - see gradle/gradle#3093 (comment)
* Add 'Validate Gradle Wrapper' to GitHub Workflow
* Add `--no-parallel --no-configuration-cache --no-daemon --max-workers=1 -Dorg.gradle.workers.max=1` to Windows test to try to limit memory usage
* Update config-cache assertions to be compatible with new config-cache log messages
* (unrelated tests refactoring) use `build {}` util and refactor `dokka-worker.log` assertions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked-by:Gradle Blocked by a bug/missing feature in Gradle bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aSemy