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

fix: Resolve Fails on Windows #1470

Merged
merged 10 commits into from
Jan 12, 2021
Merged

fix: Resolve Fails on Windows #1470

merged 10 commits into from
Jan 12, 2021

Conversation

Sloox
Copy link
Contributor

@Sloox Sloox commented Jan 7, 2021

Fixes #1434

Test Plan

How do we know the code works?
Simple solution. Increases space used but works without process elevation.
works on Pro + Home.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 7, 2021

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@Sloox
Copy link
Contributor Author

Sloox commented Jan 7, 2021

I have read the CLA Document and I hereby sign the CLA

@Sloox
Copy link
Contributor Author

Sloox commented Jan 7, 2021

recheck

github-actions bot added a commit that referenced this pull request Jan 7, 2021
@Sloox
Copy link
Contributor Author

Sloox commented Jan 7, 2021

@flank-it

@github-actions
Copy link
Contributor

github-actions bot commented Jan 7, 2021

Integration tests succeed ✅
Build scan
Workflow run https://github.com/Flank/flank/actions/runs/469213124

@github-actions
Copy link
Contributor

github-actions bot commented Jan 7, 2021

Timestamp: 2021-01-12 05:07:07
Buildscan url for ubuntu-workflow run 479396836
https://gradle.com/s/q5w6utsb24itc

@Sloox Sloox marked this pull request as ready for review January 8, 2021 12:05
@Sloox Sloox requested a review from piotradamczyk5 January 8, 2021 12:49
@mergify
Copy link

mergify bot commented Jan 8, 2021

Title does not follow the guidelines of Conventional Commits.
Please adjust title before merge and use one of following prefix:

  • build - Changes that affect the build system or external dependencies (dependencies update)
  • ci - Changes to our CI configuration files and scripts (basically directory .github/workflows)
  • docs - Documentation only changes
  • feat - A new feature
  • fix - A bug fix
  • chore - Changes which does not touch the code (ex. manual update of release notes). It will not generate release notes changes
  • refactor - A code change that contains refactor
  • style - Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • test - Adding missing tests or correcting existing tests and also changes for our test app
  • perf - A code change that improves performance (I do not think we will use it)

@Sloox Sloox changed the title bug: Resolve Fails on Windows fix: Resolve Fails on Windows Jan 8, 2021
@Sloox Sloox requested a review from piotradamczyk5 January 8, 2021 17:07
@adamfilipow92
Copy link
Contributor

I try to test your solution but when I try to build Flank I get

Execution failed for task ':flank-scripts:checkIfVersionUpdated'.
> Flank scripts version is not updated, but files changed.
  Please update version according to schema: <breaking change>.<feature added>.<fix/minor change>

@bootstraponline bootstraponline force-pushed the #1434-resolve-fails branch 3 times, most recently from 34998f6 to ee73ee9 Compare January 11, 2021 07:05
@pawelpasterz
Copy link
Contributor

I try to test your solution but when I try to build Flank I get

Execution failed for task ':flank-scripts:checkIfVersionUpdated'.
> Flank scripts version is not updated, but files changed.
  Please update version according to schema: <breaking change>.<feature added>.<fix/minor change>

Hey @adamfilipow92 I've implemented some changes, could you verify again?

@adamfilipow92
Copy link
Contributor

I try to test your solution but when I try to build Flank I get

Execution failed for task ':flank-scripts:checkIfVersionUpdated'.
> Flank scripts version is not updated, but files changed.
  Please update version according to schema: <breaking change>.<feature added>.<fix/minor change>

Hey @adamfilipow92 I've implemented some changes, could you verify again?

Sure!

@adamfilipow92
Copy link
Contributor

adamfilipow92 commented Jan 11, 2021

I think it's not related to this pr but two tests fail
should create new epic with sub issues && should update existing epic from SDKUpdateTest, outputs looks the same. Maybe we could skip these tests on windows and fix it in another ticket.

  1. should create new epic with sub issues
expected to contain:
    ** Create linked issues
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Create new epic
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue 123 successfully converted to an epic
but was:
    ** Create linked issues
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Create new epic
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue 123 successfully converted to an epic
    
	at flank.scripts.shell.firebase.sdk.SDKUpdateTest$should create new epic with sub issues$1.invokeSuspend(SDKUpdateTest.kt:34)
	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 flank.scripts.shell.firebase.sdk.SDKUpdateTest.should create new epic with sub issues(SDKUpdateTest.kt:31)
  1. should update existing epic
expected to contain:
    ** Create linked issues
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Update existing epic
    ** Issues successfully added to the issue 123
but was:
    ** Create linked issues
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Issue created:
         url:    https://bla.org
         number: 123 
    ** Update existing epic
    ** Issues successfully added to the issue 123
    
	at flank.scripts.shell.firebase.sdk.SDKUpdateTest$should update existing epic$1.invokeSuspend(SDKUpdateTest.kt:50)
	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.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 flank.scripts.shell.firebase.sdk.SDKUpdateTest.should update existing epic(SDKUpdateTest.kt:40)

@pawelpasterz
Copy link
Contributor

@adamfilipow92 thanks!
Fixed

@pawelpasterz
Copy link
Contributor

@flank-it

@github-actions
Copy link
Contributor

github-actions bot commented Jan 11, 2021

Integration tests failed ❌
Build scan https://gradle.com/s/7aat66s55e5fg
Workflow run https://github.com/Flank/flank/actions/runs/477077981

@pawelpasterz
Copy link
Contributor

@flank-it

@github-actions
Copy link
Contributor

github-actions bot commented Jan 11, 2021

Integration tests succeed ✅
Build scan https://gradle.com/s/ckxlwwvn6656k
Workflow run https://github.com/Flank/flank/actions/runs/477192919

@pawelpasterz pawelpasterz self-assigned this Jan 11, 2021
Copy link
Contributor

@adamfilipow92 adamfilipow92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Works on windows
  • It passes on windows

@pawelpasterz pawelpasterz merged commit 662d88c into master Jan 12, 2021
@pawelpasterz pawelpasterz deleted the #1434-resolve-fails branch January 12, 2021 06:24
@github-actions github-actions bot locked and limited conversation to collaborators Jan 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Resolve Artifacts Fails on Windows
5 participants